VERITAS Volume Manager 4.1 Administrator's Guide

Creating and Administering Plexes
Displaying Plex Information
Chapter 6214
when the volume is stopped as a result of a system crash and the
plex is ACTIVE at the moment of the crash
In the latter case, a system failure can leave plex contents in an
inconsistent state. When a volume is started, VxVM does the recovery
action to guarantee that the contents of the plexes marked as ACTIVE
are made identical.
NOTE On a system running well, ACTIVE should be the most common state
you see for any volume plexes.
CLEAN Plex State
A plex is in a CLEAN state when it is known to contain a consistent copy
(mirror) of the volume contents and an operation has disabled the
volume. As a result, when all plexes of a volume are clean, no action is
required to guarantee that the plexes are identical when that volume is
started.
DCOSNP Plex State
This state indicates that a data change object (DCO) plex attached to a
volume can be used by a snapshot plex to create a DCO volume during a
snapshot operation.
EMPTY Plex State
Volume creation sets all plexes associated with the volume to the
EMPTY state to indicate that the plex is not yet initialized.
IOFAIL Plex State
The IOFAIL plex state is associated with persistent state logging. When
the vxconfigd daemon detects an uncorrectable I/O failure on an ACTIVE
plex, it places the plex in the IOFAIL state to exclude it from the
recovery selection process at volume start time.
This state indicates that the plex is out-of-date with respect to the
volume, and that it requires complete recovery. It is likely that one or
more of the disks associated with the plex should be replaced.