REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol) posted (#1) for review on master by Anuradha Talur (atalur)
REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol) posted (#2) for review on master by Anuradha Talur (atalur)
REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol During lookup and discover, currently read_subvol is based only on data_readable. read_subvol should be decided based on both data_readable and metadata_readable.) posted (#5) for review on master by Anuradha Talur (atalur)
REVIEW: http://review.gluster.org/11551 (cluster/afr : Examine data/metadata readable for read-subvol During lookup and discover, currently read_subvol is based only on data_readable. read_subvol should be decided based on both data_readable and metadata_readable.) posted (#7) for review on master by Anuradha Talur (atalur)
COMMIT: http://review.gluster.org/11551 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 36349fa250ace6109002dfa41305d9dcd54ce0a9 Author: Anuradha Talur <atalur> Date: Mon Aug 3 17:09:13 2015 +0530 cluster/afr : Examine data/metadata readable for read-subvol During lookup and discover, currently read_subvol is based only on data_readable. read_subvol should be decided based on both data_readable and metadata_readable. Credits to Ravishankar N for the logic of afr_first_up_child from http://review.gluster.org/10905/ . Change-Id: I98580b23c278172ee2902be08eeaafb6722e830c BUG: 1240244 Signed-off-by: Anuradha Talur <atalur> Reviewed-on: http://review.gluster.org/11551 Reviewed-by: Ravishankar N <ravishankar> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krutika Dhananjay <kdhananj> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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