Description of problem: Whenever we delete a snapshot-clone, the entries of clones under /run/gluster/snaps doesn't get deleted. and we have to manually clean up the system. Version-Release number of selected component (if applicable): glusterfs-3.7.5-0.3 How reproducible: Always Steps to Reproduce: 1.Craete a volume and then a snapshot of it. 2.Create a clone of this snapshot. 3.Delete the clone using volume delete command. 4.Observe that after deleting the clones, the entries for clones still persists inside /run/gluster/snaps and it still shows as mounted. 5. We have to manually delete the entries and clean up the system. Actual results: Clone entries under /run/gluster/snaps doesn't get deleted and clone still shows as mounted. Expected results: Clone entries should be removed from /run/gluster/snaps and it should get umounted. Additional info:
*** Bug 1273716 has been marked as a duplicate of this bug. ***
*** Bug 1309209 has been marked as a duplicate of this bug. ***
A cloned snapshot, is similar to a gluster volume, and hence following the same protocol, will not clear it's entries itself. The issue of not being able to create clone with the same name will be handled as part of https://bugzilla.redhat.com/show_bug.cgi?id=1309209