*** UNIX MANUAL PAGE BROWSER ***

volinfo(8) System Manager's Manual volinfo(8) NAME volinfo - Print accessibility and usability of volumes SYNOPSIS /usr/sbin/volinfo -g diskgroup -U usetype -o useopt [ volume ... ] 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, 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 volintro(8). A specific disk group can be forced with -g diskgroup. OPTION The following options are recognized: Write 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. Report the name and condition of each plex in each re- ported volume. 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 re- sult in a failure message for all named volumes that do not have the indicated usage type. 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 speci- fied, the disk group defaults to rootdg. 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 volinfo utility reports the following conditions for volumes: A volume startall operation would likely succeed in starting the volume. 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. The volume has been started and can be used. The volume has been started but is not opera- tionally accessible. This condition may result from errors that have occurred since the volume was started, or may be a result of adminis- trative actions, such as voldg -k rmdisk. OUTPUT FORMAT Summary reports for each volume are printed in one-line output records. The volume output line consists of blank-separated fields for the vol- ume name, volume condition, and the type of the volume. The following example shows the volume summary: bigvol fsgen Startable vol2 fsgen Startable brokenvol gen Unstartable The output format for each plex is a one-line output record consisting of blank-separated fields for the plex name and the plex condition, as a usage-type-dependent string. The plex records are indented from the 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 volinfo utility. The fsgen and gen usage types do not support any op- tions passed in with -o. Plex conditions (reported with -p) can be one of the following: No physical disk was found for one of the subdisks in the plex. This im- plies 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 re- moved 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 associated 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 current 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 volas- sist 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. A volassist snap- start operation completed the process of attaching the plex. It is a candidate for selection 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 opera- tion 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. Volume conditions for these usage types are reported as follows: This condition is reported if the volume is not enabled and if any of the plexes have a reported condition of ACTIVE or CLEAN. This condition is reported if the volume is not enabled, but the volume does not meet the criteria for being Startable. 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). This condition is reported if the volume is en- abled, but the volume does not meet the criteria for being Started. FILE The utility that performs volinfo operations for a particular volume usage type. 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. RELATED INFORMATION volintro(8), volassist(8), volmend(8), volplex(8), volsd(8), volume(8). delim off volinfo(8)