Veritas Volume Manager 5.0 Administrator's Guide (September 2006)

373Administering hot-relocation
How hot-relocation works
Failures have been detected by the Veritas Volume Manager:
failed plexes:
home-02
src-02
See “Modifying the behavior of hot-relocation” on page 384 for information on how to
send the mail to users other than root.
You can determine which disk is causing the failures in the above example message by
using the following command:
# vxstat -g mydg -s -ff home-02 src-02
The -s option asks for information about individual subdisks, and the -ff option displays
the number of failed read and write operations. The following output display is typical:
FAILED
TYP NAME READS WRITES
sd mydg01-04 0 0
sd mydg01-06 0 0
sd mydg02-03 1 0
sd mydg02-04 1 0
This example shows failures on reading from subdisks mydg02-03 and mydg02-04 of
disk mydg02.
Hot-relocation automatically relocates the affected subdisks and initiates any necessary
recovery procedures. However, if relocation is not possible or the hot-relocation feature is
disabled, you must investigate the problem and attempt to recover the plexes. Errors can
be caused by cabling failures, so check the cables connecting your disks to your system. If
there are obvious problems, correct them and recover the plexes using the following
command:
# vxrecover -b -g mydg home src
This starts recovery of the failed plexes in the background (the command prompt
reappears before the operation completes). If an error message appears later, or if the
plexes become detached again and there are no obvious cabling failures, replace the disk
(see “Removing and replacing disks” on page 112).
Complete disk failure mail messages
If a disk fails completely and hot-relocation is enabled, the mail message lists 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:
mydg02
failed plexes: