voldisksetup(8)

Index for
Section 8
Alphabetical
listing for V
Bottom of
page
voldisksetup(8)
NAME
  voldisksetup - Sets up a disk for use with the Logical Storage Manager
  (LSM)

SYNOPSIS
  /usr/sbin/voldisksetup [-i] { diskname... | partition... } [attribute...]

OPTIONS
  The voldisksetup command takes the following option:

  -i  Normally, voldisksetup simply creates partitions for use with the
      Logical Storage Manager.	If the -i (initialize) option is specified, a
      disk header is added and an empty configuration is written on the disk.
      This operation destroys any previous LSM database contents on the disk.

DESCRIPTION
  The voldisksetup command is normally called by the voldiskadd command as
  part of initial disk configuration.

  The voldisksetup utility configures one or more disks for use by the
  Logical Storage Manager. A valid disk label must be installed on the disk
  before calling voldisksetup.

  The diskname and partition parameters specify the physical addresses of one
  or more disks and/or partitions being added to LSM. The format is dskn for
  an entire disk and dsknp for a specific partition, where n is the device
  unit number and p is a partition identifier in the range a through h.

NOTES
  The following options to voldisksetup are for HP internal use only:

  -F  Overrides partition overlap checks.

  -q  Suppresses overlap check messages.

ATTRIBUTES
  The following attributes can be specified to affect the layout strategy
  used by voldisksetup:

  publen=length
      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.

  puboffset=offset or offset=offset
      Specifies the offset from the beginning of the partition containing the
      public region to the beginning of the public region. Use this option if
      it is necessary to skip over some region reserved by the operating
      system.

      This option defaults to 16 for the sliced type. For the simple type,
      the default is the first block past the end of the private region.

  privlen=length
      Specifies the length of the private area to create on the disk. The
      default is 4096 sectors.

  privoffset=offset
      Specifies the offset from the beginning of the partition containing the
      private region to the beginning of the private region.

      This option defaults to 16 for a simple disk on the a or c partition,
      and to 0 for all other disk types.

  noconfig
      Disables the setup of kernel logs and configuration databases on the
      disk. The size of the private area is not changed, but it will not
      contain the normal private data. This attribute is ignored unless the
      -i option was supplied on the command line.

  config
      Enables the setup of kernel logs and configuration databases on the
      disk (default). This attribute is ignored unless the -i option was
      supplied on the command line.

  nconfig=number
      Specifies the number of configuration copies and log copies to be
      initialized on the disk. The default is 1.

  configlen=length
      Specifies the length in sectors of each configuration copy.  The
      default values are calculated based on the value of nconfig.

  loglen=length
      Specifies the length in sectors of each log copy. The default values
      are calculated based on the value of nconfig.

  comment=string
      Specifies a user-defined comment.

ERRORS
  You may receive the following messages when using the voldisksetup command:

       special-device or an overlapping partition is open

  This message indicates that you tried to initialize an LSM disk on a
  partition or a disk that is actively in use. The partition could be a
  mounted UFS or AdvFS file system, initialized as an LSM disk or used as a
  swap device.

       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]

  This 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.

  If you know that the partition you specified to voldisksetup does not
  contain any data, you can choose to override the warning.  In this case,
  the fstype in the disk label will be modified to an LSM fstype such as
  LSMsimp, 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.

       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]

  This message indicates that the partition you specified is not marked for
  use, but other, overlapping partitions on the disk are marked for use. If
  you override this warning, the fstype in the disk's label will be modified.
  The partition you specified to voldisksetup will be marked as in use by LSM
  and all overlapping partitions will be marked UNUSED.

  The following examples illustrate these messages:

   1.  Initializing an LSM simple disk on a partition that is open and
       actively in use:

	    # /usr/sbin/voldisksetup -i dsk11c

	    dsk11c or an overlapping partition is open.

   2.  Initializing an LSM sliced disk on a disk that has partition g marked
       for use by UFS (4.2BSD):

	    # /usr/sbin/voldisksetup -i dsk11

	    /dev/rdsk11g 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 LSMpubl and partition h will
       be marked as LSMpriv in the disk label.

   3.  Initializing an LSM simple disk on a partition whose overlapping
       partitions are marked for use:

	    # /usr/sbin/voldisksetup -i dsk11c

	    Partition(s) which overlap /dev/rdsk11c 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 currently in
       use, but other partition(s) which overlap with partition 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.

   4.  Initializing an LSM disk on a disk that has no disk label:

	    # /usr/sbin/voldisksetup -i dsk11

	    The disklabel for dsk11 does not exist or is corrupted.

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

SEE ALSO
  disklabel(8), volintro(8), voldisk(8), voldiskadd(8)
Index for
Section 8
Alphabetical
listing for V
Top of
page