Bug 832694

Summary: ESTALE error text should be reworded
Product: Red Hat Enterprise Linux 6 Reporter: Joe Julian <joe>
Component: glibcAssignee: Jeff Law <law>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3CC: fweimer, law, mcermak, mfranc, pfrankli
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: ESTALE error text specifically referred to NFS file systems. Consequence: Non-NFS file systems could also trigger this error which was confusing. Fix: The error message was rewritten to be more general and therefore, apply to all file systems that might trigger this error. Result: The error message is general enough to be used for all relevant file system types.
 Story Points: ---
Clone Of:
: 966259 1009681 (view as bug list) Environment:
Last Closed: 2013-02-21 07:05:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 966259, 1009681, 1009682, 1009687    
Attachments:
Description Flags
Possible fix
none
Very simple test case none

Description Joe Julian 2012-06-16 16:45:11 UTC 
ESTALE which is the base for the error text of "Stale NFS file handle" in sysdeps/gnu/errlist.c happens on *any* stale filehandle, totally independent from the fact if the underlying filesystem is NFS, is a corrupt ext2/3/4 filesystem with dangling inodes, or is fuse based. The error message should be reworded to be more generic instead of (in many cases) falsely pointing to NFS only.
Comment 2 Jeff Law 2012-06-29 04:44:49 UTC 
Created attachment 595180 [details]
Possible fix
Comment 3 Patsy Griffin 2012-08-06 19:37:35 UTC 
Created attachment 602568 [details]
Very simple test case
Comment 8 errata-xmlrpc 2013-02-21 07:05:00 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2013-0279.html