volinfo man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

volinfo(8)							    volinfo(8)

NAME
       volinfo - Print accessibility and usability of volumes

SYNOPSIS
       /usr/sbin/volinfo  [-Vp]	 [-g diskgroup] [-U usetype] [-o useopt] [vol‐
       ume...]

OPTIONS
       The following options are recognized: Writes a list of  utilities  that
       would  be  called  from volinfo, along with the arguments that would be
       passed. The -V performs a ``mock run'' so the utilities are  not	 actu‐
       ally  called.   Reports	the  name  and	condition of each plex in each
       reported volume.	 Specifies the usage type for  the  operation.	If  no
       volume operands are specified, the output is restricted to volumes with
       this usage type. If volume operands are specified, this will result  in
       a  failure message for all named volumes that do not have the indicated
       usage type.  Specifies 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.	 Passes in usage-type-specific options
       to the operation. This option is currently unsupported.

DESCRIPTION
       The volinfo 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, 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 volintro(8). A specific disk group can be
       forced with -g diskgroup.

   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 vol‐
       ume name, volume usage type, and volume	condition.  Each  plex	output
       line  consists of blank-separated fields for the plex name and the plex
       condition.

       The following example shows the volume summary:

       #  volinfo  bigvol	   fsgen     Startable	vol2		 fsgen
       Started brokenvol      gen      Unstartable

       The  following  example	shows the  plex summary, with the plex records
       accompanied by their volume records:

       # volinfo -p vol	  bigvol	  fsgen	    Startable  plex  bigvol-01
       ACTIVE  vol  vol2	   fsgen    Started plex vol2-01	ACTIVE
       vol  brokenvol	   gen	    Unstartable

   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.

       Volume conditions for the fsgen and gen usage  types  are  reported  as
       follows: The volume is not enabled and at least one of the plexes has a
       reported condition of ACTIVE or CLEAN.	A  volume  startall  operation
       would  likely succeed in starting a volume in this condition.  The vol‐
       ume is not enabled and fails to meet the criteria for being  Startable.
       A  volume in this condition is not started and may be configured incor‐
       rectly or prevented  from  automatic  startup  (with  volume  startall)
       because	of  errors  or other conditions.  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). A
       volume in this condition has been started and can be used.  The	volume
       is  enabled,  but  the  volume  does  not  meet	the criteria for being
       Started. A volume in this condition has been started, but is inaccessi‐
       ble  because of errors that have occurred since the volume was started,
       or because of administrative actions, such as voldg -k rmdisk.

       Volume conditions for volumes of the raid5 usage type include the  fol‐
       lowing conditions used for the fsgen and gen usage types:

       Startable, Unstartable, Started, Started Unusable

       Additional  volume conditions for raid5 volumes are: The RAID-5 plex of
       the volume is in degraded mode due to the unavailability of  a  subdisk
       in  that	 plex.	 Some  of  the	parity in the RAID-5 plex is stale and
       requires recovery.

   Plex Conditions
       The following plex conditions (reported with -p) are reported  for  the
       fsgen  and  gen	usage types: 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.  A physical disk  used  by
       one  of	the  subdisks  in  the plex was removed through administrative
       action with voldg -k rmdisk.  The plex  was  detached  from  use	 as  a
       result  of  an  uncorrectable I/O failure on one of the subdisks in the
       plex.  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	 volplex  det.
       The  plex  contains  valid  data	 and  the  volume was stopped cleanly.
       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.
       The plex was disabled using the volmend off  operation.	 The  plex  is
       part  of a volume that has not yet been initialized.  The plex is asso‐
       ciated temporarily as part of a current operation, such as  volplex  cp
       or  volplex  att.  A  system reboot or manual starting of a volume will
       dissociate the plex.  The plex was created for temporary use by a  cur‐
       rent  operation.	  A  system reboot or manual starting of a volume will
       remove the plex.	 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.  The plex is being
       attached as part of a backup operation by the volassist snapstart oper‐
       ation. When the attach is complete, the condition will change to	 SNAP‐
       DONE.  A system reboot or manual starting of the volume will remove the
       plex and all of its subdisks.  A	 volassist  snapstart  operation  com‐
       pleted  the process of attaching the plex. It is a candidate for selec‐
       tion by the volassist snapshot operation. A  system  reboot  or	manual
       starting	 of  the  volume will remove the plex and all of its subdisks.
       The plex is being attached as part of a backup operation by the volplex
       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.  A volassist snapstart operation completed
       the process of attaching the plex. It is a candidate for	 selection  by
       the  volplex  snapshot operation. A system reboot or manual starting of
       the volume will dissociate the plex.

       Plexes of raid5 volumes can be either  data  plexes  (that  is,	RAID-5
       plexes) or log plexes.

       Plex  conditions for RAID-5 plexes and log plexes include the following
       conditions used for the fsgen and gen usage types:

       NODAREC, REMOVED, IOFAIL, CLEAN, ACTIVE, OFFLINE

       RAID-5 plexes can have these  additional	 conditions:  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.   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  fur‐
       ther  failures  could case data loss.  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 this additional condition: The
       contents of the plex are not usable as logging data.

EXIT CODES
       The volinfo utility exits with a nonzero status if the attempted opera‐
       tion  fails.  A	nonzero	 exit  code is not a complete indicator of the
       problems encountered, but rather denotes the first condition that  pre‐
       vented  further execution of the utility. See volintro(8) for a list of
       standard exit codes.

SEE ALSO
       volintro(8), volassist(8), volmend(8), volplex(8), volsd(8), volume(8)

								    volinfo(8)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net