unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Page:
Section:
Apropos / Subsearch:
optional field



 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



 NAME
      vxinfo - print accessibility and usability of volumes

 SYNOPSIS
      vxinfo [-pV] [-g diskgroup] [-o useopt] [-U usetype] [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.	Any
      volume operands will be used to determine a default disk group,
      according to the standard disk group selection rules described in
      vxintro(1M).  A specific disk group can be forced with -g diskgroup.

 OPTIONS
      -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.

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

      -V	Write a list of utilities that would be called from vxinfo,
		along with the arguments that would be passed.	The -V
		performs a preview run so the utilities are not actually
		called.

 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.




				    - 1 -	  Formatted:  August 2, 2006






 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



      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.

 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:

      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.

      EMPTY	The plex is part of a volume that has not yet been
		initialized.



				    - 2 -	  Formatted:  August 2, 2006






 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



      IOFAIL	The plex was detached because 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.

      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.

      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.

      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.

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



				    - 3 -	  Formatted:  August 2, 2006






 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



		the volume will remove 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
      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.

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

      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.

      REMOVED	A physical disk used by one of the subdisks in the plex was
		removed through administrative action with vxdg -k rmdisk.

      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



				    - 4 -	  Formatted:  August 2, 2006






 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



		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:

      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.

      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.

      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 (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.





				    - 5 -	  Formatted:  August 2, 2006






 vxinfo(1M)			  VxVM 3.5			  vxinfo(1M)
				 1 Jun 2002



 FILES
      /usr/lib/vxvm/type/usetype/vxinfo
				    The utility that performs vxinfo
				    operations for a particular volume usage
				    type.

 EXIT CODES
      The vxinfo utility exits with a non-zero status if the attempted
      operation fails.	A non-zero 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(1M) for a list of standard exit codes.

 SEE ALSO
      vxassist(1M), vxintro(1M), vxmend(1M), vxplex(1M), vxsd(1M), vxvol(1M)






































				    - 6 -	  Formatted:  August 2, 2006