Red Hat Bugzilla – Bug 46771
nfs Client fileHandle cache updation is not consistent.
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
Description of problem:
RedHat 7.1 (fine with 6.2 and 7.0) even after getting an updated NFS
Handle from NFS Server in a lookup call, Linux NFS Client issues, calls
with old NFS Handle, which fails.
Steps to Reproduce:
*. Works fine with RedHat 6.2 and 7.0, but fails in 7.1
*. Against Netware NFS Server, exporting an NSS Volume
1. touch a
2. mv a b
3. link b c (or) cat b
Actual Results: Gives an I/O Error in either case.
Expected Results: Step 3 should create a hardlink c to b (or) display
content of b
* Say fileHandle of 'a' is fh1
* During mv, rename operation 'a' to 'b' is successful. (But NetWare NFS
Server changes the fileHandle of 'b' to fh2)
* Linux NFS Client now issues a Lookup for 'b' and gets the new fileHandle
fh2 (EXPECTING Linux NFS client to update it's fileHandle cache, at this
* Now during linking or reading, instead of issuing NFS Calls with updated
fh2 handle, NFS Calls are issued with fh1, leading to the I/O error, as
the handle may not always be valid now at the NFS Server.
Will attach or send the snoop traces soon or when asked for. Contact
Changed priority and severity as basic operations like fail due to this,
against the NFS Server.
Please Upgrade to supported Release