Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

To identify LUNs
◆
To identify LUNs that are thin or thinrclm type the following command:
# vxdisk -o thin list
DEVICE SIZE(mb) PHYS_ALLOC(mb) GROUP TYPE
hitachi_usp0_065a 10000 84 - thinrclm
hitachi_usp0_065b 10000 110 - thinrclm
hitachi_usp0_065c 10000 74 - thinrclm
hitachi_usp0_065d 10000 50 - thinrclm
.
.
.
hitachi_usp0_0660 10000 672 thindg thinrclm
In the above output, the SIZE column shows the size of the disk. The
PHYS_ALLOC column shows the physical allocation on the array side. The
TYPE indicates that the array supports thin reclamation.
How reclamation on a deleted volume works
Storage that is no longer in use, needs to be reclaimed by the array. The process
of reclaiming storage on an array can be intense on the array. To avoid any effect
on regular I/O's to the array, the reclaim operation is made asynchronous. When
a volume is deleted the space previously used by the volume is tracked for later
asynchronous reclamation. This asynchronous reclamation is handled by vxrelocd
(or recovery) daemon.
By default, the vxrelocd daemon runs everyday at 22:10 hours and reclaims
storage on the deleted volume that are one day old.
To perform the reclaim operation during less critical time of the system, control
the time of the reclaim operation by using the following tunables:
Administering volumes
Reclamation of storage on thin reclamation arrays
344