/usr/sbin/vxinfo – UnixArena’s Manual page
/usr/sbin/vxinfo – Print accessibility and usability of volumes
The vxinfo utility reports a usage-type-dependent condition on one or more volumes in a disk group.A report for each volume specified by the volume operand is written to the standard output.
Volume conditions:
| Volume Condition | Description |
| Startable | A volume can be started using ‘vxvol start’ command. |
| Started | The volume has been started and can be used. |
| Started Unusable | The volume has been started but is not operationally accessible. This condition may result from errors that have occurred since the volume was started, or may be a result of administrative actions, such as vxdg -k rmdisk. |
| Unstartable | The volume is not started and either is not correctly configured or doesn’t meet the prerequisites for automatic startup (with volume startup) because of errors or other conditions. |
Plex States
| State | Description |
| ACTIVE | 1. When the volume is started and the plex fully participates in normal volume I/O 2. When the volume is stopped as a result of a system crash and the plex is ACTIVE at the moment of the crash |
| CLEAN | 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 | 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 | Volume creation sets all plexes associated with the volume to the EMPTY state to indicate that the plex is not yet initialized. |
| IOFAIL | 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. |
| LOG | The state of a dirty region logging (DRL) or RAID-5 log plex is always set to LOG. |
| OFFLINE | The vxmend off task indefinitely detaches a plex from a volume by setting the plex state to OFFLINE. |
| SNAPATT | A snapshot plex that is being attached by the snapstart operation, when the attach is complete, the state for the plex is changed to SNAPDONE. If the system fails before the attach completes, the plex and all of its subdisks are removed. |
| SNAPDIS | A snapshot plex that is fully attached. If the system fails before the attach completes, the plex is dissociated from the volume. |
| SNAPDONE | A snapshot plex is ready for a snapshot to be taken |
| SNAPTMP | The SNAPTMP plex state is used during a vxassist snapstart operation when a snapshot is being prepared on a volume. |
| STALE | A plex does not have the complete and current volume contents, that plex is placed in the STALE state. Also, if an I/O error occurs on a plex, the kernel stops using and updating the contents of that plex, and the plex state is set to STALE. |
| TEMP | Setting a plex to the TEMP state eases some plex operations that cannot occur in a truly atomic fashion. |
vxinfo – command line examples:
Display Usable status Volumes in disk group
# vxinfo -g oradg appsvol01 fsgen Started appsvol02 fsgen Startable oravol fsgen Started newvol fsgen Unstartable testvol raid5 Started
Report the name and condition of each plex in each reported volume
# vxinfo -g oradg -p vol appsvol01 fsgen Started plex appsvol01-01 ACTIVE vol appsvol02 fsgen Startable plex appsvol02-01 CLEAN vol oravol fsgen Started plex oravol-01 ACTIVE plex oravol-02 ACTIVE vol newvol fsgen Unstartable plex newvol-01 OFFLINE vol testvol raid5 Started plex testvol-01 ACTIVE plex testvol-02 LOG
Leave a Reply