Home > Veritas Storage Foundation™ Volume Manager Manual Pages
VXDISKADD (1M) |
|
Maintenance Commands |
Table of contents
vxdiskadd - add one or more disks for use with Veritas Volume Manager
vxdiskadd disk_address_pattern_list
The vxdiskadd utility configures disks for use by
Veritas Volume Manager (VxVM).
Disks must already have been formatted, and have a valid, recognized partition
table. Currently, DOS and SOLARIS partitioning is supported.
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.
If a disk is found to already contain partitioning not set up by VxVM,
the user will be asked whether the disk should be encapsulated.
Encapsulation will turn each partition of the disk
into a volume. A disk should be encapsulated if it contains file systems
or data that should not be overwritten. If encapsulation is not desired
for a disk, the disk can be initialized as a new disk for use by VxVM.
For new disks, all space on the disk becomes free space
in the disk's disk group. vxdiskadd interactively allows
encapsulation or
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
disk_address_pattern_list.
The basic form of a disk address is
is sdc or hdc,
but others may be supported.
Disk address names relate directly to device node names.
The
/etc/vx/disks.exclude
file may be used to exclude disks from use by
vxdiskadd.
Each line of
disks.exclude
specifies
a disk to exclude.
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.
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
vxrecover
utility.
-
Encapsulation of disks that have existing contents
-
This is the
default action for disks that do not have a valid, existing
Veritas Volume Manager private region, but that do have a VTOC or EFI label.
Encapsulation is performed by calling vxencap.
-
Initialization of a disk with reserved regions and partitions
-
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.
The
vxassist
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
guidelines.
-
/etc/vx/disks.exclude
-
Specifies the address of disks to exclude from
vxdiskadd operations.
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.
vxassist(1M),
vxdisk(1M),
vxdiskadm(1M),
vxdisksetup(1M),
vxencap(1M),
vxintro(1M),
vxrecover(1M)
Last updated: 17 Jul 2008
Copyright ©2009 Symantec Corporation
All rights reserved.