HP XP P9000 RAID Manager Reference Guide (T1610-96061, January 2014)
DescriptionOption
If the target device has shared an LDEV among multiple device files and an LDEV is displayed
by another target device already, then its target device is suppressed as a comment as shown
below:
# ERROR [LDEV LINK] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [FIBRE FCTBL = 4]
If the target device does not have a valid MU#, then its target device is suppressed as a comment
as shown below:
# ERROR [INVALID MUN (2 < 1)] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3 ]
If the target device is mixed with a different RAID TYPE, then its target device is suppressed as
a comment as shown below:
# ERROR [MIXING RAID TYPE] /dev/rdsk/c24t0d3 SER = 61456 LDEV = 195 [ OPEN-3 ]
Flushes the system buffer associated to a logical drive which corresponds to a [-g <group>]
through the KEY WORD($Volume,$LETALL, $Physical) provided via STDIN.
-find sync[d] [MU#]
[-g <group>]
[-g <group>] specifies the group for 'dev_group' on horcm.conf. If this option is not specified,
then flushes the system buffer associated to all groups for the local instance.
Example of flushing the system buffer associated to ORB group through $Volume (Windows):
echo $Volume | raidscan -find sync -g ORB or
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}
Example of flushing the system buffer associated to all groups for the local instance (Windows):
echo $Volume | raidscan -find sync or
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}
Notes:
(1) WindowsNT does not support the LDM volume so that the user must be specified $LETALL
instead of $Volume as follows:
(1)raidscan -pi $LETALL -find sync -g ORA
[SYNC] : ORA ORA_000[-] -> F:\Dsk1\p1 : F:
(2) The option cannot be specified the device object name as follows:
D:\Vol(Dms,Dmt,Dmr)X\DskY,\Vol(Dms,Dmt,Dmr)X\DskY
(3) Sync executes the following behavior under any conditions:
• If the logical drive which corresponds to a [-g <group>] is not open by any applications,
then sync flushes the system buffer to a drive and makes the dismount state for this drive.
• If the logical drive which corresponds to a [-g <group>] is already opened by any
applications, then sync flushes only the system buffer to a drive. This is allowed to flush the
system buffer before pairsplit without unmounting the PVOL (opening state), and indicates
the behavior as [FLUSH] below: [FLUSH] : ORA ORA_000[-] -> \Vol44\Dsk0 :
Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}
72 Data management commands