REVIEW: http://review.gluster.org/13184 (cluster/dht: Handle failure in getxattr) posted (#1) for review on release-3.7 by Susant Palai (spalai)
REVIEW: http://review.gluster.org/13184 (cluster/dht: Handle failure in getxattr) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/13184 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit f3426ccc95133f8b5c946f98867090c636305d6e Author: Susant Palai <spalai> Date: Wed Dec 2 04:59:55 2015 -0500 cluster/dht: Handle failure in getxattr Problem: Currently even if we have received xattrs from any one of the subvolume, we unwind with error in case the last subvol (which unwinds) received a negative response. To handle the case check if any of the subvolume has received a response and pass it down. BUG: 1296108 Change-Id: I5279442fabd500934d04509d83ae87fdd69388e2 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/12845 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/13184 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org>
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