vxinfo(ADM)

vxinfo - print accessibility and usability of volumes

Synopsis

vxinfo [ -Vp ] [ -g diskgroup ] [ -U usetype ] [ -o useopt ] [ volume ... ]

Description

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. If no volume operands are given, then a volume condition report is provided for each volume in the selected disk group.

Each invocation can be applied to only one disk group at a time, due to internal implementation constraints. Any volume operands will be used to determine a default disk group, according to the standard disk group selection rules described in vxintro(ADM). A specific disk group can be forced with -g diskgroup.

Options

-V: Write a list of utilities that would be called from vxinfo, along with the arguments that would be passed. The -V performs a ``mock run'' so the utilities are not actually called.
-p: Report the name and condition of each plex in each reported volume.
-U usetype: Specify the usage type for the operation. If no volume operands are specified, then the output is restricted to volumes with this usage type. If volume operands are specified, then this will result in a failure message for all named volumes that do not have the indicated usage type.
-g diskgroup: Specify the disk group for the operation, either by disk group ID or by disk group name. By default, the disk group is chosen based on the volume operands. If no volume operands are specified, the disk group defaults to rootdg.
-o useopt: Pass in usage-type-specific options to the operation.

Volume conditions

The volume condition is a usage-type-dependent summary of the state of a volume. This condition is derived from the volume's kernel-enabled state and the usage-type-dependent states of the volume's plexes.

The vxinfo utility reports the following conditions for volumes:

Startable: A vxvol startall operation would likely succeed in starting the volume.
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.
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.

Output format

Summary reports for each volume are printed in one-line output records. Each volume output line consists of blank-separated fields for the volume name, volume usage type, and volume condition. The following example shows the volume summary:

	bigvol         fsgen    Startable
	vol2           fsgen    Startable
	brokenvol      gen      Unstartable

Each plex output line consists of blank-separated fields for the plex name and the plex condition. The plex records are accompanied by their volume records, as the following example shows:

	vol    bigvol         fsgen    Startable
	plex   bigvol-01      ACTIVE
	vol    vol2           fsgen    Startable
	plex   vol2-01        ACTIVE
	vol    brokenvol      gen      Unstartable

Fsgen and gen usage types

The fsgen and gen usage types provide identical semantics for the vxinfo utility. The fsgen and gen usage types do not support any options passed in with -o.

Plex conditions (reported with -p) can be one of the following:

NODAREC: No physical disk was found for one of the subdisks in the plex. This implies either that the physical disk failed, making it unrecognizable, or that the physical disk is no longer attached through a known access path.
REMOVED: A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.
IOFAIL: The plex was detached from use as a result of an uncorrectable I/O failure on one of the subdisks in the plex.
STALE: The plex does not contain valid data, either as a result of a disk replacement affecting one of the subdisks in the plex, or as a result of an administrative action on the plex such as vxplex det.
CLEAN: The plex contains valid data and the volume was stopped cleanly.
ACTIVE: Either the volume is started and the plex is enabled, or the volume was not stopped cleanly and the plex was valid when the volume was stopped.
OFFLINE: The plex was disabled using the vxmend off operation.
EMPTY: The plex is part of a volume that has not yet been initialized.
TEMP: The plex is associated temporarily as part of a current operation, such as vxplex cp or vxplex att. A system reboot or manual starting of a volume will dissociate the plex.
TEMPRM: The plex was created for temporary use by a current operation. A system reboot or manual starting of a volume will remove the plex.
TEMPRMSD: The plex and its subdisks were created for temporary use by a current operation. A system reboot or manual starting of the volume will remove the plex and all of its subdisks.
SNAPATT: The plex is being attached as part of a backup operation by the vxassist snapstart operation. When the attach is complete, the condition will change to SNAPDONE. A system reboot or manual starting of the volume will remove the plex and all of its subdisks.
SNAPDONE: A vxassist snapstart operation completed the process of attaching the plex. It is a candidate for selection by the vxassist snapshot operation. A system reboot or manual starting of the volume will remove the plex and all of its subdisks.
SNAPTMP: The plex is being attached as part of a backup operation by the vxplex snapstart operation. When the attach is complete, the condition will change to SNAPDIS. A system reboot or manual starting of the volume will dissociate the plex.
SNAPDIS: A vxassist snapstart operation completed the process of attaching the plex. It is a candidate for selection by the vxplex snapshot operation. A system reboot or manual starting of the volume will dissociate the plex.

