[Bugs] [Bug 1419824] repeated operation failed warnings in gluster mount logs with disperse volume
bugzilla at redhat.com
bugzilla at redhat.com
Tue Feb 7 13:29:52 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1419824
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16550 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit 66cc803f1134016a34e3b8d9f55254029877df53
Author: Ashish Pandey <aspandey at redhat.com>
Date: Thu Jan 19 18:20:44 2017 +0530
cluster/disperse: Do not log fop failed for lockless fops
Problem: Operation failed messages are getting logged
based on the callbacks of lockless fop's. If a fop does
not take a lock, it is possible that it will get some
out of sync xattr, iatts. We can not depend on these
callback to psay that the fop has failed.
Solution: Print failed messages only for locked fops.
However, heal would still be triggered.
> Change-Id: I4427402c8c944c23f16073613caa03ea788bead3
> BUG: 1414287
> Signed-off-by: Ashish Pandey <aspandey at redhat.com>
> Reviewed-on: http://review.gluster.org/16435
> Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
> 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>
Change-Id: I8728109d5cd93c315a5ada0a50b1f0f158493309
BUG: 1419824
Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Reviewed-on: https://review.gluster.org/16550
Tested-by: Xavier Hernandez <xhernandez at datalab.es>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Smoke: Gluster Build System <jenkins at build.gluster.org>
--
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=y33pXvb9yh&a=cc_unsubscribe
More information about the Bugs
mailing list