REVIEW: http://review.gluster.org/15683 (snapshot: Fix the failure to recreate clones with same name) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/15683 (snapshot: Fix the failure to recreate clones with same name) posted (#2) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/15683 committed in master by Rajesh Joseph (rjoseph) ------ commit 9a2b3fb8b9ff28edafa012dacc5f5f0e4ee1afab Author: Avra Sengupta <asengupt> Date: Thu Oct 20 12:58:16 2016 +0530 snapshot: Fix the failure to recreate clones with same name The brick path of snapshot clones contained the clonename, thereby failing to create newer clones with the same name after the original clone had been deleted. This fix creates the brick path with the clone's vol id instead of the clones name. Hence future clones with the same name will not have the namespace clash. Change-Id: I262712adc576122f051b5d1ce171d020efaefd1a BUG: 1387160 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/15683 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/