Summary
Sometimes Catalog condense will fail due to locked snapshots on the vstor appliance. This article provides steps to find and clear these locked snapshots.
Symptoms
Catalog Condense fails with error:
X.X.X.X 10/18/2018 11:30:48 am SNBSVH_525E Could not delete snapshot(SSSV_kvhb-mtz-18.1537209001) on volume(vol01) of node(DPX-vStor). Reason(org.springframework.web.client.RestClientException: Failed to delete snapshot: One or more dependent clones are present: id 53)
Resolution
The reasons for this error are that the snapshot in question is locked due to a LUN/Share still being present that requires it.
The most common cause for this is an Instant Mapping drive still made available to a host:
In order to find the possible host(s) in question access the the vstor appliance via ssh and run
vstor host show , this command will show all hosts current having a share /mapping on the vstor appliance
In the management console, navigate to Restore > Block tab. Expand your Enterprise.
Locate and right-click the hosts from the above command terminating the IA mapped volume.
Highlight the volume in the IA mapped volumes window and select Unmap volume.
If the mapping fails to unmap or says it is no longer present and you are sure you do not need the mappings anymore you can do the following on the vstor appliance
[root@DPX-vStor fs2]# vstor volume show
ID | TYPE | POOL | IS CLONE | TOTAL | FREE | USED | NAME
-----------------------------------------------------------------------------------------------
2 | filesystem | 2 | No | 7.69TB | 3.46TB | 4.23TB | vol01
53 | filesystem | 2 | Yes | 7.69TB | 3.46TB | 14.98MB | temp_lun_clone_vol01_1537210136
61 | filesystem | 2 | Yes | 7.69TB | 3.46TB | 14.94MB | temp_lun_clone_vol01_1537382920
77 | filesystem | 2 | Yes | 7.69TB | 3.46TB | 15.07MB | temp_lun_clone_vol01_1537728451
Delete all volumes that contain temp_lun_clone with the command:
vstor volume delete --id <number>
Run a fresh condense job and this should complete successfully.