CLI Guide

Table 16. virtual-volume field descriptions (continued)
Field Description
● in-progress - An expansion has been started, but has
not completed. The following operations are blocked on
the volume: additional expansion, migration, and NDU.
● unknown - Metro node could not determine the expansion
status of the volume.
health-indications
Indicates the reasons for:
● A health-state that is not 'ok'
● The reasons for the failure of virtual volume expansion or
initialization.
health state
● major failure - One or more of the virtual volume's
underlying devices is out-of-date, but will never rebuild.
● minor failure - One or more of the virtual volume's
underlying devices is out-of-date, but will rebuild.
● non-recoverable error - Metro node cannot
determine the virtual volume's Health state.
● ok - The virtual volume is functioning normally.
● unknown -Metro node cannot determine the virtual
volume's Health state, or the state is invalid.
initialization-status
Status of the initialization process on the virtual volume.
● success - Indicates that the initialization process is
completed successfully.
● failed - Indicates that the initialization process is failed.
● in-progress - Indicates that the initialization process is
in progress.
● unknown - Indicates that the initialization process remains
in a status other than success, failed, or in-
progress.
NOTE: If initialization is requested during the creation
of the virtual volume, you must wait until the
initialization process is completed successfully to use
the virtual volume. If the initialization process fails,
restart the process by using the virtual-volume re-
initialize command.
locality
● local - The virtual volume relies completely on storage at
its containing cluster.
● remote - The virtual volume is a proxy for a volume
whose storage resides at a different cluster. I/O to a
remote virtual volume travels between clusters.
● distributed - The virtual volume is the cluster-local
representation of a distributed RAID-1. Writes to a
distributed volume travels to all the clusters at which it
has storage; reads come, if possible, from the local leg.
operational status
● degraded - The virtual volume may have one or more
out-of-date devices that will eventually rebuild.
● error - One or more of the virtual volume's underlying
devices is hardware-dead.
● ok - The virtual volume is functioning normally.
● starting -The virtual volume is not yet ready.
● stressed - One or more of the virtual volume's
underlying devices is out-of-date and will never rebuild.
● unknown - Metro node cannot determine the virtual
volume's Operational state, or the state is invalid.
Commands 317