vxdisksetup(1M)

NAME

vxdisksetup, vxdiskunsetup — configure a disk for use with the Volume Manager

SYNOPSIS

/etc/vx/bin/vxdisksetup [-Bi] disk_device_address [ attribute... ]

/etc/vx/bin/vxdiskunsetup [-C] disk_device_address..

DESCRIPTION

The vxdisksetup command configures the disk for use by the Volume Manager. 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 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 the Volume Manager. vxdiskunsetup can be applied only to 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. 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.

OPTIONS

-B: Initializes the Volume Manager private region to begin at block number 2144. This block is designated as the VM private region offset for a VM 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

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 the Volume Manager.

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 80 blocks, which is the minimum allowed private region size. noconfig is ignored unless the -i option is specified.
privlen=length: Specifies the length of the private region of the disk. The default size of this area is 1024 sectors.
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

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 768K instead of the default size of 1 MB, enter:

/etc/vx/bin/vxdisksetup -i c2t1d0 privlen=768 

Force deconfiguration of disk c0t4d0:

/etc/vx/bin/vxdiskunsetup -C c0t4d0 

vxdisksetup(1M)

Technical documentation

» Table of Contents

» Index