Using Virtual Disks With Solaris Volume Manager
When a RAID or mirror Solaris Volume Manager volume is used as a virtual disk by another domain, then it has to be exported without setting the exclusive (excl
) option. Otherwise, if there is a failure on one of the components of the Solaris Volume Manager volume, then the recovery of the Solaris Volume Manager volume using the metareplace
command or using a hot spare does not start. The metastat
command sees the volume as resynchronizing, but the resynchronization does not progress.
For example, /dev/md/dsk/d0
is a RAID Solaris Volume Manager volume exported as a virtual disk with the excl
option to another domain, and d0
is configured with some hot-spare devices. If a component of d0
fails, Solaris Volume Manager replaces the failing component with a hot spare and resynchronizes the Solaris Volume Manager volume. However, the resynchronization does not start. The volume is reported as resynchronizing, but the resynchronization does not progress.
primary# metastat d0
d0: RAID
State: Resyncing
Hot spare pool: hsp000
Interlace: 32 blocks
Size: 20097600 blocks (9.6 GB)
Original device:
Size: 20100992 blocks (9.6 GB)
Device Start Block Dbase State Reloc
c2t2d0s1 330 No Okay Yes
c4t12d0s1 330 No Okay Yes
/dev/dsk/c10t600C0FF0000000000015153295A4B100d0s1 330 No Resyncing Yes
In such a situation, the domain using the Solaris Volume Manager volume as a virtual disk has to be stopped and unbound to complete the resynchronization. Then the Solaris Volume Manager volume can be resynchronized using the metasync
command.
# metasync d0