|
|
|
|
|
vxapslice - manage an area of disk for use by an AP database
/etc/vx/bin/vxapslice [-g diskgroup] [-o offset] [-p partition] [-s size] accessname | medianame
/etc/vx/bin/vxapslice -d [-g diskgroup] accessname | medianame
/etc/vx/bin/vxapslice -l [-g diskgroup] accessname | medianame
/etc/vx/bin/vxapslice -r [-g diskgroup] [-p partition] accessname | medianame
The vxapslice utility in Veritas Volume Manager (VxVM) allows you to reserve an area on a disk for an Alternate Pathing (AP) database (APDB).
In the first usage form shown in the SYNOPSIS section, vxapslice removes an area of disk from Veritas Volume Manager control, creates a slice in this area by adding an entry to the disk's partition table, and creates a Veritas Volume Manager subdisk that is mapped to the slice. Finally, vxapslice displays the device associated with the newly created slice.
After it has been created, the subdisk associated with the slice is not usable by VxVM, and cannot be moved or associated. AP commands such as apdb are used to create, administer, or delete an AP database located on the slice.
Sufficient free space, that is not already in use by any subdisk, must be available to reserve the area on the disk where the slice is to be created. Additionally, vxapslice cannot reserve the area if an area is already reserved for the disk.
In the second usage form (-d option), vxapslice returns the area of the disk reserved for an AP database to Veritas Volume Manager control, and deletes the corresponding subdisk and partition table entry for the slice (if any).
In the third usage form (-l option), vxapslice displays information about any existing area of a disk that is reserved for use as an AP database, and about any associated device. If no such device exists, as might happen if you have replaced the physical disk, vxapslice informs you that the AP database area needs either to be repaired or to be deleted.
In the fourth usage form (-r option), vxapslice attempts to repair the area of the disk that is reserved for an AP database. This may fail if the slice cannot be created for some reason, such as the geometry of a replacement disk not being the same as that of the original disk. If it succeeds, vxapslice adds an entry for the slice to the disk's partition table.
accessname is a system-dependent device name that identifies the physical disk, such as c0t1d0s2. Alternatively, medianame identifies a disk by its VM disk name, such as disk01.
Releases an area of the disk reserved for use by an AP database, and deletes any corresponding slice from the partition table.
Specifies the disk group to which fIaccessname belongs. diskgroup can be either a group name or group ID number. If this option is not specified, the default disk group is determined using the rules given in the vxdg(1M) manual page.
Lists information about the area on a disk that is reserved for an AP database.
Specifies an offset into the public region to use for the slice. This value may be rounded up for alignment purposes.
Specifies a partition number (0-7) to use for the slice. Note that, by convention, 2 refers to the entire disk, and that VxVM usually assigns the public and private regions of a VM disk to partitions 3 and 4.
Attempts to repair the area of a disk that is reserved for an AP database.
Specifies a minimum size for the slice. The default size is 300K. The specified size may be rounded up for alignment purposes.
On successful completion, an exit status of zero is returned. On error, -1 is returned.
After replacing a failed disk, repair the area reserved for an AP database on disk01, and make it available as slice 0:
/etc/vx/bin/vxapslice -r -p 0 disk01
The repair can fail if the replacement disk is not identical to the original disk. If this happens, release the area that is currently reserved for an AP database, and then reserve a new area of the disk:
/etc/vx/bin/vxapslice -d disk01
/etc/vx/bin/vxapslice -p 0 disk01
Finally, use apdb to delete, and then recreate the AP database:
/usr/sbin/apdb -d /dev/vx/rdmp/c0t1d0s0
/usr/sbin/apdb -c /dev/vx/rdmp/c0t1d0s0
apdb(1M), vxintro(1M)
Sun Enterprise Server Alternate Pathing 2.3.1 User's Guide