Red Hat Bugzilla – Bug 1315168
Fd based fops should not be logging ENOENT/ESTALE
Last modified: 2016-06-16 09:59:22 EDT
Description of problem:
Ideally fd based operations shouldn't be logging ENOENT/ESTALE. But it can happen when self-heal is yet to happen where the files need to be re-created etc.
So don't log them as ERRORS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/13621 (protocol/server: Do not log ENOENT in readv) posted (#1) for review on master by Pranith Kumar Karampuri (email@example.com)
REVIEW: http://review.gluster.org/13621 (protocol/server: Do not log ENOENT/ESTALE in fd based fops) posted (#2) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13621 committed in master by Pranith Kumar Karampuri (email@example.com)
Author: Pranith Kumar K <firstname.lastname@example.org>
Date: Mon Mar 7 11:52:18 2016 +0530
protocol/server: Do not log ENOENT/ESTALE in fd based fops
When fd-fops come on anon-fds there is a chance to log ENOENT/ESTALE for them.
Log it as DEBUG.
Signed-off-by: Pranith Kumar K <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Ashish Pandey <firstname.lastname@example.org>
Reviewed-by: Jeff Darcy <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.