-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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
diss
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 NF
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 06 Apr 2014 20:01:24 +0200 Toralf Förster
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 mou
4 matches
Mail list logo