[Bugs] [Bug 1449924] When either killing or restarting a brick with performance.stat-prefetch on , stat sometimes returns a bad st_size value.
bugzilla at redhat.com
bugzilla at redhat.com
Fri May 12 13:35:18 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1449924
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17244 committed in release-3.11 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit a9c09c5fe97c6861fa3b500b690ebd5df063d0be
Author: Ravishankar N <ravishankar at redhat.com>
Date: Tue May 9 02:31:39 2017 +0530
afr: send the correct iatt values in fsync cbk
Problem:
afr unwinds the fsync fop with an iatt buffer from one of its children
on whom fsync was successful. But that child might not be a valid read
subvolume for that inode because of pending heals or because it happens
to be the arbiter brick etc. Thus we end up sending the wrong iatt to
mdcache which will in turn serve it to the application on a subsequent
stat call as reported in the BZ.
Fix:
Pick a child on whom the fsync was successful *and* that is readable as
indicated in the inode context.
> Reviewed-on: https://review.gluster.org/17227
> CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
> Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
> NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
> Smoke: Gluster Build System <jenkins at build.gluster.org>
(cherry picked from commit 1a8fa910ccba7aa941f673302c1ddbd7bd818e39)
Change-Id: Ie8647289219cebe02dde4727e19a729b3353ebcf
BUG: 1449924
RCA'ed-by: Miklós Fokin <miklos.fokin at appeartv.com>
Signed-off-by: Ravishankar N <ravishankar at redhat.com>
Reviewed-on: https://review.gluster.org/17244
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
--
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=xMdzGJzuVy&a=cc_unsubscribe
More information about the Bugs
mailing list