 | ||
| How automatic reclamation works | ||
|---|---|---|
| Prev | Understanding storage optimization solutions in Storage Foundation | Next |
| ||
| How automatic reclamation works | ||
|---|---|---|
| Prev | Understanding storage optimization solutions in Storage Foundation | Next |
On thin-reclamable arrays, storage that is no longer in use needs to be reclaimed by the array. Storage Foundation automatically reclaims the space on the array for certain admimistrative operations, as follows:
Deleting a volume.
Removing a mirror.
Shrinking a volume.
Removing a log.
Creating or growing a volume with the init=zero option.
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, Storage Foundation performs the reclaim operation asynchronously. The disk is flagged as pending reclamation. The vxrelocd (or recovery) daemon asynchronously reclaims the disks marked for reclamation at a future time. By default, the vxrelocd daemon runs every day at 22:10 hours, and reclaims storage on the deleted volumes or plexes that are one day old.
To display the disks that are pending reclamation, use the following command:
# vxprint -z
You can configure the automatic reclamation to reclaim immediately, or to schedule the asynchronous reclamation.
You can also trigger a reclamation manually for a disk, disk group or enclosure. This operation also reclaims any disks flagged as pending reclamation.