Bug 447628 - Stale NFS file handle errors on readonly automounted directories
Summary: Stale NFS file handle errors on readonly automounted directories
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-20 21:22 UTC by Matt Dey
Modified: 2023-09-14 01:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:18:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 201211 0 medium CLOSED Stale NFS file handle errors occur on automounted directories 2021-02-22 00:41:40 UTC

Description Matt Dey 2008-05-20 21:22:04 UTC 
Description of problem:  NFS error handeling.


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


How reproducible: Almost always


Steps to Reproduce:
1. Mount a readonly NFS Filesyetm from a NetApp appliance
2. attempt to create a direoctory or touch a file in the RO filesystem
3.
  
Actual results: The directory the operation was attempted in will become stale.
 Returning the error "Stale NFS file handle"\


eg..

[/net/nasa04/vol/fast/fastbio/SecMap]
matt@unixdeva09$ ls -la
total 16
drwxr-xr-x  4 fastbio vision 4096 May 20 15:21 .
drwxr-xr-x 18 fastbio vision 4096 May 10 09:02 ..
drwxr-xr-x 13 fastbio vision 4096 Jan  4  2007 localvision
drwxr-xr-x  3 fastbio vision 4096 Jul  1  2005 releases

[/net/nasa04/vol/fast/fastbio/SecMap]
matt@unixdeva09$ touch junk
touch: cannot touch `junk': Read-only file system

[/net/nasa04/vol/fast/fastbio/SecMap]
matt@unixdeva09$ ls -la
ls: .: Stale NFS file handle

The error does not occur on RHEL4 boxes.

Expected results: Not a stale NFS file handle.


Additional info: Appears to be the same as bug 201211 Filed against Fedora.
Comment 1 Steve Dickson 2008-05-21 13:37:54 UTC 
What is the server that this is happening with and 
how reproducible is it?
Comment 2 Matt Dey 2008-05-21 13:57:44 UTC 
This is happening with a Netapp NFS server and is easily reproducible.
Comment 3 Steve Dickson 2008-05-30 19:43:42 UTC 
Can we get a bzip2 tshark network trace of this? Something similar
to 'tshark -w /tmp/bz447628.pcap host <server> ; bzip2 /tmp/bz447628.pcap'
Comment 4 RHEL Program Management 2014-03-07 12:14:25 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the  last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via  appropriate support channels and provide additional business and/or technical details about its importance to you.
Comment 5 RHEL Program Management 2014-06-02 13:18:25 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Comment 6 Red Hat Bugzilla 2023-09-14 01:12:45 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.