From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: volodya@mindspring.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS in 2.4.9
Date: 28 Aug 2001 12:18:06 +0200 [thread overview]
Message-ID: <shsbsl0ij35.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.20.0108271739400.15526-100000@node2.localnet.net>
In-Reply-To: volodya@mindspring.com's message of "Mon, 27 Aug 2001 17:50:21 -0400 (EDT)"
>>>>> " " == volodya <volodya@mindspring.com> writes:
> I have upgraded to 2.4.9 and NFS no longer works for me. I get
> ---------------------------------------------------------------
> NFS: NFSv3 not supported. nfs warning: mount version older
> than kernel
You forgot to enable NFSv3 support in your 2.4.9 kernel.
> ---------------------------------------------------------------
> even though I upgraded to the most recent version of util-linux
> (2.11h) and when reading certain files programs lock up and the
> kernel prints out the following messages:
> nfs: server node4 not responding, still trying nfs: server
> node4 not responding, still trying
> However, node4 is fine (I can telnet in it) and seems to work
> ok. (node4 is running 2.4.7, with knfsd).
In 99.999% of cases this is due to a network configuration
error. Usually it's things like running full-duplex against a
half-duplex capable switch etc.
TCP is less sensitive to this sort of thing than UDP is, so you won't
see it using telnet.
If you can't resolve where the problem lies, try setting rsize and
wsize manually to some smaller value.
Cheers,
Trond
next prev parent reply other threads:[~2001-08-28 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 21:50 NFS in 2.4.9 volodya
2001-08-28 10:18 ` Trond Myklebust [this message]
2001-08-29 1:03 ` volodya
2001-08-29 8:48 ` Trond Myklebust
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=shsbsl0ij35.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=volodya@mindspring.com \
/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