REVIEW: http://review.gluster.org/12437 (snapshot: Inherit snap-max-hard-limit from original volume) posted (#1) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/12437 committed in master by Rajesh Joseph (rjoseph) ------ commit 1f74a3efbd0337759878ffff5cd4ee6782ddfe3f Author: Avra Sengupta <asengupt> Date: Wed Oct 28 12:30:34 2015 +0530 snapshot: Inherit snap-max-hard-limit from original volume A snapshot should inherit snap-max-hard-limit from the original volume while being created and when being restored to, it should restore the same. Similarly a clone taken from a snapshot should inherit snap-max-hard-limit from the snapshot. Change-Id: If8e90e2ffc10e22086b803ac8e2638a16bcec968 BUG: 1275616 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/12437 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: mohammed rafi kc <rkavunga> Tested-by: 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