Red Hat Bugzilla – Bug 227249
RHEL4.5 NFSv2 intermittently fails connectathon basic test 7 when run against solaris NFS server
Last modified: 2007-11-16 20:14:55 EST
Connectathon basic test 7 (which tests renaming and hard linking) intermittently
fails when run against a Solaris 10 NFS server.
Created attachment 147289 [details]
patch to add some missing inode revals
This patch seems to correct the problem. Without it, the test was pretty
regularly failing to notice that the i_nlink count had been incremented after
the link call. With this patch though, it seems to work. Looks like it may also
prevent some other v2 problems as well...
A very easy reproducer for this. Mount a NFSv2 filesystem:
# cd mounted_filesystem
# mkdir d1 d2
# touch d1/foo; ln d1/foo d2/bar; stat d1/foo
Size: 0 Blocks: 8 IO Block: 4096 regular empty file
Device: 11h/17d Inode: 1048679 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2007-02-16 10:56:06.000000000 -0500
Modify: 2007-02-16 10:56:06.000000000 -0500
Change: 2007-02-16 10:56:06.000000000 -0500
Links should be 2 here. If you wait a few seconds and stat it again, it is.
Created attachment 148245 [details]
respun patch that just includes the bit for nfs_proc_link
This patch is a smaller patch that just corrects the problem in the reproducer
without the other bits that we may not need.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
committed in stream U6 build 55.4. A test kernel with this patch is available
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.