RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
We experienced very infrequent FNF errors (3 occurrences in one month period) when running hadoop benchmarks: Wordcount, TestDFSIO read and Pi Estimator, on glusterfs.  During the time period when the errors occurred we had a disk fail in our RAID6 array which the gluster volume resides on. Since we replaced the downed disk we have not been able to reproduce this problem.  


Version-Release number of selected component (if applicable):


How reproducible: Cannot be reproduced at this time


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Upstream fix available at https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=154210ccb3a871e631bf39fdeb7a8731d98af87b

Note about the comment about disk replacement - the actual 'no such file or directory' (or 'File not Found' in Java lingo) seems not to be caused by the disk failure/replacement, but probably just impacted probability with timing/races because of delays.

A correction: 'File not Found' is a generic exception Java throws. It was found during debugging that the system errno was ESTALE and not ENOENT (Java just throws FNF exception even for ESTALE). Hopefully that clarifies the intention of the patch.

Patch(es) available on kernel-3.10.0-191.el7

Test failed on kernel-3.10.0-190.el7, got failed message:
/mnt/one/file: Stale file handle

Test passed on kernel3.10.0-220.el7

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0290.html