Description of problem: Whenever we are creating a clone with a name that's already been a part of a system as cloned volume before (but its deleted now), it fails with "Commit failed" message. For this to work properly, user need to remove the entries of older cloned volume from /run/gluster/snaps and and unmount it. Document URL: Section Number and Name: Describe the issue: 1.Create a clone with a name that was already a part of the system (but deleted now). However its entries can be seen under /run/gluster/snaps and it will be mounted. 2.this creation fails with commit failed message. 3.Remove the cloned volume entries from /run/gluster/snaps and unmount the clone. 4.Try the clone creation again with the same name and it should pass after removing the entries. Suggestions for improvement: Additional information:
Thanks Laura. It's perfect.
The issue is same as 1273722 and will be fixed as part of 1273722 *** This bug has been marked as a duplicate of bug 1273722 ***
This has been marked as duplicate by mistake. This needs to be fixed.
Patch posted upstream master : http://review.gluster.org/15683
*** Bug 1408386 has been marked as a duplicate of this bug. ***
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101285
[root@rhs-arch-srv1 yum.repos.d]# gluster snapshot clone clone1 snap0 snapshot clone: success: Clone clone1 created successfully [root@rhs-arch-srv1 yum.repos.d]# gluster v list clone1 gluster_shared_storage newvolume vol0 vol1 [root@rhs-arch-srv1 yum.repos.d]# gluster v start clone1 volume start: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v stop clone1 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y gluster v delete clone1volume stop: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v delete clone1 Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y volume delete: clone1: success [root@rhs-arch-srv1 yum.repos.d]# gluster v list gluster_shared_storage newvolume vol0 vol1 [root@rhs-arch-srv1 yum.repos.d]# gluster snapshot list vol1 snap0_GMT-2017.05.02-06.35.44 snap0 snap1 snap1-2 [root@rhs-arch-srv1 yum.repos.d]# gluster snapshot clone clone1 snap0 snapshot clone: success: Clone clone1 created successfully [root@rhs-arch-srv1 yum.repos.d]# gluster v start clone1 volume start: clone1: success [root@rhs-arch-srv1 yum.repos.d]# Can create clones with same name as previous deleted clone. Bug verified on build glusterfs-3.8.4-24.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774