From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Pascal Schmidt <der.eremit@email.de>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: [NFS] attempt to use V1 mount protocol on V3 server
Date: 03 Sep 2003 19:33:31 -0400 [thread overview]
Message-ID: <shsptihla5w.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0309040004230.4629-100000@neptune.local>
>>>>> " " == Pascal Schmidt <der.eremit@email.de> writes:
> a) when unmounting an NFS volume, the server gets sent an umount
> request indicating version 1 of the protocol, sending a
> version 3 umount is not even attempted
> b) when something goes wrong during the NFSv3 mount, the kernel
> seems to fall back to NFSv2, re-attempting the mount with
> mount protocol version 1
> I think both of this should not be done when the remote side
> does not advertise mount protocol version 1 support.
> Question: is this a problem of the user-space mount utility or
> is it an in-kernel problem?
a) Is a feature of the 'mount' program. An NFS server should in any
case not rely on the umount being sent: a client may have crashed
or been firewalled, or whatever...
b) Is a kernel feature which will never trigger if you are passing a
correct filehandle from your mountd.
Cheers,
Trond
next prev parent reply other threads:[~2003-09-03 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 22:13 [NFS] attempt to use V1 mount protocol on V3 server Pascal Schmidt
2003-09-03 23:33 ` Trond Myklebust [this message]
[not found] <rO94.822.25@gated-at.bofh.it>
[not found] ` <rPop.1vp.13@gated-at.bofh.it>
2003-09-04 2:08 ` Pascal Schmidt
2003-09-04 2:17 ` Trond Myklebust
2003-09-04 2:40 ` Pascal Schmidt
2003-09-04 4:37 ` Trond Myklebust
2003-09-04 14:27 ` Pascal Schmidt
2003-09-04 15:24 ` 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=shsptihla5w.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=der.eremit@email.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).