NFS problems with Linux-2.4

jlnance@unity.ncsu.edu
Tue, 13 May 2003 10:50:23 -0400


Hello all,

I am having some problems with NFS which I suspect may be a bug in the
2.4 kernels. I can probably come up with a small testcase, but before I do
that I would like to describe the problem and see if it is something that
is susposed to work. Perhaps I simply do not understand the guarantees
that NFS makes.

The setup is like this. I have two machines which share an NFS mounted
directory. The NFS server is a network appliance box. Machine A
does an fopen/fwrite/fclose to create a file on the NFS filesystem. It
then sends a message to machine B. Machine B then attemps to fopen the
file, but fopen fails (as does stat). If I add code that sleeps for a
couple of seconds and retries the fopen then everything works.

I have seen the problem on both IA64 machines running the kernel 2.4.18
from Red Hats Advanced Server and on x86 machines running Red Hats
2.4.7-10smp kernel. I have not tried other linux kernels (I am not root),
but I have run the same program under Solaris (sparc) and have never
observed this.

The IA64 and x86 machines were on different networks and using different
network appliance servers. The IA64 /proc/mounts entry is:

na1:/vol/h1/home /remote/na1h1home nfs rw,v3,rsize=4096,wsize=4096,hard,intr,udp,lock,addr=na1 0 0

and the x86 entry is:

na1-rtp:/vol/vol0/home/jlnance /home/jlnance nfs rw,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=na1-rtp 0 0

If you would like more information, please let me know.

Thanks,

Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/