From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS V4 calls for a NFS v3 mount
Date: Sun, 06 Apr 2014 20:01:24 +0200 [thread overview]
Message-ID: <53419674.7010509@gmx.de> (raw)
In-Reply-To: <CAAMCDec1OJFPKWPz-qnFedYiHXpag3=2qRYPwNHdQCC4tqaQ_Q@mail.gmail.com>
-----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
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-----
next prev parent reply other threads:[~2014-04-06 18:01 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 [this message]
2014-04-06 22:33 ` NeilBrown
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=53419674.7010509@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerheflin@gmail.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