92
Alphabetical list of commands
When a vdisk is quarantined, its disks become write-locked, its volumes become inaccessible, and it
is not available to hosts until it is dequarantined. If there are interdependencies between the
quarantined vdisk’s volumes and volumes in other vdisks, quarantine may temporarily impact
operation of those other volumes. For example, if the quarantined vdisk contains the snap pool used
for snapshot, volume-copy, or replication operations, quarantine may temporarily cause the
associated master volume to go offline; a volume-copy or replication operation can also be
disrupted if an associated volume (snap pool, source volume, or destination volume) goes offline.
Depending on the operation, the length of the outage, and the settings associated with the
operation, the operation may automatically resume when the vdisk is dequarantined or may require
manual intervention. A vdisk can remain quarantined indefinitely without risk of data loss.
A vdisk is dequarantined when it is brought back online, which can occur in three ways:
•
If the inaccessible disks come online, making the vdisk
FTOL
, the vdisk is automatically
dequarantined.
•
If after 60 seconds from being quarantined the vdisk is
QTCR
or
QTDN
, the vdisk is automatically
dequarantined. The inaccessible disks are marked as failed and the vdisk status changes to
CRIT
(critical) or
FTDN
(fault tolerant with a down disk). If the inaccessible disks later come
online, they are marked as
LEFTOVR
(leftover).
•
The
dequarantine
command is used to manually dequarantine the vdisk. If the inaccessible
disks later come online, they are marked as
LEFTOVR
(leftover). If event 172 was logged, do not
use the
dequarantine
command; instead follow the event’s recommended-action text. If event
485 was logged, use the
dequarantine
command only as specified by the event’s
recommended-action text to avoid data corruption or loss.
When a vdisk is dequarantined, event 173 is logged.
A quarantined vdisk can be fully recovered if the inaccessible disks are restored. Make sure that all
disks are properly seated, that no disks have been inadvertently removed, and that no cables have
been unplugged. Sometimes not all disks in the vdisk power up. Check that all enclosures have
restarted after a power failure. If these problems are found and then fixed, the vdisk recovers and no
data is lost.
If the inaccessible disks cannot be restored (for example, they failed), and the vdisk’s status is
FTDN
or
CRIT
, and compatible spares are available to replace the inaccessible disks, reconstruction will
automatically begin.
If a replacement disk (reconstruct target) is inaccessible at power up, the vdisk becomes
quarantined; when the disk is found, the vdisk is dequarantined and reconstruction starts. If
reconstruction was in process, it continues where it left off.
NOTE:
The only commands allowed for a quarantined vdisk are
dequarantine
and
delete
vdisk
. If you delete a quarantined vdisk and its inaccessible disks later come online, the vdisk will
reappear as quarantined or offline and you must delete it again (to clear those disks).
Syntax
dequarantine vdisk
vdisk
Parameters
vdisk
vdisk
Name or serial number of the vdisk to remove from quarantine. For vdisk syntax, see
Command
syntax
on page 22.
Содержание P2000 G3
Страница 1: ...HP P2000 G3 MSA System CLI Reference Guide Part number 500912 009 First edition February 2014 ...
Страница 14: ...14 About this guide ...
Страница 30: ...30 Categorical list of commands ...
Страница 96: ...96 Alphabetical list of commands exit Description Log off and exit the CLI session Syntax exit ...
Страница 159: ...HP P2000 G3 MSA System CLI Reference Guide 159 See also set host parameters show iscsi parameters ...
Страница 199: ...HP P2000 G3 MSA System CLI Reference Guide 199 See also set cache parameters show volumes ...
Страница 217: ...HP P2000 G3 MSA System CLI Reference Guide 217 Basetypes drives enclosure list status See also show vdisks ...
Страница 223: ...HP P2000 G3 MSA System CLI Reference Guide 223 Basetypes email parameters status See also set email parameters ...
Страница 230: ...230 Alphabetical list of commands See also clear events set snmp parameters show snmp parameters ...
Страница 288: ...288 Alphabetical list of commands Basetypes snapshots status See also show master volumes show snap pools ...
Страница 292: ...292 Alphabetical list of commands Basetypes system unhealthy component status See also set system ...
Страница 294: ...294 Alphabetical list of commands See also set volume set vdisk ...
Страница 338: ...338 Alphabetical list of commands Basetypes remote links See also show remote systems verify remote link ...
Страница 340: ...340 Alphabetical list of commands Basetypes remote links See also show remote systems verify links ...
Страница 424: ...424 XML API basetype properties PROPERTY name utility priority numeric type string 0 PROPERTY OBJECT ...
Страница 469: ...HP P2000 G3 MSA System CLI Reference Guide 469 PROPERTY name status type string OK PROPERTY OBJECT ...
Страница 494: ...494 XML API basetype properties PROPERTY name sample time numeric type string 1329397200 PROPERTY OBJECT ...
Страница 498: ...498 XML API basetype properties PROPERTY name mrc version type uint8 0 PROPERTY OBJECT ...
Страница 510: ...510 XML API basetype properties PROPERTY name reserve type numeric type string 0 PROPERTY OBJECT ...
Страница 524: ...524 Glossary ...
Страница 532: ...532 Index ...