Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

10 Recovery from hardware failure
Understanding the plex state cycle
Figure 1-2 Additional plex state transitions
After a system crash and reboot, all plexes of a volume are ACTIVE but marked
with plex kernel state DISABLED until their data is recovered by the
vxvol
resync task.
A plex may be taken offline with the
vxmend off command, made available again
using
vxmend on, and its data resynchronized with the other plexes when it is
reattached using
vxplex att. A failed resynchronization or uncorrectable I/O
failure places the plex in the IOFAIL state.
“Recovering an unstartable mirrored volume” on page 11, and subsequent
sections describe the actions that you can take if a system crash or I/O error
leaves no plexes of a mirrored volume in a CLEAN or ACTIVE state.
For information on the recovery of RAID-5 volumes, see “Failures on RAID-5
volumes” on page 15 and subsequent sections.
Recover data (vxvol
resync)
Initialize plex
(vxvol init clean)
Take plex offline
(vxmend off)
Shut down (vxvol
stop)
After crash and
reboot (vxvol
start)
Uncorrectable I/O
failure
Put plex online
(vxmend on)
Resync data (vxplex
att)
Resync fails
Create plex
PS: EMPTY
PKS: DISABLED
PS: ACTIVE
PKS: DISABLED
Start up
(vxvol start)
PS: CLEAN
PKS: DISABLED
PS: ACTIVE
PKS: ENABLED
PS: OFFLINE
PKS: DISABLED
PS: IOFAIL
PKS: DETACHED
PS: STALE
PKS: DETACHED
PS = plex state
PKS = plex kernel state