REVIEW: http://review.gluster.org/12914 (tier/dht: files are still going to decommissioned subvol) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/12914 (tier/dht: files are still going to decommissioned subvol) posted (#2) for review on master by Vijay Bellur (vbellur)
REVIEW: http://review.gluster.org/12914 (tier/dht: files are still going to decommissioned subvol) posted (#3) for review on master by Vijay Bellur (vbellur)
REVIEW: http://review.gluster.org/12914 (tier/dht: files are still going to decommissioned subvol) posted (#4) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/12914 (tier/dht: files are still going to decommissioned subvol) posted (#5) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/12914 committed in master by Dan Lambright (dlambrig) ------ commit cb41de7c4a7d620dbab645f2b105286b68bde9a9 Author: Mohammed Rafi KC <rkavunga> Date: Tue Dec 8 19:55:22 2015 +0530 tier/dht: files are still going to decommissioned subvol After detach tier start, creates are still going to hot tier. Because when creating data files we are not checking for decommissioned bricks. Change-Id: I8e28258d9b2367dcc8ad6e5e91d0e54d92fdf771 BUG: 1289602 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/12914 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
REVIEW: http://review.gluster.org/12937 (tier/dht: files are still going to decommissioned subvol) posted (#1) for review on release-3.7 by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/12937 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit 9f35fcf087d5c30d460999d667b1b82dfd08d762 Author: Mohammed Rafi KC <rkavunga> Date: Tue Dec 8 19:55:22 2015 +0530 tier/dht: files are still going to decommissioned subvol After detach tier start, creates are still going to hot tier. Because when creating data files we are not checking for decommissioned bricks. Backpor of> >Change-Id: I8e28258d9b2367dcc8ad6e5e91d0e54d92fdf771 >BUG: 1289602 >Signed-off-by: Mohammed Rafi KC <rkavunga> >Reviewed-on: http://review.gluster.org/12914 >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Dan Lambright <dlambrig> >Tested-by: Dan Lambright <dlambrig> (cherry picked from commit cb41de7c4a7d620dbab645f2b105286b68bde9a9) Change-Id: I56e4551657a234ac51fa2513dc46a48c19c4fac7 BUG: 1289602 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/12937 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Dan Lambright <dlambrig>
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.7.7, please open a new bug report. glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
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