From: Michael Feig <meikel@scripps.edu>
To: nfs@lists.sourceforge.net
Subject: NFS client eventually stalls with automount
Date: Wed, 26 Jun 2002 17:23:52 -0700 [thread overview]
Message-ID: <3D1A5B18.7050601@scripps.edu> (raw)
Hi!
Here is the problem. When I try to read and write at the same time (it
shows up when trying to create a tar file)
on an automounted directory the process starts up fine, but pretty
quickly slows down and eventually
stalls completely. The process is then frozen but reacts to a kill
signal after a few minutes.
At the same time I have seen kernel messages such as
Jun 25 17:37:05 vangogh kernel: nfs: task 39046 can't get a request slot
Jun 25 17:37:37 vangogh kernel: nfs: server bebop OK
....
Networking seems to be fine otherwise, in particular I have no problems
when I just read OR write from the same
disk (as when I would create a tar file on a local disk from the mounted
directory).
I ran into this with the RedHat 7.3 distribution kernel (2.4.18) but
also tried the very latest 2.4.19-rc1 with
Trond's latest NFS_ALL patches (for pre10).
The machine from where the disk is server is running SGI IRIX 6.5 and
nfsstat shows that I am using
NFS V3.
So far I did not change any NFS options such as buffer size yet.
Any suggestions?
Thanks.
--
Michael Feig meikel@scripps.edu
The Scripps Research Institute, La Jolla, CA
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-06-27 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 0:23 Michael Feig [this message]
2002-06-27 3:53 ` NFS client eventually stalls with automount H. J. Lu
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=3D1A5B18.7050601@scripps.edu \
--to=meikel@scripps.edu \
--cc=nfs@lists.sourceforge.net \
/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.