Veritas Volume Manager 5.0 Administrator's Guide (September 2006)

356 Creating and administering volume sets
Removing a volume from a volume set
vol2 1 12582912 ENABLED -
vol3 2 12582912 ENABLED -
Removing a volume from a volume set
To remove a component volume from a volume set, use the following command:
# vxvset [-g diskgroup] [-f] rmvol volset volume
For example, the following commands remove the volumes, vol1 and vol2, from the
volume set myvset:
# vxvset -g mydg rmvol myvset vol1
# vxvset -g mydg rmvol myvset vol2
Note: When the final volume is removed, this deletes the volume set.
Caution: The -f (force) option must be specified if the volume being removed, or any
volume in the volume set, is either a snapshot or the parent of a snapshot. Using this option
can potentially cause inconsistencies in a snapshot hierarchy if any of the volumes
involved in the operation is already in a snapshot chain.
Raw device node access to component volumes
To guard against accidental file system and data corruption, the device nodes of the
component volumes are configured by default not to have raw and block entries in the /
dev/vx/rdsk/diskgroup and /dev/vx/dsk/diskgroup directories. As a
result, applications are prevented from directly reading from or writing to the component
volumes of a volume set.
If some applications, such as the raw volume backup and restore feature of the Veritas
NetBackup
TM
software, need to read from or write to the component volumes by accessing
raw device nodes in the /dev/vx/rdsk/diskgroup directory, this is supported by
specifying additional command-line options to the
vxvset command. Access to the block
device nodes of the component volumes of a volume set is unsupported.
Caution: Writing directly to or reading from the raw device node of a component volume
of a volume set should only be performed if it is known that the volume's data will not
otherwise change during the period of access.
All of the raw device nodes for the component volumes of a volume set can be created or
removed in a single operation. Raw device nodes for any volumes added to a volume set
are created automatically as required, and inherit the access mode of the existing device
nodes.