Monitoring Thin Reclamation using the vxtask command

The thin reclamation can be an intensive operation that may be time consuming, depending on the size of the disk and the amount of space to be reclaimed. As with other long-running tasks, you can monitor the operation with the vxtask command.

To monitor thin reclamation

  1. Initiate the thin reclamation as usual, for a disk, disk group, or enclosure.
    # vxdisk reclaim diskgroup| disk| enclosure

    For example:

    # vxdisk reclaim dg100
  2. To monitor the reclamation status, run the following command in another session:
    # vxtask monitor
    TASKID PTID TYPE/STATE    PCT   PROGRESS
    1258   -    RECLAIM/R 17.28% 65792/33447328/5834752 RECLAIM vol4 dg100
    1259   -    RECLAIM/R 25.98% 0/20971520/5447680     RECLAIM vol2 dg100
    1263   -    RECLAIM/R 25.21% 0/20971520/5287936     RECLAIM vol3 dg100
    1258   -    RECLAIM/R 25.49% 0/20971520/3248128     RECLAIM vol4 dg100
    1258   -    RECLAIM/R 27.51% 0/20971520/3252224     RECLAIM vol4 dg100 
    1263   -    RECLAIM/R 25.23% 0/20971520/5292032     RECLAIM vol3 dg100  
    1259   -    RECLAIM/R 26.00% 0/20971520/5451776     RECLAIM vol2 dg100
  3. If you have multiple tasks, you can use the following command to display the tasks.
    # vxtask list
    TASKID PTID TYPE/STATE    PCT   PROGRESS
    1258   -    RECLAIM/R 17.28% 65792/33447328/5834752 RECLAIM vol4 dg100
    1259   -    RECLAIM/R 25.98% 0/20971520/5447680     RECLAIM vol2 dg100
    1263   -    RECLAIM/R 25.21% 0/20971520/5287936     RECLAIM vol3 dg100
  4. Use the task id from the above output to monitor the task:
    # vxtask monitor 1258
    TASKID  PTID TYPE/STATE    PCT   PROGRESS
    1258     -   RECLAIM/R 17.28% 65792/33447328/5834752 RECLAIM vol4 dg100
    1258     -   RECLAIM/R 32.99% 65792/33447328/11077632 RECLAIM vol4 dg100
    1258     -   RECLAIM/R 45.55% 65792/33447328/15271936 RECLAIM vol4 dg100
    1258     -   RECLAIM/R 50.00% 0/20971520/10485760     RECLAIM vol4 dg100
    .
    .
    .

    The vxdisk reclaim command runs in another session while you run the vxtask list command.

    See the vxtask(1m) manual page.