Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

Failures have been detected by the Veritas Volume Manager:
failed disks:
mydg02
failed plexes:
home-02
src-02
mkting-01
failing disks:
mydg02
This message shows that mydg02 was detached by a failure. When a disk is
detached, 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).
One possible cause of the problem could be a cabling error.
See “Partial disk failure mail messages” on page 409.
If the problem is not a cabling error, replace the disk.
See “Removing and replacing disks” on page 130.
How space is chosen for relocation
A spare disk must be initialized and placed in a disk group as a spare before it can
be 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.
When selecting space for relocation, hot-relocation preserves the redundancy
characteristics of the VxVM object to which the relocated subdisk belongs. For
example, hot-relocation ensures that subdisks from a failed plex are not relocated
to a disk containing a mirror of the failed plex. If redundancy cannot be preserved
using any available spare disks and/or free space, hot-relocation does not take
place. If relocation is not possible, the system administrator is notified and no
further action is taken.
From the eligible disks, hot-relocation attempts to use the disk that is “closest”
to the failed disk. The value of “closeness” depends on the controller, target, and
disk number of the failed disk. A disk on the same controller as the failed disk is
closer than a disk on a different controller. A disk under the same target as the
failed disk is closer than one on a different target.
411Administering hot-relocation
How hot-relocation works