[Bugs] [Bug 1278744] ec-readdir.t is failing consistently
bugzilla at redhat.com
bugzilla at redhat.com
Wed Nov 11 13:48:30 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1278744
--- Comment #1 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12562 committed in release-3.7 by Xavier
Hernandez (xhernandez at datalab.es)
------
commit 06b888bbeac61aa1234b43e398431529988c28b6
Author: Pranith Kumar K <pkarampu at redhat.com>
Date: Tue Nov 10 09:06:54 2015 +0530
cluster/ec: fix bug in update_good
Backport of http://review.gluster.com/12561
Problem:
Bricks that didn't participate in the fops are considered to be good. This
is
happening two fold.
Examples:
Case-1:
1) 2+1 volume. 'd1' directory on Brick-0 is bad.
2) readdir takes locks and lock->good_mask is '7'
3) readdir does xattrop and fop->mask is '6'.
4) because fop->expected is '1' lock->good_mask remains '7'
Case-2:
1) when all the bricks are up, it does lock + xattrop before op and figures
out
all the bricks are good.
2) By the time second operation starts brick-0 is down. Now lock->good_mask
will always have the '0' bit set as long as the operations are happening
on it.
because: "lock->good_mask &= ~fop->mask | fop->remaining" fop->mask
doesn't
have '0' th bit.
3) When it comes time to perform the final xattrop in update_size_version
brick-0 comes online because of which it gives the same version to
brick-0
as well thinking it has participated in all the transactions till then,
even
when it didn't participate in the transactions.
Fix:
Case-1's fix: Update lock->good_mask in ec_prepare_update_cbk with latest
good/bad bricks
Case-2's fix: Consider non-participating brick as bad.
BUG: 1278744
Change-Id: I5c2b07005107f3c067bac69da3b37ff39688bd69
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: http://review.gluster.org/12562
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ZUDb5trre8&a=cc_unsubscribe
More information about the Bugs
mailing list