424 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
The only parameter except virtual capacity that is available on a volume level to monitor thin, 
compressed, or deduplicated volume, is used_capacity_before_reduction. It indicates the 
total amount of data written to a thin-provisioned or compressed volume copy in a data 
reduction storage pool before data reduction occurs. This field is empty for fully allocated 
volume copies and volume copies not in a data reduction pool. Capacity that is assigned to 
the volume in the tier is also not reported. 
To find this value, use the lsvdisk command with volume name or ID as a parameter, as 
shown in Example 10-9. It shows a non-compressed thin-provisioned volume with virtual size 
100 GiB on a DRP pool, which was mounted to a host, and had a 72 GiB file created on it.
Example 10-9   Volume in a DRP pool capacity monitoring
IBM_Storwize:ITSOV7K:superuser>lsvdisk vdisk1
id 15
name vdisk1
<...>
capacity 100.00GB
<...>
used_capacity
real_capacity
free_capacity
tier tier0_flash
tier_capacity 0.00MB
tier tier1_flash
tier_capacity 0.00MB
tier tier_enterprise
tier_capacity 0.00MB
tier tier_nearline
tier_capacity 0.00MB
compressed_copy no
uncompressed_used_capacity
deduplicated_copy no
used_capacity_before_reduction 71.09GB
Capacity and space saving reporting is available in the storage pool views, and Out of space 
warning thresholds are configured at the storage pool level. You can check savings with the 
GUI Pools view, GUI Dashboard, or by using the CLI command lsmdiskgrp with the DRP pool 
ID or name as a parameter, as shown in Example 10-10.
Example 10-10   Pool savings monitoring
IBM_Storwize:ITSOV7K:superuser>lsmdiskgrp 3
id 3
name Pool1
<...>
capacity 8.64TB
free_capacity 7.53TB
virtual_capacity 1.79TB
used_capacity 882.38GB
real_capacity 883.95GB
overallocation 20
<...>
tier tier0_flash
tier_mdisk_count 0