You can only expand a nomal volume whose status is "Normal" or "ExpansionFailed", and "volumeType" is "Normal."
-
If you expand a volume whose "status" is "Normal", the volume is expanded by the capacity specified in the parameter "additionalCapacity."
-
If you expand a volume whose status is "ExpansionFailed", the volume expansion is performed again.
-
Snapshot volumes cannot be expanded. To expand volumes whose volumeType is "Snapshot" and whose snapshotAttribute is "P-VOL", delete all the snapshot volumes created from the applicable volumes. Volumes whose volumeType is "Snapshot" and whose snapshotAttribute is "P/S-VOL" or "S-VOL" cannot be expanded.
-
Volumes whose universalReplicatorAttribute is "P-VOL" or "S-VOL" cannot be expanded. To expand volumes whose universalReplicatorAttribute is "P-VOL" or "S-VOL", perform Universal Replicator pair split, volume expansion, and Universal Replicator pair resynchronization in sequence.
-
Volumes whose volumeType is "Journal" cannot be expanded. To expand volumes whose volumeType is "Journal", add a volume that has required capacity as a reserve journal volume, and then replace the journal volume with the reserve journal volume.
-
Volumes whose volumeType is "FormerJournal" cannot be expanded.
In a command for expanding volumes, specify the capacity to be expanded in units of MiB for "additionalCapacity." However, the expanded capacity must also have additional management area. Therefore, the upper limit value that can be specified for "additionalCapacity" is logicalLimit minus the capacity for additional management area.
The upper limit value that can be specified for "additionalCapacity" = logicalLimit [MiB] – ((168 [MiB] × n) + 42 [MiB])
-
n = Logical capacity of a volume to be added to the expanded volume [MiB] / 3,145,548 [MiB] (A decimal is rounded up to the nearest integer.)
-
To verify the value of logicalLimit, run either of the following commands.
REST API: GET /v1/objects/storage-controllers
CLI: storage_controller_list
- If the event log KARS06170-C is issued and no actions are taken, verify to take actions for KARS06170-C before the operations on the volume.
- Volume capacity is managed in units of 42 MiB. Accordingly, even if the value of logicalLimit is 0, unused capacity might exist. In this case, volume capacity can be expanded to the upper limit of the management unit (a maximum of 41 MiB) in some cases.
-
If expansion of a volume causes it to become over-provisioned, write I/Os for the capacity equal to or more than allocatableCapacity [MiB] of the storage controller that manages the volume become unavailable.
Also, if a capacity is depleted while a single volume is over-provisioned, drive addition becomes necessary. See Adding drives to add storage pool capacity.
-
Required role: Storage
-
When expanding volumes in a VPS: Scope of the VPS