*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->Tru64 Unix man pages -> voldiskadd (8)              



NAME    [Toc]    [Back]

       voldiskadd - Adds one or more disks for use with the Logical
 Storage Manager

SYNOPSIS    [Toc]    [Back]

       /usr/sbin/voldiskadd disk-address-list

DESCRIPTION    [Toc]    [Back]

       The voldiskadd interactive utility sets up new disks  that
       are added to the system after the initial system installation
 and configures the disks for use by the Logical Storage
  Manager.  A  valid  disk label must exist on the disk
       before using the voldiskadd utility.

       One or more disks may be specified using  a  disk-addresslist.
  Disk  addresses in the list have the form dskn (for
       the entire disk) or dsknp (for a specific partition). When
       specifying  multiple  disks,  use a space between entries.
       Disk address names relate directly to device names in  the
       /dev/disk directory.

       For  example,  the  following  are  valid voldiskadd diskaddress-list
 specifications: #  voldiskadd  dsk1  #  voldiskadd
 dsk2 dsk3a

       The  file  /etc/vol/disks.exclude  may  be used to exclude
       disks from use by voldiskadd. Each line of the file specifies
 the name of a disk to exclude (for example, dsk5).

       The  voldiskadd  utility prompts you for a disk group name
       and disk media name for the disks. If you  specify  a  new
       disk  group  name,  that disk group is created for the new
       disks. If you do not specify a disk group name, the  disks
       are  left  as unassigned replacement disks for future use.
       If you specify  an  existing  disk  group  name,  you  are
       prompted  for  whether  the  disks should be designated as
       spares for the disk group.

       If a disk is found to already contain non-Logical  Storage
       Manager  partitioning,  you  are  asked  whether  the disk
       should be encapsulated. Encapsulation turns each partition
       of  the  disk into a volume. Encapsulate a disk if it contains
 file systems or data that should not be overwritten.
       If  you  do not want to encapsulate the disk, you can initialize
 it as a new disk for use by  the  Logical  Storage
       Manager. For new disks, all space on the disk becomes free
       space in the disk's disk group.

       Context-sensitive help is available  at  every  prompt  by
       typing  ?.  You  can also enter list to get information on
       available target disks for an operation.

       The voldiskadd  utility  supports  the  following  general
       classes  of  actions:  Initializing  a  disk with reserved
       regions and partitions.

              Disk initialization is performed by  calling  voldisksetup
  command.   Adding  a  disk to an existing
              disk group.

              You can add disks to disk groups  independently  of
              initializing  disks,  to add a disk's storage space
              to a disk group's free space  pool.  The  volassist
              command  may  subsequently  allocate from that free
              space.  You can also add the disk as  a  hot  spare
              device.   Creating  new disk groups in which to add
              new disks.

              If no disk group exists for adding disks,  you  can
              create  a new disk group.  Encapsulating disks that
              have existing contents.

              This is the default action for disks  that  do  not
              have a valid, existing Logical Storage Manager private
 region, but that do have a disk label.  Encapsulation
  is performed by calling volencap.  Reconnecting
 a drive that was temporarily  inaccessible.

              This situation is detected automatically, by noting
              that the specified drive has a disk ID that matches
              a  disk  media  record with no currently associated
              physical disk. After reconnection, any stale plexes
              referring  the disk are reattached, and any stopped
              volumes referring  the  disk  are  restarted.  This
              reattach  action is performed by calling the volrecover

ERRORS    [Toc]    [Back]

       You may receive the  following  messages  when  using  the
       voldiskadd command:

       Initialization   of  disk  device  special-device  failed.
       Error: special-device or an overlapping partition is open.

       This message indicates that the partition you specified or
       an overlapping partition on the disk is actively  in  use.
       The  partition could be a mounted UFS or AdvFS filesystem,
       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.

       Would you like to continue?? [y,n,q,?] (default: n)

       This message indicates that the fstype of a  partition  or
       an  overlapping  partition  is  set in the disk label. The
       voldiskadd command prints this message to warn that a disk
       partition may have valid data that could be destroyed.

       If  you  are  sure  that  the disk partition does not have
       valid data and that the partition can be added to LSM, you
       can  ignore  the  warning  message  by  entering  y at the
       prompt. The voldiskadd command will proceed to  initialize
       the disk partition and add it to LSM.

FILES    [Toc]    [Back]

       A list of disks to exclude from use by voldiskadd.

SEE ALSO    [Toc]    [Back]

       disklabel(8),   volassist(8),  voldisk(8),  voldiskadm(8),
       voldisksetup(8), voldg(8), volintro(8)

[ Back ]
 Similar pages
Name OS Title
voldisk Tru64 Defines and manages Logical Storage Manager disks
voldisksetup Tru64 Sets up a disk for use with the Logical Storage Manager (LSM)
volsave Tru64 Saves a Logical Storage Manager (LSM) configuration
volmake Tru64 Create Logical Storage Manager objects
vol_pattern Tru64 Logical Storage Manager (LSM) search specifications
vold Tru64 Logical Storage Manager configuration daemon
volplex Tru64 Perform Logical Storage Manager operations on plexes
volsd Tru64 Perform Logical Storage Manager operations on subdisks
volprint Tru64 Displays records from the Logical Storage Manager configuration
volnotify Tru64 Displays Logical Storage Manager configuration events
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service