System buffer flushing function – HP XP RAID Manager Software User Manual
Page 177
![background image](/manuals/398124/177/background.png)
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
\\?\Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}\
G:\
\\?\
Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}\
F:\
You can determine what \\?\Volume{guid}\ is configured, as follows:
inqraid $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -CLI
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
\Vol46\Dsk1 CL2-K 61456 193 - S/s/ss 0004 1:01-10 OPEN-3
raidscan -pi $Volume
{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -find
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
\Vol46\Dsk1 0 F CL2-K 7 1 61456 193 OPEN-3
System buffer flushing function
The logical drive to be flushed can be specified by the following two methods. One method is that
the logical drive (e.g., G:\hd1 drive, as below) is specified immediately, but this method must
know about the logical drive corresponding to a group before executing the sync command. Also
the volume is mounting by a directory and this method requires finding its volume name. To solve
such a complication, RAID Manager supports a method that flushes the system buffer associated
with a logical drive through finding a volume{guid} corresponding to a group of the configuration
file. This method does not depend on mounted point, so that it is possible to flush the volume
mounted by a directory. This method is supported to be specified a group to the raidscan -find
sync
command.
Figure 66 LDM volume flushing
The following example flushes the system buffer associated with the ORB group through $Volume.
raidscan -pi
$Volume -find sync -g ORB
[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
The following example flushes the system buffer associated with all groups for the local instance.
raidscan -pi
$Volume -find sync
[SYNC] : ORA ORA_000[-] -> \Vol44\Dsk0 : Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}
[SYNC] : ORA ORA_000[-] -> \Vol45\Dsk0 : Volume{56e4954a-28d5-4824-a408-3ff9a6521e5e}
[SYNC] : ORB ORB_000[-] -> \Dmt1\Dsk1 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
[SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}
NOTE:
Windows NT does not support the LDM volume, so specify $LETALL instead of $Volume.
LDM volume discovery and flushing for Windows 177