From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: volodya@mindspring.com
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: NFS in 2.4.9
Date: Wed, 29 Aug 2001 10:48:19 +0200 [thread overview]
Message-ID: <15244.44115.209683.288790@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.20.0108282041120.23923-100000@node2.localnet.net>
In-Reply-To: <shsbsl0ij35.fsf@charged.uio.no> <Pine.LNX.4.20.0108282041120.23923-100000@node2.localnet.net>
>>>>> " " == volodya <volodya@mindspring.com> writes:
>> > NFS: NFSv3 not supported. nfs warning: mount version older
>> > than kernel
>>
>> You forgot to enable NFSv3 support in your 2.4.9 kernel.
> I did.. I'll make clean and recompile the kernel again, just in
> case. But still: why complain about mount ? Why allow to mount
> a partition ? I do not think this is the cause (also see
> below).
The mount format changed when we added NFSv3. The new format is
backward compatible, but we still print out a message in order to
ensure people get the combination NFS + mount correct.
> the interface. Setting wsize and rsize to 5000 helped - thank
> you very much ! I guess that between 2.4.7 and 2.4.9 the
> default rsize and wsize went up.
No. The default should still be the same. I changed the latter last in
the 2.4.0 pre series. You can check what the actual value is using
'/proc/mounts'.
> Now I am wondering what is wrong with large udp packets ? (my
> mtu is 1500 and they do get chopped up in smaller packets, but
> so do size 5524). Any ideas ?
You're probably seeing fragments disappearing. UDP has no mechanism
detect this, so when it happens, the RPC layer first has to time out
and then resend the entire request. In TCP connections, only the
missing fragment needs to be resent.
Now as to the reason why fragments are disappearing, I suggest you
look at your network layout and try to measure (with the aid of a
packet sniffer such as tcpdump) on which segment the loss is occuring.
Cheers,
Trond
prev parent reply other threads:[~2001-08-29 8:48 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
2001-08-29 1:03 ` volodya
2001-08-29 8:48 ` Trond Myklebust [this message]
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=15244.44115.209683.288790@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