Among the information obtained in Obtaining a list of information about storage pools or Obtaining information about individual storage pools, you can obtain the following capacity information ((1) to (13)). You can also verify these information through VSP One SDS Block Administrator.
(1) totalPhysicalCapacity: Total capacity of the storage pool [MiB].
(2) totalRawCapacity: The amount of space that is now available by adding drives to the storage pool [MiB].
(3) metaDataPhysicalCapacity: Capacity for control information in totalPhysicalCapacity [MiB].
(4) usablePhysicalCapacity: Capacity that can be used as logical capacity in totalRawCapacity [MiB].
(5) reservedPhysicalCapacity: Capacity not used for logical capacity in totalRawCapacity [MiB].
(6) blockedPhysicalCapacity: Blocked capacity in totalRawCapacity [MiB].
(7) totalCapacity: Capacity that can be used in the storage pool [MiB].
(8) usedCapacity: Capacity of storage that actually stores user data and metadata related to user data [MiB].
(9) freeCapacity: Capacity that is not used in the storage pool [MiB].
You can verify the total capacity of created volumes from the capacity information about storage pools.
| Name | Description | Type of the included volumes and snapshot attributes |
|---|---|---|
|
(10) totalVolumeCapacity [MiB] |
Total capacity of created volumes (Total of created provisioned volume capacity, other volume capacity, and temporary volume capacity) |
|
|
(11) provisionedVolumeCapacity [MiB] |
Capacity of provisioned volumes that have been created (Total capacity of normal volumes, snapshot volumes (P-VOL), journal volumes, and former journal volumes) |
|
|
(12) otherVolumeCapacity [MiB] |
Capacity of other volumes that have been created (Total capacity of snapshot volumes (S-VOLs and P/S-VOLs)) |
|
|
(13) temporaryVolumeCapacity [MiB] |
Temporary capacity of volumes that have been created (Cloud) Total capacity of volumes created temporarily by Data migration and Capacity balance (Bare metal) Total capacity of volumes created temporarily by Capacity balance |
|
-
The used capacity of snapshot volumes might be larger than the capacity of created volumes.
-
Each capacity listed in the preceding table does not include control information of the volume. Capacity including the control information can be calculated by referring to Maximum storage pool capacity consumed by a volume.
-
totalCapacity [MiB] (logical capacity of the storage pool) might differ depending on the setting value of the rebuild capacity policy (rebuildCapacityPolicy). For details, see Rebuild capacity of a storage pool.
Even if the totalVolumeCapacity [MiB] is smaller than the totalCapacity [MiB] (logical capacity of the storage pool), the capacity of the storage controller might become full if the used capacity of each storage controller is uneven.
When the capacity of storage controller is full, the following failures might occur:
-
Operations other than deleting the normal volumes, snapshot volumes, or the volumes with data reduction enabled fail
-
I/O to the normal volumes, snapshot volumes, or the volumes with data reduction enabled fails
-
Data in the snapshot volume is lost