Home > Veritas Storage Foundation™ Volume Manager Manual Pages
Table of contents
vxdiskadd - add one or more disks for use with Veritas Volume Manager
The vxdiskadd utility configures disks for use by
Veritas Volume Manager (VxVM).
vxdiskadd prompts the user for
a disk group name and disk name for the disks. If no disk group name
specified, the disks will be left as unassigned
replacement disks for future use. A new disk group may be created that
will become the disks' disk group.
If a disk group is specified for the disks,
the user is prompted for whether the disks should be designated as spares
for the disk group.
For new disks, all space on the disk becomes free space
in the disk's disk group. vxdiskadd interactively allows
initialization to be done for all the disks specified or
allows the user to ask to make the decision for each disk individually.
One or more disks may be specified with a
The basic form of a disk address is
Controller addresses are typically of the form
scsi# for SCSI controllers
or fscsi# for Fibre Channel controllers.
This address may be specified to indicate that all disks on that controller
should be used. For example scsi2 may be used
to specify all disks on SCSI controller 2.
A disk address of the form enclosurename_
indicates that all disks in the specified enclosure are to
be used. For example, enc1_ specifies all disks in the enclosure
More than one disk
address or address pattern may be specified on the command line.
The word all may be used to specify all disks on the system.
names relate directly to device node names in the /dev/vx/dmp and
/dev/vx/rdmp directories. Here are more examples:
all: all disks
scsi3: all disks on controller
hdisk12: a single disk
xyz_0 : a single disk
xyz_ : all disks on the enclosure whose name is xyz
The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and
/etc/vx/enclr.exclude may be used to exclude controllers or disks
from use by vxdiskadd. Each line of cntrls.exclude
specifies the address of a controller to exclude, for example,
scsi2. Each line of disks.exclude specifies a disk to exclude,
for example, hdisk12. Each line of enclr.exclude specifies
the name of an enclosure to exclude, for example, enc0.
All courses of action that do not involve clear failure conditions require
prompts from the user, with defaults supplied as appropriate. Help is made
available at every prompt. Entering ? in response to a prompt displays
a context-sensitive help message.
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.
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
Initialization of a disk with reserved regions
Initialization of the disk is
performed by calling vxdisksetup.
Adding a disk to an existing disk group
This operation can be performed independently of the initialization of the
disk drive. The operation adds the disk to the group so that its
storage is added to the free space pool in that disk group.
utility can subsequently allocate from that free space.
Creation of new disk groups in which to import a new disk
If disks are added that are required to be put into a disk
group that does not exist,
the option of creating the disk group is offered.
Some environments provide guidelines to optimize VxVM's interaction
with intelligent storage systems. If these guidelines are present, VxVM
follows the guidelines when adding disks to disk groups. If the
operation fails due to these guideline(s), you are prompted to use the
force option. The force option ignores any such storage-specific
Specifies the address of controllers to exclude from
Specifies the address of disks to exclude from
Specifies the address of enclosures to exclude from vxdiskadd
EFI disks cannot be added to a disk group that is compatible with
the Cross-platform Data Sharing (CDS) feature, nor can they be formatted
as CDS disks.
Last updated: 28 Jul 2003
Copyright ©2009 Symantec Corporation
All rights reserved.