CLI Guide

release volume
Description Clears initiator registrations and releases persistent reservations for all or specified volumes. Normally,
reservations placed on volumes by initiators accessing those volumes can be released by host software. This
command should be used only when the system is in an abnormal state, perhaps due to a configuration
problem, and you need to remove all reservations for specified volumes and return them to a “clean” state.
CAUTION: Releasing reservations for volumes may allow unintended access to those volumes
by other initiators, which may result in data corruption. Before issuing this command, quiesce
all host initiators that have visibility to the volumes whose reservations will be released.
Minimum role manage
Syntax
release volume
all|volumes
Parameters all|volumesSpecifies all volumes, or a comma-separated list of the names or serial numbers of specific
volumes. A name that includes a space must be enclosed in double quotes.
Examples Release reservations for a specific volume.
# release volume vd04_v0002
See also
show volume-reservations
show volumes
remove disk-groups
Description
Removes specified disk groups.
CAUTION:
If your system gets into a state where a virtual disk group is quarantined or offline or does
not have a corresponding pool, contact technical support.
Deleting a linear disk group will delete all data it contains.
If a specified disk group has a job running, such as media scrub, the command will prompt for confirmation to
stop the job.
For a linear disk group, if the group contains volumes, the command will prompt for confirmation to delete the
volumes. If the reply is yes, the command will unmap and delete all volumes in the group, delete the group and
corresponding pool, and make all the disks available. If the reply is no, the command will be canceled.
For a virtual disk group, if the group contains no volume data, the group will be removed. If the group
contains volume data, the command will initiate removal and try to drain (move) all volume data to other
groups in the same pool. While data is being drained, the group's status will be VDRAIN. If the pool does not
have enough space to contain the volume data, the command will immediately fail with an error. If draining
begins and is successful, an event will be logged and the group will be removed. If draining begins but hosts
continue to write new data to the volumes and cause amout-of-space condition, the command will fail and an
event will be logged.
NOTE: Disk group removal (draining) can take a very long time depending on a number of
factors in the system, including but not limited to: large pool configuration; the amount of I/O
traffic to the system (e.g., active I/O pages to the draining disk group); the type of the disk
group page migration (enterprise SAS, midline SAS, SSD); the size of the draining disk
group(s) in the system; and the number of disk groups draining at the same time.
If you remove the last disk group in a virtual pool, the command will prompt for confirmation to remove the
pool, too. If the reply is yes, the pool will be removed. If the reply is no, the disk group and the pool will remain.
In one command you can delete linear and virtual disk groups, and disk groups from more than one pool.
NOTE:
86 Alphabetical list of commands