CLI Guide

CAUTION: Deleting a volume will delete all data it contains, and its schedules.
NOTE: For virtual storage, you cannot delete a volume that is in a replication set.
This command has a confirmation prompt in interactive console mode.
Minimum role manage
Syntax
delete volumes
volumes
Parameters
volumes
A comma-separated list of the names or serial numbers of the volumes to delete. A name that includes a
space must be enclosed in double quotes
Examples Delete volumes vol1 and vol2.
# delete volumes vol1,vol2
See also
create volume
show volumes
dequarantine
Description
Removes a disk group from quarantine.
NOTE: For virtual storage, this command should only be used by or with direction from
technical support.
Dequarantine is supported for a RAID-3, RAID-5, RAID-6, or RAID-50 disk group and operates as detailed
below.
Dequarantine is not supported for a RAID-1 or RAID-10 disk group. For these RAID levels, if the missing disks
become available, the disk group will be dequarantined automatically. Otherwise, some data will have been
lost because data in the remaining disks will be invalid (“stale”).
CAUTION: Carefully read this topic to determine whether to use the dequarantine command to
manually remove a disk group from quarantine. The dequarantine command should only be
used as part of the emergency procedure to attempt to recover data and is normally followed
by use of the CLI trust command. If a disk group is manually dequarantined and does not have
enough disks to continue operation, its status will change to OFFL and its data may or may not
be recoverable through use of the trust command. It is recommended that you contact
technical support for assistance in determining if the recovery procedure that makes use of
the dequarantine and trustcommands applies to your situation and for assistance to perform
it. Also, see the help for the trustcommand.
To continue operation and not go to quarantined status, a RAID-3 or RAID-5 disk group can have only one
inaccessible disk, a RAID-6 disk group can have only one or two inaccessible disks, and a RAID-10 or RAID-50
disk group can have only one inaccessible disk per subgroup. For example, a 16-disk RAID-10 disk group can
remain online (critical) with 8 inaccessible disks if one disk per mirror is inaccessible.
The system will automatically quarantine a disk group having a fault-tolerant RAID level if one or more of its
disks becomes inaccessible, or to prevent invalid data that may exist in the controller from being written to
the disk group. Quarantine will not occur if a known-failed disk becomes inaccessible or if a disk becomes
inaccessible after failover or recovery. The system will automatically quarantine an NRAID or RAID-0 disk
group to prevent invalid data from being written to the disk group. If quarantine occurs because of an
inaccessible disk, event 172 is logged. If quarantine occurs to prevent writing invalid data, event 485 is logged.
Examples of when quarantine can occur are:
• At system power-up, a disk group has fewer disks online than at the previous power-up. This may happen
because a disk is slow to spin up or because an enclosure is not powered up. The disk group will be
automatically dequarantined if the inaccessible disks come online and the disk group status becomes
FTOL (fault tolerant and online), or if after 60 seconds the disk group status is QTCR or QTDN.
Alphabetical list of commands
75