lsmsetup man page on DigitalUNIX

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

volsetup(8)							   volsetup(8)

NAME
       volsetup,  lsmsetup - Initializes Logical Storage Manager (LSM) by cre‐
       ating the rootdg disk group

SYNOPSIS
       /usr/sbin/volsetup [-c] [-o force] [-n num]  [-s]  [diskname  |	parti‐
       tion...] [attribute...]

OPTIONS
       The following options are recognized: Clears the lock protecting multi‐
       ple nodes in a cluster from simultaneously running  the	volsetup  com‐
       mand.  After clearing the lock, it is taken out on behalf of the initi‐
       ating node.  Specifies the approximate number of disks to be managed by
       LSM. This option is currently ignored and is only provided for compati‐
       bility with existing scripts.   Forces  re-initialization  if  LSM  has
       already been initialized.  Synchronizes a node with cluster members.

DESCRIPTION
       The  volsetup  script is an interactive script that should be run after
       installing LSM. The diskname or partition parameter specifies the  name
       of  at  least  one  disk or partition to be used in creating the rootdg
       disk group.  If no disk or partition name is given on the command line,
       the volsetup script prompts for this information.

       If more than one disk name or partition name is given as input, all the
       disks and partitions are added to the rootdg disk group.

       The -o force option can be used to remove an existing LSM configuration
       and reinitialize LSM.

       The  volsetup  script  starts the vold daemon and one voliod daemon per
       CPU by default. After volsetup has been run, LSM is fully functional.

       To configure LSM in a TruCluster Version 5.0 multi-member cluster,  run
       the  volsetup  command  from  one  of  the  cluster members and run the
       volsetup -s on the other cluster members.  If  additional  members  are
       later  added to the cluster with the clu_add_member utility, do not run
       volsetup -s command on the new member. The clu_add_member utility auto‐
       matically synchronizes LSM on the new node.

ATTRIBUTES
       The following attributes can be specified to affect the layout strategy
       used by volsetup: Specifies the length of the public area to create  on
       the disk.  This defaults to the size of the disk minus the private area
       on the disk.  Specifies the length of the private area to create on the
       disk.  The default is 4096 sectors.  Specifies the number of configura‐
       tion copies and log copies to be initialized on the disk. The number of
       configuration copies will be the same as the number of log copies. This
       defaults to 1.  Specifies the length in sectors of  each	 configuration
       copy.  The default values are calculated based on the value of nconfig.
       Specifies the length in sectors of each log copy.  The  default	values
       are calculated based on the value of nconfig.  Specifies a user-defined
       comment.

ERRORS
       You may receive the following messages when using the volsetup command.
       LSM initialization fails if none of the disks specified can be initial‐
       ized by LSM.

       The following message indicates that LSM is initialized on the  system.
       To  reinitialize	 LSM,  use the -o force option, which removes previous
       LSM configuration.  A previous LSM configuration exists (err=22).   Use
       the "-o force" option to reinitialize LSM.  Stop.

       The  following  message	indicates  that you tried to initialize an LSM
       disk on a partition or on a disk that is actively in use. The partition
       could  be  a  mounted UFS or AdvFS filesystem that is initialized as an
       LSM disk or used as a swap device.  special-device  or  an  overlapping
       partition is open.

       The  following  message	indicates  that you tried to initialize an LSM
       disk on a partition that is not currently in active use, but is	marked
       for  use	 in the disk label's partition map. For example, the partition
       may be part of a UFS filesystem (4.2BSD) or an AdvFS domain.   special-
       device  is  marked in use for fstype in the disklabel.  If you continue
       with the operation you can possibly  destroy  existing  data  CONTINUE?
       [y/n]

       If  you know that the partition you specified to volsetup does not con‐
       tain any data, you can choose to override the warning.  In  this	 case,
       the  fstype in the disk label is modified to an LSM fstype such as LSM‐
       simp, LSMpubl or LSMpriv. The exact fstype depends on whether a disk or
       a partition is given as an argument to voldisksetup.

       Note that you can use the command disklabel -s to set the fstype in the
       disk label to unused for partitions that do not contain any valid data.
       See disklabel(8) for more information.

       The following message indicates that the partition you specified is not
       marked for use, but other,  overlapping	partitions  on	the  disk  are
       marked  for  use.  Partition(s) which overlap special-device are marked
       in use.	If you continue with the operation you	can  possibly  destroy
       existing data.  CONTINUE? [y/n]

       If  you	override this warning, the fstype in the disk's label is modi‐
       fied. The partition you specified to volsetup will be marked as in  use
       by LSM and all overlapping partitions will be marked UNUSED.

       The  following  examples illustrate these messages: Initializing an LSM
       disk on a partition that is open and actively in use:

	      # /usr/sbin/volsetup dsk11c

	      dsk11c or an overlapping partition is open.  Initializing an LSM
	      sliced  disk  on	a disk which has partition g marked for use by
	      UFS (4.2BSD):

	      # /usr/sbin/volsetup dsk11

	      /dev/rdisk/dsk11g is marked in use for 4.2BSD in the  disklabel.
	      If  you  continue	 with  the  operation you can possibly destroy
	      existing data.  CONTINUE? [y/n]

	      Partition g of disk dsk11 is marked for use by UFS (4.2BSD).  If
	      UFS  is not actively using this partition and the partition does
	      not contain any data, you may want to override this warning,  by
	      answering	 y.   In this case, partition g will be marked as LSM‐
	      publ and partition h will be  marked  as	LSMpriv	 in  the  disk
	      label.   Initializing  an	 LSM  simple disk on a partition whose
	      overlapping partitions are marked for use:

	      # /usr/sbin/volsetup dsk11c

	      Partition(s) which overlap /dev/rdisk/dsk11c are marked in  use.
	      If  you  continue	 with  the  operation you can possibly destroy
	      existing data.  CONTINUE? [y/n]

	      Partition c, which is being initialized into LSM,	 is  not  cur‐
	      rently  in use, but other partition(s) which overlap with parti‐
	      tion c are marked in use in the disk label.  If  you  answer  y,
	      partition	 c  on	disk  dsk11 will be marked LSMsimp in the disk
	      label and all partitions that overlap partition c will be marked
	      UNUSED.	Initializing  an  LSM  disk on a disk that has no disk
	      label:

	      # /usr/sbin/volsetup dsk11

	      The disklabel for dsk11 does not exist or is  corrupted.	 Quit‐
	      ting...

	      See disklabel(8) for information on installing a disk label on a
	      disk.

EXAMPLES
       The following is an example of volsetup usage :

       # /usr/sbin/volsetup dsk3 dsk8h

       This will add disk dsk3 and partition dsk8h to the rootdg disk group.

SEE ALSO
       disklabel(8), volintro(8), vold(8), voliod(8)

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