Bug 1405902
Summary: | Fix spurious failure in tests/bugs/replicate/bug-1402730.t | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Krutika Dhananjay <kdhananj> | |
Component: | replicate | Assignee: | Krutika Dhananjay <kdhananj> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.10.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1406739 1406740 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-06 17:40:20 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: | ||||
Bug Blocks: | 1406739, 1406740 |
Description
Krutika Dhananjay
2016-12-19 06:19:43 UTC
And whenever this issue is hit, the names a,b and c are healed into the bad brick, which probably means that name heal kicked in somewhere and did the new entry marking. [root@krutika-1 glusterfs-3.10dev]# cd /d/backends/ [root@krutika-1 backends]# ls * patchy0: a patchy1: a patchy2: a [root@krutika-1 backends]# ls */a patchy0/a: b patchy1/a: b patchy2/a: b [root@krutika-1 backends]# ls */a/b patchy0/a/b: c patchy1/a/b: c patchy2/a/b: c [root@krutika-1 backends]# ls */a/b/c patchy0/a/b/c: file patchy1/a/b/c: file patchy2/a/b/c: Will confirm the same by printing log messages everytime name heal happens. Indeed it is name heal that is doing the new entry marking, as is evident from the following: [2016-12-19 06:41:28.916995]:++++++++++ G_LOG:tests/bugs/replicate/bug-1402730.t: TEST: 31 touch file ++++++++++ [2016-12-19 06:41:29.049544] I [MSGID: 108031] [afr-common.c:2335:afr_local_discovery_cbk] 0-patchy-replicate-0: selecting local read_child patchy-client-0 [2016-12-19 06:41:29.050808] I [MSGID: 108031] [afr-common.c:2335:afr_local_discovery_cbk] 0-patchy-replicate-0: selecting local read_child patchy-client-1 [2016-12-19 06:41:29.051916] I [MSGID: 108031] [afr-common.c:2335:afr_local_discovery_cbk] 0-patchy-replicate-0: selecting local read_child patchy-client-2 [2016-12-19 06:41:29.053024] I [afr-common.c:2508:afr_lookup_selfheal_wrap] 0-patchy-replicate-0: About to name heal a [2016-12-19 06:41:29.069815] I [afr-common.c:2508:afr_lookup_selfheal_wrap] 0-patchy-replicate-0: About to name heal b [2016-12-19 06:41:29.085733] I [afr-common.c:2508:afr_lookup_selfheal_wrap] 0-patchy-replicate-0: About to name heal c REVIEW: http://review.gluster.org/16193 (tests: Fix spurious failure in tests/bugs/replicate/bug-1402730.t) posted (#1) for review on master by Krutika Dhananjay (kdhananj) REVIEW: http://review.gluster.org/16193 (tests: Fix spurious failure in tests/bugs/replicate/bug-1402730.t) posted (#2) for review on master by Krutika Dhananjay (kdhananj) COMMIT: http://review.gluster.org/16193 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 8094e5005fbe9016ae039003bcc617d1172385b3 Author: Krutika Dhananjay <kdhananj> Date: Mon Dec 19 12:22:29 2016 +0530 tests: Fix spurious failure in tests/bugs/replicate/bug-1402730.t Replace the EXPECT '00000001' with EXPECT_NOT '00000000'. This is because occasionally a name-heal is performing new-entry marking on 'c' causing the pending entry changelog on it to become '00000002'. Change-Id: I30916e6266534d18899cfa5771c892db8c51ad9a BUG: 1405902 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/16193 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> 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.10.0, please open a new bug report. glusterfs-3.10.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://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/ |