CLI Guide

Description
A virtual volume is created on a device or a distributed device, and is presented to a host through a storage view. Virtual
volumes are created on top-level devices only, and always use the full capacity of the device or distributed device.
The underlying storage of a virtual volume may be distributed over multiple storage volumes, but appears as a single contiguous
volume.
The specified device must not already have a virtual volume and must not have a parent device.
Use the --set-tier argument to set the storage tier for the new virtual volume.
Table 16. virtual-volume field descriptions
Field Description
block count
The number of blocks in the volume.
block size
The size of a single block, in kilobytes.
cache-mode
Synchronous (write-through).
capacity
The total number of bytes in the volume. Equals the block-
size multiplied by the block-count.
NOTE: The capacity of a virtual volume on which the
initialization process has failed will be 0.
thin-capable
Determines whether the virtual volume is thin-capable or not.
thin-enabled
Determines whether the virtual volume is configured as thin-
enabled.
consistency-group
The name of the consistency group to which this volume
belongs, if any.
expandable-capacity
Excess capacity not yet exposed to the host by the virtual
volume. This capacity is available for expanding the virtual
volume.
● Zero (0) - Expansion is not supported on the virtual
volume or that there is no capacity available for expansion.
● Non-zero - The capacity available for virtual volume
expansion using the storage-volume method.
expansion-method
The expansion method that can be used to expand the virtual
volume.
● concatenation - The virtual volume can be expanded
only by adding the specified extents.
● not-supported - The virtual volume cannot be
expanded. This includes virtual volumes that are members
of RecoverPoint consistency groups.
● storage-volume - The virtual volume can be expanded
using storage array based volume expansion or by
migrating to a larger device.
expansion-status
Expansion status for the volume.
● - - None of the other expansion states apply. No operation
is blocked by this state.
● failed - An expansion has failed. The expansion has
failed and the expansion must be re-tried. If the expansion
is not retried this state will persist for up-to 2 days. See
health-indications for more information.
● When an expansion fails, the overall health, operational-
status, or service-status of the virtual-volume is not
degraded.
316 Commands