The plex state cycle

Changing plex states are part of normal operations, and do not necessarily indicate abnormalities that must be corrected. A clear understanding of the various plex states and their interrelationship is necessary if you want to be able to perform any recovery procedures.

Figure: Main plex state cycle shows the main transitions that take place between plex states in VxVM.

Figure: Main plex state cycle

Main plex state cycle

For more information about plex states, see the Veritas Volume Manager Administrator's Guide.

At system startup, volumes are started automatically and the vxvol start task makes all CLEAN plexes ACTIVE. At shutdown, the vxvol stop task marks all ACTIVE plexes CLEAN. If all plexes are initially CLEAN at startup, this indicates that a controlled shutdown occurred and optimizes the time taken to start up the volumes.

Figure: Additional plex state transitions shows additional transitions that are possible between plex states as a result of hardware problems, abnormal system shutdown, and intervention by the system administrator.

Figure: Additional plex state transitions

Additional plex state transitions

When first created, a plex has state EMPTY until the volume to which it is attached is initialized. Its state is then set to CLEAN. Its plex kernel state remains set to DISABLED and is not set to ENABLED until the volume is started.

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.

There are various 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.

More Information

Recovering an unstartable mirrored volume

Failures on RAID-5 volumes