From: "Steven A. DuChene" <sduchene@mindspring.com>
To: linux-kernel@vger.kernel.org
Cc: nfs@lists.sourceforge.net
Subject: NFS hangs between systems running 2.4.10-ac12 or 2.4.12-ac3
Date: Wed, 17 Oct 2001 23:42:40 -0400 [thread overview]
Message-ID: <20011017234240.S2015@lapsony.mydomain.here> (raw)
OK, I have noticed the last couple of days that I am getting extremely bad
file transfer (reads) response between systems here I have running various
recent flavors of 2.4.9-ac10, 2.4.10-ac12, and 2.4.12-ac3
The nfs server is running the 2.4.12-ac3 or 2.4.10-ac12. I have tried updating
the nfs-utils on it from the stuff supplied with SuSE-7.1 (0.2.1-17) to the
current 0.3.3 stuff with no change.
The clients are running either mount-2.9z or the more current mount-2.11l.
The client system running 2.9z has a 2.4.9-ac10 kernel and the other with
the 2.11l version of mount is running 2.4.10-ac12
This is most noticeable when I have a directory mounted from the server to the
clients that contains bzipped patch files and when I execute the following on
a client:
bzcat /mnt/net/archive/patch-2.4.12-ac3.bz2 |patch -p1
It just sits there for a LONG time waiting for the transfer to start.
I have tried playing around with various -onfsvers options when I mount
the remote directory but it seems to get worse when I try nfsvers=2 (I have
the above command hung in limbo right now on one of the client systems
where I tried -onfsvers=2
When I compile kernels I turn on the "Provide NFSv3 server support" options.
Also scp'ing the files between the systems proceeds at what seems like a
normal rate.
I have looked in the syslog and dmesg outputs when this occurs but nothing
unusual seems to be getting logged.
--
Steven A. DuChene sad@ale.org
linux-clusters@mindspring.com
sduchene@mindspring.com
http://www.mindspring.com/~sduchene/
reply other threads:[~2001-10-18 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011017234240.S2015@lapsony.mydomain.here \
--to=sduchene@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®