Installation guide
Hot Spares Do Not Work Correctly When Solaris
Volume Manager RAID-1 (Mirror) or RAID-5 Volumes
Are Created in Disk Sets Built on Soft Partitions
(4981358)
If you create a Solaris Volume Manager RAID-1 (mirror) or RAID-5 volume in a disk set that is
built on top of a soft partition, hot spare devices do not work correctly.
Problems that you might encounter include, but are not limited to, the following:
■
A hot spare device might not activate.
■
A hot spare device status might change, indicating the device is broken.
■
A hot spare device is used, but resynced from the wrong drive.
■
A hot spare device in use encounters a failure, but the broken status is not reported.
Workaround: Do not use this conguration to create a Solaris Volume Manager RAID-1 or
RAID-5 volume in disk sets.
Solaris Volume Manager metadevadm Command Fails if
Logical Device Name No Longer Exists (4645721)
You cannot replace a failed drive with a drive that has been congured with the Solaris Volume
Manager software. The replacement drive must be new to Solaris Volume Manager software. If
you physically move a disk from one slot to another slot on a Sun StorEdge A5x00, the
metadevadm command fails. This failure occurs when the logical device name for the slice no
longer exists. However, the device ID for the disk remains present in the metadevice replica.
The following message is displayed:
Unnamed device detected. Please run ’devfsadm && metadevadm -r to resolve.
Note – You can access the disk at the new location during this time. However, you might need to
use the old logical device name to access the slice.
Workaround: Physically move the drive back to its original slot.
Solaris Volume Manager
Solaris 10 5/08 Release Notes • April 200894