[Bugs] [Bug 1331226] New: Cloned volume is not cleaned up on deletion

bugzilla at redhat.com bugzilla at redhat.com
Thu Apr 28 03:24:23 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1331226

            Bug ID: 1331226
           Summary: Cloned volume is not cleaned up on deletion
           Product: GlusterFS
           Version: 3.7.11
         Component: snapshot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: lpabon at redhat.com
                CC: bugs at gluster.org



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:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list