vxdisksetup(1M) VxVM 3.5 vxdisksetup(1M)
1 Jun 2003
NAME [Toc] [Back]
vxdisksetup, vxdiskunsetup - configure a disk for use with VERITAS
Volume Manager
SYNOPSIS [Toc] [Back]
/etc/vx/bin/vxdisksetup [-iB] disk_device_address [ attribute...]
/etc/vx/bin/vxdiskunsetup [-C] disk_device_address...
DESCRIPTION [Toc] [Back]
The vxdisksetup command configures the disk for use by VERITAS Volume
Manager (VxVM). vxdisksetup is called by the vxdiskadd command as
part of initial disk configuration. It is not typically necessary to
call this command directly. vxdisksetup creates a VERITAS Volume
Manager private configuration region and public region for allocating
subdisks.
The vxdiskunsetup command reverses the configuration done by
vxdisksetup and makes the specified disks unusable by VxVM.
vxdiskunsetup can be applied only to VxVM-initialized disks that are
not in use within an imported disk group.
The disk_device_address argument passed to vxdisksetup or
vxdiskunsetup directs the command to the disk being operated upon.
The address should be provided in the form c#t#d#, which define a
controller number (c#), a SCSI target ID (t#), and a SCSI logical unit
number (d#). Each number is specified in decimal and can be multiple
digits. If the disks are named using the enclosure based naming
scheme, the address usually takes the form enclosurename_diskno. The
name must reference a valid disk under the /dev/vx/rdmp directory.
The vxdiskunsetup command operates by removing the public and private
regions that were created by the last invocation of vxdisksetup on the
specified disks. After this operation, those disks are converted from
the online to the online invalid state (as displayed by vxdisk list).
The command does not operate on disks that are active members of an
imported disk group.
Note: When vxdisksetup is executed on an HP IPF (IA64) system, the
target disk is either configured or deconfigured as an EFI partitioned
disk. The action that is taken depends on whether the -B option is
specified, and whether the disk is already formatted as an EFI
partitioned disk:
+ If the -B option is specified, and the disk is not already
formatted as an EFI disk, the idisk(1M) utility is called to
format the disk as an EFI partitioned disk. The partitioning
creates an EFI header in the first 1K block, a 100MB partition
(or slice) 1, and partition 2 (the HP-UX partition) on the
remainder of the disk. If the vxbootsetup(1M) command is
subsequently used to configure the disk as a boot disk, partition
- 1 - Formatted: January 24, 2005
vxdisksetup(1M) VxVM 3.5 vxdisksetup(1M)
1 Jun 2003
1 is populated with an EFI file system, which contains the boot
programs that are needed by an HP IPF system, and the HP-UX
partition (partition 2) is set up as a logical simple VxVM disk
with the same layout as a non-EFI disk. When vxdisksetup has
completed setting up an EFI disk, the resulting disk must be
addressed using the s2 suffix to select the logical simple VxVM
disk.
+ If the -B option is not specified and the target disk is
currently formatted as an EFI partitioned disk, any EFI
formatting is destroyed, and the disk is initialized as a non-EFI
partitioned disk.
OPTIONS [Toc] [Back]
-B Initializes the VERITAS Volume Manager private region to
begin at block number 2144. This block is designated as the
private region offset for a VERITAS Volume Manager root
disk. Without this option, the private region is
initialized to start at the default block number 128.
-C vxdiskunsetup usually does not operate on disks that appear
to be imported by some other host (for example, a host that
shares access to the disk). In this case, the -C option can
be specified to force de-configuration of the disk,
effectively removing the host locks that were detected by
vxdiskunsetup.
-i Writes a disk header to the disk, making the disk directly
usable (as a new disk in a disk group, for example).
ATTRIBUTES [Toc] [Back]
You can specify attributes to affect the layout strategy used by
vxdisksetup.
CAUTION: Be very careful when using these attributes as they can
render a disk unusable by VxVM.
config Sets up kernel logs or configuration databases on the disk.
config is the converse of the noconfig attribute and is the
default. config is ignored unless the -i option is
specified.
noconfig Prevents setting up kernel logs or configuration databases
on the disk. The size of the default private region is set
to 160 blocks, which is the minimum allowed private region
size. noconfig is ignored unless the -i option is
specified.
old_layout
When used with the -i option, creates a private region with
a layout that is compatible with VxVM releases prior to
- 2 - Formatted: January 24, 2005
vxdisksetup(1M) VxVM 3.5 vxdisksetup(1M)
1 Jun 2003
release 3.2. This attribute may be used to initialize a
disk that is intended to replace a failed disk that was
initialized under VxVM before release 3.2.
Note: This attribute assumes a private region size of 1024
blocks. To specify a different private region size, use the
privlen attribute as shown in the EXAMPLES section.
privlen=length
Specifies the length of the private region of the disk. The
default size of this area is 1024 blocks. The maximum
possible size of the private region is 524288 blocks.
privoffset=offset
Indicates the sector offset of the private region on the
disk. The default value for the private region offset is
block number 128 for non-boot disks and block number 2144
for boot disks.
publen=length
Specifies the length of the public region of the disk. This
defaults to the size of the disk minus the private area on
the disk.
puboffset=offset
Sets the offset on the disk where the public region starts.
This defaults to the end of the private region unless the
private region is moved from the beginning of the disk, in
which case the public region offset defaults to following
the private region.
EXAMPLES [Toc] [Back]
To initialize a disk for regular use, enter:
/etc/vx/bin/vxdisksetup -i c2t1d0
To initialize a disk for normal use, but set the private region size
to 2500 KB instead of the default size of 1024 blocks, enter:
/etc/vx/bin/vxdisksetup -i c2t1d0 privlen=2500k
Force deconfiguration of a VxVM-initialized disk, c0f4d0:
/etc/vx/bin/vxdiskunsetup -C c0t4d0
Initialize a disk with a private region size of 1024 blocks that is
compatible with VxVM 3.1:
- 3 - Formatted: January 24, 2005
vxdisksetup(1M) VxVM 3.5 vxdisksetup(1M)
1 Jun 2003
/etc/vx/bin/vxdisksetup -i c3t11d0 privlen=1024 old_layout
SEE ALSO [Toc] [Back]
vxdisk(1M), vxdiskadd(1M), vxintro(1M)
- 4 - Formatted: January 24, 2005 [ Back ] |
