Bug 1335433
Summary: | Self heal shows different information for the same volume from each node | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> |
Component: | sharding | Assignee: | Pranith Kumar K <pkarampu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.8.0 | CC: | atalur, bugs, kdhananj, pcuzner, pkarampu, ravishankar, sabose |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1334566 | Environment: | |
Last Closed: | 2016-06-16 14:06:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1334566 | ||
Bug Blocks: | 1335429 |
Description
Pranith Kumar K
2016-05-12 08:42:20 UTC
REVIEW: http://review.gluster.org/14303 (cluster/afr: Handle non-zero source in heal-info decision) posted (#1) for review on release-3.8 by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/14303 committed in release-3.8 by Niels de Vos (ndevos) ------ commit 91dcbfb58ac06b84940d3de9049514465a3acd6b Author: Pranith Kumar K <pkarampu> Date: Thu May 12 13:55:44 2016 +0530 cluster/afr: Handle non-zero source in heal-info decision Backport of http://review.gluster.org/14302 Problem: Spurious entries are reported in heal info when the mount is on second/third brick of the replica pair because local-child is given preference in selecting source. The code is supposed to suggest the file needs heal if the (source < 0) (failure code path), but instead it is written as if any non-zero value is considered failure. Fix: Treat +ve source as success case BUG: 1335433 Change-Id: Iede983b6560622964e91306405587da3f1de5748 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/14303 Reviewed-by: Krutika Dhananjay <kdhananj> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Ravishankar N <ravishankar> Reviewed-by: Anuradha Talur <atalur> Reviewed-by: Niels de Vos <ndevos> 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 |