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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/13621 (protocol/server: Do not log ENOENT in readv) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
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 (pkarampu)
COMMIT: http://review.gluster.org/13621 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit b145cd15ded130078c9f1105e76f35d0886e62d5 Author: Pranith Kumar K <pkarampu> 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. Change-Id: I8ae53c29d6a66f6a65081c281a9a5c205f53766b BUG: 1315168 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/13621 CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Ashish Pandey <aspandey> Reviewed-by: Jeff Darcy <jdarcy> Smoke: Gluster Build System <jenkins.com>
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user