VXVM 6.1 – How to get Veritas Volume Accessibility and Usability information using vxinfo?

vxvm-how-to
The following example output shows one volume, mkting, as being unstartable:
# vxinfo [-g diskgroup] [volume …] 
home   fsgen Started
mkting fsgen Unstartable
src fsgen Started
rootvol root Started
swapvol swap Started

The vxinfo utility reports the following conditions for volumes:

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

:::: 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:

  • 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.
  • CLEAN The plex contains valid data and the volume was stopped cleanly.
  • DCOSNP A data change object (DCO) plex that is attached to a volume, and which can be used by a snapshot plex to create a DCO volume during a snapshot operation.
  • EMPTY The plex is part of a volume that has not yet been initialized.
  • IOFAIL The plex was detached because of an uncorrectable I/O failure on one of the subdisks in the plex.
  • LOG A dirty region logging (DRL) or RAID-5 log plex.
  • 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.
  • NODEVICE A physical device could not be found corresponding to the disk ID in the disk media record for one of the subdisks associated with the plex. The plex cannot be used until this condition is fixed, or the affected subdisk is dissociated.
  • OFFLINE The plex was disabled using the vxmend off operation.
  • REMOVED A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.
  • SNAPATT The plex is being attached as part of a backup operation by the vxassist snapstart operation. When the attach is complete, the condition changes to SNAPDONE. A system reboot or manual starting of the volume removes the plex and all of its subdisks.
  • 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 dissociates the plex.
  • 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 removes 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 changes to SNAPDIS. A system reboot or manual starting of the volume dissociates 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.
  • 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 dissociates the plex.
  • TEMPRM The plex was created for temporary use by a current operation. A system reboot or manual starting of a volume removes 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 removes the plex and all of its subdisks.

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.
  • 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 EMPTY conditions).
  • Started Unusable :   This condition is reported if the volume is enabled, but the volume does not meet the criteria for being Started.
  • Unstartable             :      This condition is reported if the volume is not enabled, but the volume does not meet the criteria for being Startable.

:::: RAID-5 Usage Type

Plexes of RAID-5 volumes can be either data plexes (that is, RAID-5 plexes) or log plexes. RAID-5 data and log plex conditions are as follows:
  • 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.
  • CLEAN The plex contains valid data and the volume was stopped cleanly. The raid5 usage type does not support any options passed in with -o.
  • IOFAIL The plex was detached from use as a result of an uncorrectable I/O failure on one of the subdisks in the plex.
  • 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.
  • OFFLINE The plex was disabled using the vxmend off operation.
  • REMOVED A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.
  • RAID-5 data plexes can 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 cause data loss.
  • UNUSABLE This indicates that 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 additional conditions:
  • 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 (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.
Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

1 Response

  1. September 18, 2015

    […] Read – How to get Veritas Volume Accessibility and Usability information using vxinfo? […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us