[Bugs] [Bug 1210562] Dist-geo-rep: Too many "remote operation failed: No such file or directory" warning messages in auxilary mount log on slave while executing "rm -rf"
bugzilla at redhat.com
bugzilla at redhat.com
Sun Apr 26 05:16:19 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1210562
--- Comment #10 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10184 committed in master by Vijay Bellur
(vbellur at redhat.com)
------
commit 009363dbc162dca71efce6689497b3948a14bd82
Author: Kotresh HR <khiremat at redhat.com>
Date: Thu Apr 9 19:00:58 2015 +0530
geo-rep: Don't log geo-rep safe errors in mount logs
EEXIST and ENOENT are safe errors for geo-replication.
Since mkdir is captured in all the bricks of the changelog.
mkdir is tried multiple times as per the number of bricks.
The first one to process by gsyncd will succeed and all
others will get EEXIST. Hence EEXIST is a safe error
and can be ignored. Similarly ENOENT also in rm -rf case.
And also gsyncd validates these errors and log them in
master if it is genuine error. This is coming up with
the patch http://review.gluster.org/#/c/10048/
Hence ignoring above said safe errors.
Change-Id: I10ae86b11d49c7c3ba2be3110dace6b33daa509e
BUG: 1210562
Signed-off-by: Kotresh HR <khiremat at redhat.com>
Reviewed-on: http://review.gluster.org/10184
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list