3PAR CIM API Programming Reference for InForm OS 2.3.1 (320-200164 Rev B, February 2010)

5.52
Block Services Package
CIM API Programming Reference InForm OS Version 2.3.1
 TPD_DynamicStoragePool.RemainingManagedSpace =
TPD_DynamicStoragePool.SpaceLimit – volume logical size = 100G – 10G = 90G
 TotalManagedSpace for the dynamic storage pool remains unchanged.
5.9.6.6 Thinly Provisioned Storage Volume
TPD_AllocatedFromStoragePool.SpaceConsumed between the parent dynamic storage
pool and the thinly provisioned storage volume represents the actual size allocated to the
volume. This value is also represented in
StorageVolume.ProvisionedConsumableBlocks, i.e., SpaceConsumed equals
ProvisionedConsumableBlocks. As is the case with Fully Provisioned volume Fully
Provisioned Storage Volume on page 5.50, logical capacity is used in calculating
SpaceConsumed with child volumes/delta replica pool.
StorageVolume.NumberOfBlocks is the virtual size of the TPVV.
TPD_StorageVolume.ConsumableBlocks is set to be the same as
TPD_StorageVolume.NumberOfBlocks.
Example:
 Initial State
A dynamic storage pool has a virtual capacity of 100GB (as set in the –sdgl option). This value is
reflected in
TPD_DynamicStoragePool.SpaceLimit property and is what’s available for
volume allocation. Let’s assume that there are no volumes or
DeltaReplicaStoragePool
allocated from this pool initially. The
TotalManagedSpace property reflects the actual
capacity allocated to the pool.
 Before Volume Creation
 TPD_DynamicStoragePool.TotalManagedSpace = actual capacity allocated to the
pool
 TPD_DynamicStoragePool.SpaceLimit = 100GB
 TPD_DynamicStoragePool.RemainingManagedSpace = 100 GB (capacity that can
be used to create volume)
 After Volume Creation
Suppose a RAID-10 volume of logical size 10G is created from the dynamic storage pool. This
value is represented in the
TPD_StorageVolume class as NumberOfBlocks
(
ConsumableBlocks also has the same value). Since this is a thinly provisioned volume, what