From: NeilBrown <neilb@suse.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Roger Heflin <rogerheflin@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS V4 calls for a NFS v3 mount
Date: Mon, 7 Apr 2014 08:33:38 +1000 [thread overview]
Message-ID: <20140407083338.351db1c7@notabene.brown> (raw)
In-Reply-To: <53419674.7010509@gmx.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 4007 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 06 Apr 2014 20:01:24 +0200 Toralf Förster <toralf.foerster@gmx.de>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 04/06/2014 07:57 PM, Roger Heflin wrote:
> > No where in the mount command did you tell it that this was a
> > nfsversion 3 only mount, the mount name itself means nothing to
> > mount, so it tired nfs version 4 first then nfs version 3.
> >
> > Note this in the man page for nfs: nfsvers=n The NFS protocol
> > version number used to contact the server's NFS service. If the
> > server does not support the requested version, the mount
> > request fails. If this option is not specified, the client
> > negotiates a suitable version with the server, trying version 4
> > first, version 3 second, and version 2 last.
> >
>
> ick, I misunderstand the key word "nfs4" in /etc/fstab - I thought
> that (and only that) would activate any NFS v4 Calls :
>
> Hre all of my setting
> $ grep nfs /etc/fstab
> n22:/mnt/ramdisk /mnt/nfsv2 nfs auto,bg,intr,soft,nfsvers=2
> n22:/mnt/ramdisk /mnt/nfsv3 nfs auto,bg,intr,soft
> n22: /mnt/nfsv4 nfs4 auto,bg,intr,soft
That was used to indicate nfsv4 early in development, possibly to make sure
it didn't get used by default, but it was quickly realised that having a
separate filesystem type was confusing.
So while "nfs4" does still work an selected vers=4, it is deprecated. You
should always use "nfs" if possible.
BTW the nfs list is "linux-nfs@vger.kernel.org" - suitable for "noobs",
developers, and everyone in between.
NeilBrown
>
>
> Thx for explanation.
>
>
> > On Sun, Apr 6, 2014 at 12:27 PM, Toralf Förster
> > <toralf.foerster@gmx.de> wrote: Probably a question better suited
> > for a NFS noobs mailing list (is there any around ?) ...
> >
> > While playing with kernel 3.13.x, wireshark and NFS I realized,
> > that mounting a NFS v3 share results in NFS V4 Calls - is this
> > indented or a wireshark dissector issue ?
> >
> >
> > $ cat /etc/exports # /etc/exports: NFS file systems being exported.
> > See exports(5). /mnt/ramdisk
> > 192.168.0.0/16(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
> >
> >
> >
> > $ grep nfsv3 /etc/fstab n22:/mnt/ramdisk /mnt/nfsv3 nfs
> > auto,bg,intr,soft
> >
> - --
> MfG/Sincerely
> Toralf Förster
> pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iF4EAREIAAYFAlNBlnQACgkQxOrN3gB26U41HQD8D/KROgItC324iDevD33vJ6QS
> PcSWPcBTzimC0cMOfzkA/04ejAWOGGqyqNedV5Ps235rxqbxDWoiUS7M7iQtu/Wz
> =jJAD
> -----END PGP SIGNATURE-----
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIVAwUBU0HWQjnsnt1WYoG5AQLr+Q//az/LlGyQRBKGCcrNAEUxeI7msLur6aAR
6j/ecJkjNtI+D4o3WuUZQlkxnvjZ7uA9RacRbLc7UHDh7kWpJjsoCl/s6SkS1RY2
y3KHOY/vm6+jwBXRknbGPMjPDNDA34s0cok2/so6ELyL82Uxd/Zsrhua6/yxoj8D
6J2p2KLY6DqgmJnicTAmZf5F2gVCnL0cwuv16wKCsCrf24O0d9eXqjStYUV62jLX
m3JrzB8JxovT7LmU9jsH1ChE7PW6sAd92R1lzrgQM7XNLoy4Q3bggWBNcLOATRNp
V5uGXCOXW+mnnPCdwhQkK7hoJf4dpkodU+BDydZO/oet2kE84eQYM0oyl5Ebz+mR
nOKQwp7Y2Zitj4ZzAfa9KrxteZ6Pa5ISv0Olbjw/3W0aL148Y3UmEo9cT4kUzhAm
hiNzN7K2835vOVZvtCW3Woq+sN66v7Jp9Ig/6ZNAsAizH2oMl9F9k/fH6u8P9bV4
4Lc9nc9yo6IzFVlJYbM3wPMod70gQz9QNCNXvRH9m6ospV+wY/TFfvqYNCAE9msk
tjbKnfYCNoAdGgPSW2tHbpqM42ZwYpy6wu7gG3Io98CtsoUiJbG7meMj6FkkWOno
6dW8CVovxdGrdQP1cLQbyVUKX4XYDRzI2eCJI7sUH11Sn8o+Ft0rRtxzeLpE4s4t
3vGS4lERy+U=
=EiAW
-----END PGP SIGNATURE-----
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2014-04-06 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 17:27 NFS V4 calls for a NFS v3 mount Toralf Förster
2014-04-06 17:57 ` Roger Heflin
2014-04-06 18:01 ` Toralf Förster
2014-04-06 22:33 ` NeilBrown [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=20140407083338.351db1c7@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerheflin@gmail.com \
--cc=toralf.foerster@gmx.de \
/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.