REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#1) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#2) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#3) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#4) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#5) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/13474 (Tier: making detach start fail when brick on hot tier is down) posted (#6) for review on master by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/13474 committed in master by Jeff Darcy (jdarcy) ------ commit 133441436875416258bdc1272db91fab73a7065c Author: hari <hgowtham> Date: Fri Feb 19 13:43:48 2016 +0530 Tier: making detach start fail when brick on hot tier is down Currently detach tier start happens even when a hot brick is down this might lead to data loss. This patch prevents the detach tier start from being executed successfully if a brick in hot tier is down Change-Id: I3b6047a44bd01b8a6887d41f799f64de6bf075ef BUG: 1309999 Signed-off-by: hari <hgowtham> Reviewed-on: http://review.gluster.org/13474 Smoke: Gluster Build System <jenkins.com> Tested-by: hari gowtham <hari.gowtham005> Reviewed-by: Gaurav Kumar Garg <ggarg> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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