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

Chapter 8, Administering Volumes
Displaying Volume Information
185
CLEAN Volume State
The volume is not started (kernel state is DISABLED) and its plexes are synchronized. For
a RAID-5 volume, its plex stripes are consistent and its parity is good.
EMPTY Volume State
The volume contents are not initialized. The kernel state is always DISABLED when the
volume is EMPTY.
NEEDSYNC Volume State
The volume requires a resynchronization operation the next time it is started. For a
RAID-5 volume, a parity resynchronization operation is required.
REPLAY Volume State
The volume is in a transient state as part of a log replay. A log replay occurs when it
becomes necessary to use logged parity and data. This state is only applied to RAID-5
volumes.
SYNC Volume State
The volume is either in read-writeback recovery mode (kernel state is currently
ENABLED) or was in read-writeback mode when the machine was rebooted (kernel state
is DISABLED). With read-writeback recovery, plex consistency is recovered by reading
data from blocks of one plex and writing the data to all other writable plexes. If the
volume is ENABLED, this means that the plexes are being resynchronized through the
read-writeback recovery. If the volume is DISABLED, it means that the plexes were being
resynchronized through read-writeback when the machine rebooted and therefore still
need to be synchronized.
For a RAID-5 volume, the volume is either undergoing a parity resynchronization (kernel
state is currently ENABLED) or was having its parity resynchronized when the machine
was rebooted (kernel state is DISABLED).
Note The interpretationof these flagsduringvolume startup ismodifiedby the persistent
state log for the volume (for example, the DIRTY/CLEAN flag). If the clean flag is
set, an ACTIVEvolume was notwritten to byany processesor was noteven open at
the time of the reboot; therefore, it can be considered CLEAN. The clean flag is
always set in any case where the volume is marked CLEAN.