*** UNIX MANUAL PAGE BROWSER ***

volmend(8) System Manager's Manual volmend(8) NAME volmend - Mend simple problems in configuration records SYNOPSIS /usr/sbin/volmend -g diskgroup -U usetype -o useopt [ -Vfrvps ] clear field name ... /usr/sbin/volmend -g diskgroup -U usetype -o useopt [ -Vfrvp ] fix how name [ arg ... ] /usr/sbin/volmend -g diskgroup -U usetype -o useopt [ -Vfrvp ] off name ... /usr/sbin/volmend -g diskgroup -U usetype -o useopt [ -Vfrvp ] on name ... DESCRIPTION The volmend utility performs various Logical Storage Manager usage- type-specific operations on subdisk, plex, and volume records. The first operand is a keyword that determines the specific operation to perform. The remaining operands specify the configuration objects to which the operation is applied. Each invocation can be applied to only one disk group at a time, due to internal implementation constraints. Any name operands will be used as record names to determine a default disk group, according to the stan- dard disk group selection rules described in volintro(8). A specific disk group can be forced with -g diskgroup. These are the recognized operation keywords: Clear specified utility fields for each named record in the disk group. An option of -v, -p, or -s specifies that the utility operates only on volumes, plexes, or subdisks, respectively. If a record is a volume, or is associated di- rectly or indirectly with a volume, then the clear operation is per- formed according to rules used by the usage type appropriate for that volume. The field operand is a comma-separated list of keywords specify- ing fields to be cleared. Each keyword in the field operand is one of the following: Clear all clearable utility fields. Nor- mally, this clears all of the persistent and non-persistent utility fields. A usage-type utility may choose a different set of fields, as appropriate. Clear all persistent utility fields. Clear all non-persistent (temporary) utility fields. Clear a specific persistent utility field. Clear a specific non-persis- tent utility field. Usage types may implement additional field keywords. A usage type may also limit the set of clear operations that can be per- formed. Change the state of a volume or plex, named by the name operand, in a manner specified by the how string. The meaning of this operation is entirely usage-type specific. This opera- tion applies only to volumes, or to plexes associated with a volume. Usage type rules appropriate for the volume are used to interpret the command. Additional arguments, after name, are interpreted according to rules defined by the usage type. Put the named plexes or volumes into an offline state. This opera- tion can be applied only to volumes, or to plexes associated with a volume. Usage type rules appropriate for the volume are used to perform the operation. Take the named plexes or volumes out of the offline state. This operation can be applied only to volumes, or to plexes associated with a volume. Usage type rules appropriate for the volume are used to perform the opera- tion. OPTIONS The following options are recognized: 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 name operands. Limit the opera- tion to apply to this usage type. Attempts to affect volumes with a different usage type will fail. Pass in usage-type-specific options to the operation. Write a list of utilities that would be called from volmend, along with the arguments that would be passed. The -V per- forms a ``mock run'' so the utilities are not actually called. Force an operation that the Logical Storage Manager considers potentially dangerous or unnecessary. This enables a limited set of additional op- erations. Some operations may be disallowed even with this flag. Op- erate recursively on records associated with the named volume or plex record. Operations applied to a volume will apply to the associated plexes and subdisks. Likewise, operations applied to a plex may be ap- plied to the associated subdisks. Require that name operands name vol- ume records. Require that name operands name plex records. Require that name operands name subdisk records. FSGEN AND GEN USAGE-TYPES The fsgen and gen usage types provide identical semantics for all oper- ations of the volmend utility. These usage types provide the following options as arguments to -o: Force an operation that internal consis- tency checks consider to be questionable. This applies to attempts to use volmend fix empty to uninitialize a volume that has plexes in the ACTIVE state, and also to attempts to disable the last plex, or the last complete (non-sparse) plex, in a volume. This flag is the same as -f. Require that any named plex or subdisk record be associated, di- rectly or indirectly, with a volume named volume. Several vol options can be specified to indicate a list of allowed volume names. Require that any named subdisk record be associated with a plex named plexname. Several plex options can be specified to indicate a list of allowed plex names. Limitations and extensions for the fsgen and gen usage types consist of the following: Keywords supported in the field operands include all standard keywords. In addition, a keyword of the form attnumber can be used to remove locks on a volume for a particular number of concurrent plex attach operations. For example, assume that the following command has been entered: volplex att v1 v1-01 If the above command is aborted by pressing the INTERRUPT key several times (which prevents a clean abort of the operation), you may have to clear the operation with the following commands: /usr/sbin/volmend clear tutil0 v1-01 /usr/sbin/volmend clear att1 v1 /sbin/volplex dis v1-01 Interruption of the above-mentioned volplex att command will display a list of commands to run, which will include the previ- ous list. The number of plexes currently being attached, either directly or as part of a compound operation, is stored in the tutil0 field of the volume record as a string in the form ATTnumber. If the number drops to zero, the tutil0 field is cleared. Some operations on a volume require that the tutil0 field be cleared. The fsgen and gen usage types support the following volmend fix operations: Set the state for the named plex to CLEAN. The as- sociated volume must be disabled, the named plex must be in the STALE state, and the volume must have no additional plexes in the CLEAN state. A volume is not startable if one plex is in the CLEAN state and some plexes are in the ACTIVE state. Thus, several /usr/sbin/volmend fix operations are normally used in conjunc- tion to set all plexes in a volume to STALE and then to set one plex to CLEAN. A volume start operation will then enable the CLEAN plex and recover the STALE plexes by copying data from the one CLEAN plex. Set the state for the named plex to ACTIVE. The state for the volume is set to SYNC. The associated volume must be disabled, and the named plex must be in the STALE state. When starting a volume in the SYNC state, all ACTIVE plexes are enabled and are synchronized to have the same contents using a special read/write-back recovery mode. Any STALE plexes are then recovered by copying data from the ACTIVE plexes. Set the state for the named plex to STALE. The associated volume must be disabled, and the named plex must be ACTIVE or CLEAN. This operation names plexes that will be recovered by copying data from other plexes by a volume start operation. This operation sets the named volume and all of its associated plexes to the EMPTY state. The volume can then be re-initialized using volume start or any of the volume init operations. This operation re- quires that the volume be disabled. The fsgen and gen usage types allow volumes and plexes to be specified as operands to /usr/sbin/volmend off. A volume can be named only if -r is used to specify recursion, and is applied to all plexes in the vol- ume. Offlining a plex disables the plex and sets its state to OFFLINE. Offlining the last enabled read-write plex in a volume, or the last complete plex (if there are additional sparse plexes) will normally fail unless -f is specified. Applying this operation to a volume also disables the volume, and does not require use of -f. If a volume is disabled, then the checks for the last plex or the last complete plex are performed on the set of ACTIVE and CLEAN plexes, rather than on enabled read-write plexes. An offline state for a plex can be cleared with /usr/sbin/vol- mend on. Alternatively, an offline plex can be reattached with volplex att. The fsgen and gen usage types allow volumes and plexes to be specified as operands to /usr/sbin/volmend on. The /usr/sbin/volmend on operation applied to a plex will change the OFFLINE state for a plex to STALE, allowing the plex to be re- covered by the next volume start or volume startall. Applying /usr/sbin/volmend on to a volume will change the state for all associated OFFLINE plexes to STALE. FILES The utility that performs volmend operations for a particular volume usage type. EXIT CODES The 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 fur- ther execution of the utility. See volintro(8) for a list of standard exit codes. RELATED INFORMATION volintro(8), volplex(8), volume(8). delim off volmend(8)