Volume conditions for these usage types are reported as follows:

Startable: This condition is reported if the volume is not enabled and if any of the plexes have a reported condition of ACTIVE or CLEAN.
Unstartable: This condition is reported if the volume is not enabled, but the volume does not meet the criteria for being Startable.
Started: This condition is reported if the volume is enabled and at least one of the associated plexes is enabled in read-write mode (which is normal for enabled plexes in the ACTIVE and EMTPY conditions).
Started Unusable: This condition is reported if the volume is enabled, but the volume does not meet the criteria for being Started.

RAID-5 usage type

The raid5 usage type does not support any options passed in with -o.

Plexes of RAID-5 volumes can be either data plexes (i.e. RAID-5 plexes) or log plexes. RAID-5 plex conditions are as follows:

NODAREC: No physical disk was found for one of the subdisks in the plex. This implies either that the physical disk failed, making it unrecognizable, or that the physical disk is no longer attached through a known access path.
REMOVED: A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.
IOFAIL: The plex was detached from use as a result of an uncorrectable I/O failure on one of the subdisks in the plex.
CLEAN: The plex contains valid data and the volume was stopped cleanly.
ACTIVE: Either the volume is started and the plex is enabled, or the volume was not stopped cleanly and the plex was valid when the volume was stopped.
OFFLINE: The plex was disabled using the vxmend off operation.

RAID-5 plexes can also have these additional conditions:

DEGRADED: Due to subdisk failures, the plex is in degraded mode. This indicates a loss of data redundancy in the RAID-5 volume and any further failures could cause data loss.
STALEPRTY: The parity is not in sync with the data in the plex. This indicates a loss of data redundancy in the RAID-5 volume and any further failures could case data loss.
UNUSABLE: This indicates a double-failure occurred within the plex. The plex is unusable due to subdisk failures and/or stale parity.

Log plexes of RAID-5 volumes can have the following conditions:

NODAREC: No physical disk was found for one of the subdisks in the plex. This implies either that the physical disk failed, making it unrecognizable, or that the physical disk is no longer attached through a known access path.
REMOVED: A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.
IOFAIL: The plex was detached from use as a result of an uncorrectable I/O failure on one of the subdisks in the plex.
CLEAN: The plex contains valid data and the volume was stopped cleanly.
ACTIVE: Either the volume is started and the plex is enabled, or the volume was not stopped cleanly and the plex was valid when the volume was stopped.
OFFLINE: The plex was disabled using the vxmend off operation.

Log plexes of RAID-5 volumes can also have the following additional condition:

BADLOG: The contents of the plex are not usable as logging data.

Volume conditions for volumes of the raid5 usage type are the same as for the fsgen and gen usage types (i.e., Startable, Unstartable, Started and Started Unusable). In addition, the following conditions can modify the conditions:

Degraded: This condition indicates that the RAID-5 plex of the volume is in degraded mode due to the unavailability of a subdisk in that plex.
Staleprty: This condition indicates that some of the parity in the RAID-5 plex is stale and requires recovery.

Files

/etc/vx/type/usetype/vxinfo: The utility that performs vxinfo operations for a particular volume usage type.

Exit codes

The vxinfo utility exits with a nonzero status if the attempted operation fails. A nonzero exit code is not a complete indicator of the problems encountered, but rather denotes the first condition that prevented further execution of the utility. See vxintro(ADM) for a list of standard exit codes.

References

vxassist(ADM), vxdg(ADM), vxintro(ADM), vxmend(ADM), vxplex(ADM), vxsd(ADM), vxvol(ADM)