From: jlnance@unity.ncsu.edu
To: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Cc: gary.nifong@synopsys.com, jlnance@synopsys.com,
david.thomas@synopsys.com
Subject: NFS problems with Linux-2.4
Date: Tue, 13 May 2003 10:50:23 -0400 [thread overview]
Message-ID: <20030513145023.GA10383@ncsu.edu> (raw)
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
next reply other threads:[~2003-05-13 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 14:50 jlnance [this message]
2003-05-13 15:19 ` NFS problems with Linux-2.4 Trond Myklebust
2003-05-15 15:22 ` Jim Nance
2003-05-18 15:00 ` Trond Myklebust
2003-05-19 0:53 ` jlnance
2003-05-19 11:27 ` Trond Myklebust
2003-05-19 20:02 ` Jim Nance
[not found] ` <mailman.1053012601.1068.linux-kernel2news@redhat.com>
2003-05-21 11:39 ` Steve Dickson
2003-05-21 13:48 ` Trond Myklebust
2003-05-13 19:07 ` jjs
2003-05-13 19:24 ` Roland Dreier
2003-05-13 21:55 ` jjs
2003-05-13 23:11 ` Alan Cox
[not found] <482A3FA0050D21419C269D13989C6113127532@lavender-fe.eng.netapp.com>
2003-05-27 17:29 ` jlnance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030513145023.GA10383@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--cc=david.thomas@synopsys.com \
--cc=gary.nifong@synopsys.com \
--cc=jlnance@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.