REVIEW: http://review.gluster.org/14021 (clone/snapshot: Save restored_from_snap for clones) posted (#1) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/14021 committed in master by Rajesh Joseph (rjoseph) ------ commit fe6c4efcc66bca84aaceb352de38f0b58b70b780 Author: Avra Sengupta <asengupt> Date: Mon Apr 18 14:44:18 2016 +0530 clone/snapshot: Save restored_from_snap for clones Bricks of cloned volumes are lvm bricks mounted in /run/gluster, which on reboot of the node gets cleared. Hence, these brick paths need to be recreated on glusterd restart and the appropriate lvms are mounted. Change-Id: I6da086288c0dbdcedf3a20fd53f25e3728bea473 BUG: 1328010 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/14021 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user