Description of problem: Once a cloned volume is deleted, there should be a way to destroy it and remove all the mount points and logical volumes created by GlusterFS Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: - gluster volume create myvol ... - gluster snapshot create mysnap myvol - gluster snapshot activate mysnap - gluster snapshot clone myclone mysnap - gluster snapshot deactivate mysnap - gluster snapshot delete mysnap - gluster volume delete myclone Actual results: All LVs are still mounted and space still allocated in thin pools Expected results: All LVs unmounted and destroyed to return space back to thin pools. or do one more command to fully destroy: - gluster snapshot clone destroy myclone Additional info:
The behaviour of snapshot clone is in sync with current volume delete's behaviour where we do not cleanup the volume's bricks, irrespective of how the bricks were created (be it user created or snapshot restored). I believe that is the right thing to do, as we do not want to mess up with users backend data. Closing it as it's not a bug, but an expected behaviour.