VERITAS Volume Manager 3.5 Administrator's Guide (September 2002)

How Hot-Relocation works
232 VERITAS Volume Manager Administrator’s Guide
Complete Disk Failure Mail Messages
If adisk fails completely and hot-relocationis enabled, the mail messagelists the disk that
failed and all plexes that use the disk. For example, you can receive mail as shown in this
example display:
To: root
Subject: Volume Manager failures on host teal
Failures have been detected by the VERITAS Volume Manager:
failed disks:
disk02
failed plexes:
home-02
src-02
mkting-01
failing disks:
disk02
This message shows that disk02 was detachedby afailure.When adisk isdetached, I/O
cannot get to that disk. The plexes home-02, src-02, and mkting-01 were also
detached (probably because of the failure of the disk).
As described in “Partial Disk Failure Mail Messages” on page 231, the problem can be a
cabling error. If the problem is not a cabling error, replace the disk (see “Removing and
Replacing Disks” on page 76).
How Space is Chosen for Relocation
A sparedisk mustbe initialized and placed in a disk groupas asparebefore it canbe used
for replacement purposes. If no disks have been designated as spares when a failure
occurs, VxVM automatically uses any available free space in the disk group in which the
failure occurs. If there is not enough spare disk space, a combination of spare space and
free space is used.
The free space used in hot-relocation must not have been excluded from hot-relocation
use. Disks can be excluded from hot-relocation use by using vxdiskadm, vxedit or the
VERITAS Enterprise Administrator (VEA).
You can designate one or more disks as hot-relocation spares within each disk group.
Disks can be designated as spares by using vxdiskadm, vxedit, or the VEA. Disks
designated as spares do not participate in the free space model and should not have
storage space allocated on them.