You can increase the capacity of a V-VOL up to 256 TB.
After capacity expansion, the host is automatically notified of the capacity change. If the host does not recognize the capacity after capacity expansion, run the reload operation.
These requirements are for increasing the V-VOL capacity:
- The V-VOL to be increased is not shared with a software product that does not allow increasing the volume capacity.
- The V-VOL is not undergoing LDEV formatting.
- The V-VOL does not have data direct mapping enabled.
- The V-VOL is not a deduplication system data volume (fingerprint).
- The capacity to be added to the V-VOL must be specified.
- The pool related to the V-VOLs to be increased is in any one of these statuses:
- Normal
- In progress of pool capacity shrinking
When increasing V-VOL capacity, do not perform the following operations. When you perform these operations, do not increase V-VOL capacity.
- Operations using Virtual LUN
- Creating V-VOLs
- Restoring pools
- Deleting V-VOLs
- Operations to increase the V-VOL capacity in another instance of CCI
- Maintenance of your storage system
If one of these operations is being performed, the V-VOL capacity might not be increased:
- Volume Migration
- Configuration change of journal used by Universal Replicator
- Quick Restore by ShadowImage
For more information about the procedure for increasing the capacity of a V-VOL used in the TrueCopy pair, global-active device pair, Universal Replicator pair, ShadowImage pair, or Thin Image Advanced pair, see the documentation for each software product.
When increasing the capacity of a V-VOL connected to the host by using NVMe-oF or NVMe/TCP, if the host does not automatically recognize the capacity after the capacity expansion, rescan the V-VOL from the host or reconnect to the NVM subsystem.