NFS client defaults to a mix of UDP and TCP

I had thought that I had posted w.r.t. before, but can't find it in
the archive (which might explain why I didn't get any responses:-).

The current mount_nfs defaults to using UDP for the mount protocol
and then switches to using TCP for the actual mount. (When neither
"udp" nor "tcp" mount options are specified.) I don't think I
changed it to be this way, because I recall noticing it when I
added changes for the experimental NFS client and thought it was
"weird", but assumed that it had been that way for a long time.

It now appears that it was introduced post-FreeBSD7 at r176198,
which changed the default for NFS to TCP, but didn't switch the
default for the mount protocol to TCP.

The ancient history of this is that "once upon a time" there were
NFS servers that could do NFS over TCP, but only supported UDP for
the mount protocol and there was an option called "mntudp" for that
case. I can't imagine that any server still needs this case, but
it appears to have become the default.

The default works fine for servers that support both UDP and TCP,
but result in a non-functional mount point when the server only
supports UDP. (See recent email thread on freebsd-stable called
"NFS issues on 8.0-BETA4".)

Is this something that should be changed? rick
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Redhat Enterprise 4 and 15 second delays with NFS via TCP
    ... I don't know NFS well ... TCP layer, but there is also the question of what else you should ... Some servers get into horribly knotted ... states when there are network problems. ...
    (comp.protocols.nfs)
  • SuSE 10.0 NFS vs. Firewall
    ... I am attempting to get NFS working; both client and server are running ... 3/min burst 5 LOG level warning tcp-options ip-options prefix ... 3/min burst 5 state NEW udp dpt:sunrpc LOG level warning tcp-options ... 3/min burst 5 state NEW tcp dpt:sunrpc LOG level warning tcp-options ...
    (alt.os.linux.suse)
  • Re: Firewall problems with NFS
    ... It seems to only allow use as an NFS client, since that worked fine when I tested it. ... U was surprised to see that TCP with tcp_adv_win_size=5 and rsize=8192 was as fast as UDP, ... 100005 1 udp 841 mountd ...
    (Fedora)
  • Trying to get NFS working with FreeBSD & OS X
    ... NFS client on a Mac OS X box. ... 100000 4 tcp 111 portmapper ... 100000 4 udp 111 portmapper ... 100021 0 udp 617 nlockmgr ...
    (comp.unix.bsd.freebsd.misc)
  • Re: nfs troubles
    ... I'm having trouble getting NFS set up. ... I have nfs-common and nfs-kernel-server installed on the server and nfs-common installed on the client. ... 100000 2 tcp 111 portmapper ... 100000 2 udp 111 portmapper ...
    (Debian-User)