unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Page:
Section:
Apropos / Subsearch:
optional field



volmend(8)							   volmend(8)



NAME

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

OPTIONS

  The following	options	are recognized:

  -g diskgroup
      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
      name operands.

  -U usetype
      Limits the operation to apply to the specified usage type.  Attempts to
      affect volumes with a different usage type will fail.

  -o useopt
      Passes in	usage-type-specific options to the operation.

      The fsgen, gen, and raid5	usage types support the	following useopt
      argument:

      force
	  Forces an operation that internal consistency	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.

      The fsgen	and gen	usage types support the	following additional useopt
      arguments:

      vol=volume
	  Requires that	any named plex or subdisk record be associated,
	  directly or indirectly, with a volume	named volume.  Several vol
	  options can be specified to indicate a list of allowed volume
	  names.

      plex=plexname
	  Requires 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.

  -V  Displays a list of utilities that	would be called	from volmend, along
      with the arguments that would be passed. The -V option performs a
      ``mock run'' so the utilities are	not actually called.

  -f  Forces an	operation that the Logical Storage Manager considers poten-
      tially dangerous or unnecessary. This enables a limited set of addi-
      tional operations	that would normally not	be allowed. Some operations
      may be disallowed	even with this flag.

  -r  Operates recursively on records associated with the named	volume or
      plex record. Operations applied to a volume will apply to	the associ-
      ated plexes and subdisks.	Likewise, operations applied to	a plex may be
      applied to the associated	subdisks.

  -v  Requires that name operands name volume records.

  -p  Requires that name operands name plex records.

  -s  Requires that name operands name subdisk records.

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 remain-
  ing 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 standard
  disk group selection rules described in volintro(8). A specific disk group
  can be forced	with -g	diskgroup.

  These	are the	recognized operation keywords for volmend:

  clear	field name
      Clears 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 directly	or indirectly with a volume, the
      clear operation is performed according to	rules used by the usage	type
      appropriate for that volume.

      The field	operand	is a comma-separated list of keywords specifying
      fields to	be cleared. Valid keywords for the field operand are:

      all Clears all clearable utility fields. Normally, this clears all of
	  the persistent and non-persistent utility fields. A usage-type
	  utility may choose a different set of	fields,	as appropriate.

      putil
	  Clears all persistent	utility	fields.

      tutil
	  Clears all non-persistent (temporary)	utility	fields.

      putil0, putil1, or putil2
	  Clears a specific persistent utility field.

      tutil0, tutil1, or tutil2
	  Clears a specific non-persistent utility field.

	  For the fsgen	and gen	usage types, 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 additional field
      keyword:

      attnumber
	  Removes locks	on a volume for	a particular number of concurrent
	  plex attach operations.

	  This operation can be	used to	clear a	volplex	att operation that
	  fails	to terminate cleanly. For example, suppose that	the following
	  command was issued and then abruptly terminated by pressing the
	  INTERRUPT key	(or equivalent):
	       volplex att v1 v1-01

	  The volplex command would respond to the interruption	by displaying
	  a list of commands to	run. For this example, you would run the fol-
	  lowing commands from the list:
	       volmend clear tutil0 v1-01
	       volmend clear att1 v1
	       volplex dis v1-01




  fix how name [arg...]
      Changes the state	of a volume, plex, or subdisk named by the name
      operand, in a manner specified by	the how	string.	The meaning of this
      operation	is entirely usage-type specific. This operation	applies	to
      volumes, or to plexes associated with a volume, or to subdisks of	a
      raid5 volume. Usage-type rules appropriate for the volume	are used to
      interpret	the command. Additional	arguments, after name, are inter-
      preted according to rules	defined	by the usage type.

      The fsgen, gen, and raid5	usage types support the	following volmend fix
      operations:

      clean plex
	  Sets the state for the named plex to CLEAN.  The associated 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 volmend fix
	  operations are normally used in conjunction 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.

      active plex
	  Sets 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 spe-
	  cial read/write-back recovery	mode. Any STALE	plexes are then
	  recovered by copying data from the ACTIVE plexes.

      stale plex
	  Sets 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.

      empty volume
	  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 requires that the
	  volume be disabled.

      The raid5	usage type supports the	following additional volmend fix
      operation:

      unstale subdisk
	  Clears any flags indicating that a subdisk of	a RAID-5 plex is
	  invalid. This	will prevent the data on the subdisk from being
	  recovered when the volume is started.

  off name
      Puts the named plexes or volumes into an 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
      operation.

      The fsgen	and gen	usage types allow volumes and plexes to	be specified
      as operands to volmend off. A volume can be named	only if	-r is used to
      specify recursion, and is	applied	to all plexes in the volume. Offlin-
      ing 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, the checks for the last plex or the last	com-
      plete 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 volmend on. Alterna-
      tively, an offline plex can be reattached	with volplex att.

  on name
      Takes 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	per-
      form the operation.

      The fsgen	and gen	usage types allow volumes and plexes to	be specified
      as operands to volmend on. The volmend on	operation applied to a plex
      will change the OFFLINE state for	a plex to STALE, allowing the plex to
      be recovered by the next volume start or volume startall.	Applying vol-
      mend on to a volume will change the state	for all	associated OFFLINE
      plexes to	STALE.

EXIT CODES

  The volmend 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 further
  execution of the utility. See	volintro(8) for	a list of standard exit
  codes.




FILES

  /sbin/lsm.d/usetype/volmend
      The utility that performs	volmend	operations for a particular volume
      usage type.

SEE ALSO

  volintro(8), volplex(8), volume(8)