298 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
free_capacity 0.00MB
overallocation 100
autoexpand
warning
grainsize
se_copy no
easy_tier on
easy_tier_status balanced
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 10.00GB
compressed_copy no
uncompressed_used_capacity 10.00GB
parent_mdisk_grp_id 1
parent_mdisk_grp_name Pool1
encrypt yes
deduplicated_copy no
used_capacity_before_reduction 0.00MB
When adding a volume copy, you can define it with different parameters than the original 
volume copy. For example, you can create a thin-provisioned copy of a fully allocated volume 
to migrate a thick-provisioned volume to a thin-provisioned volume. The migration can be also 
done in the opposite direction.
In Example 7-11, the volume name is changed from VOL_NO_MIRROR to VOL_WITH_MIRROR.
Example 7-11   Volume name changes
IBM_Storwize:ITSO:superuser>chvdisk -name VOL_WITH_MIRROR VOL_NO_MIRROR
IBM_Storwize:ITSO:superuser>
Using -autodelete flag to migrate a volume
This section shows the use of the addvdiskcopy command with the -autodelete flag set. 
The -autodelete flag causes the primary copy to be deleted after the secondary copy is 
synchronized.
Example 7-12 shows a shortened lsvdisk output for an uncompressed volume with a single 
volume copy.
Example 7-12   An uncompressed volume
IBM_Storwize:ITSO:superuser>lsvdisk UNCOMPRESSED_VOL
id 9
name UNCOMPRESSED_VOL
IO_group_id 0
IO_group_name io_grp0
status online
...
Volume copy mirror parameters: To change the parameters of a volume copy, you must 
delete the volume copy and redefine it with the new values.