+++ This bug was initially created as a clone of Bug #1337777 +++ Description of problem: 14:35:56 [21:35:56] Running tests in file ./tests/bugs/write-behind/bug-1279730.t 14:36:00 No volumes present 14:36:01 read should've failed as previous write would've failed with EDQUOT, but its successfultar: Removing leading `/' from member names 14:36:03 ./tests/bugs/write-behind/bug-1279730.t .. 14:36:03 1..15 14:36:03 ok 1, LINENUM:10 14:36:03 ok 2, LINENUM:11 14:36:03 ok 3, LINENUM:12 14:36:03 ok 4, LINENUM:14 14:36:03 ok 5, LINENUM:15 14:36:03 ok 6, LINENUM:16 14:36:03 ok 7, LINENUM:17 14:36:03 ok 8, LINENUM:18 14:36:03 ok 9, LINENUM:19 14:36:03 ok 10, LINENUM:21 14:36:03 ok 11, LINENUM:24 14:36:03 not ok 12 , LINENUM:26 14:36:03 FAILED COMMAND: ./tests/bugs/write-behind/bug-1279730 /mnt/glusterfs/0/file "gluster --mode=script --wignore volume quota patchy limit-usage / 1024" 14:36:03 ok 13, LINENUM:28 14:36:03 ok 14, LINENUM:30 14:36:03 ok 15, LINENUM:31 14:36:03 Failed 1/15 subtests 14:36:03 14:36:03 Test Summary Report 14:36:03 ------------------- 14:36:03 ./tests/bugs/write-behind/bug-1279730.t (Wstat: 0 Tests: 15 Failed: 1) 14:36:03 Failed test: 12 14:36:03 Files=1, Tests=15, 7 wallclock secs ( 0.02 usr 0.00 sys + 1.18 cusr 0.39 csys = 1.59 CPU) 14:36:03 Result: FAIL 14:36:03 End of test ./tests/bugs/write-behind/bug-1279730.t Version-Release number of selected component (if applicable): How reproducible: inconsistent, but surely there is some race causing this issue. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Vijay Bellur on 2016-05-20 01:05:52 EDT --- REVIEW: http://review.gluster.org/14443 (tests/write-behind: move 1279730.t to BAD tests) posted (#1) for review on master by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/14445 (tests/write-behind: move 1279730.t to BAD tests) posted (#1) for review on release-3.8 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/14445 (tests/write-behind: move 1279730.t to BAD tests) posted (#2) for review on release-3.8 by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/14445 committed in release-3.8 by Vijay Bellur (vbellur) ------ commit 5fa5ec2aa6faf2a564443d8e2a88cad473f37d30 Author: Raghavendra G <rgowdapp> Date: Fri May 20 10:29:05 2016 +0530 tests/write-behind: move 1279730.t to BAD tests There is a race condition which is causing the test to fail. For lack of bandwidth I am moving this test to BAD, though clearly there is some issue with codebase. Backport of: > BUG: 1337777 > Change-Id: If4f3eff8a5985f37a4dee65d2df29fa7b6bda7ae > Reviewed-on: http://review.gluster.org/14443 > Signed-off-by: Raghavendra G <rgowdapp> BUG: 1337780 Change-Id: If4f3eff8a5985f37a4dee65d2df29fa7b6bda7ae Signed-off-by: Raghavendra G <rgowdapp> Reviewed-on: http://review.gluster.org/14445 CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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