No space to allocate volume
v REMOTE_VOLUME_SIZE_ABOVE_LIMIT
Volume size specified is above limit of remote machine
v VOLUME_LOCKED
Volume is locked
v VOLUME_HAS_DATA_MIGRATION
Data Migration is defined for this volume
v CAN_NOT_SHRINK_MAPPED_VOLUME
Mapped volume's size cannot be decreased
v CAN_NOT_SHRINK_VOLUME_WITH_SNAPSHOTS
Size of volume with snapshots cannot be decreased
v CAN_NOT_SHRINK_REMOTE_VOLUME_WITH_SNAPSHOTS
Remote volume has snapshots
v CAN_NOT_SHRINK_MAPPED_REMOTE_VOLUME
Remote volume is mapped
v REMOTE_VOLUME_HAS_DATA_MIGRATION
Data Migration is defined for slave volume
v VOLUME_CANNOT_HAVE_ZERO_SIZE
Volume size cannot be zero
v CAN_NOT_SHRINK_SNAPSHOTS
Size of snapshots cannot be decreased
v CAN_NOT_RESIZE_ASYNC_INTERVAL_VOLUMES
Size of volumes with asynchronous mirroring cannot be changed
v CAN_NOT_SHRINK_VOLUME
Size of volumes cannot be decreased without explicit request
v MIRROR_SIZE_MISMATCH
Slave volume and Master Volume sizes are different
v MIRROR_POSSIBLE_SIZE_MISMATCH
Slave volume and Master Volume sizes may be different. This problem occurs
whenever the Master does not receive an acknowledgment from the Slave until
the command timed out, or any other unexpected failure.
v VOLUME_SIZE_ABOVE_LIMIT
Volume size specified is above limit
v COMMAND_NOT_SUPPORTED_FOR_OLVM_VOLUMES
This command is not supported for IBM Hyper-Scale Mobility volumes.
v MIRROR_IS_NON_OPERATIONAL
Mirror is non-operational
v VOLUME_IS_SLAVE
Volume is defined as a slave volume
v MIRROR_RETRY_OPERATION
There is an operation in progress on this mirror , please retry your request in a
few seconds
Troubleshooting: Please retry the command in a few seconds
Chapter 3. Volume Management 57
To Next Page
Loading...
Need help?
General
