Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

# vxvset -g mydg stop set1
# vxvset -g mydg list set1
VOLUME INDEX LENGTH KSTATE CONTEXT
vol1 0 12582912 DISABLED -
vol2 1 12582912 DISABLED -
vol3 2 12582912 DISABLED -
# vxvset -g mydg start set1
# vxvset -g mydg list set1
VOLUME INDEX LENGTH KSTATE CONTEXT
vol1 0 12582912 ENABLED -
vol2 1 12582912 ENABLED -
vol3 2 12582912 ENABLED -
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
Symantec NetBackup™ 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.
Warning: 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.
389Creating and administering volume sets
Raw device node access to component volumes