Hi,
r230516, which was just committed to head/current, will result in
a "mount -u -o udp /path" failing if the mount is using an
rsize/wsize/readdirsize of greater than 16384 (which will be the
case of a default sized TCP mount).
As such, specifying "udp" or "mntudp" options in the /etc/fstab
entry for "/" on a diskless NFS client could result in the "mount -u"
failing. I'd suggest that "udp" and "mntudp" be avoided for this
case, if you are using the default of TCP for the root mnt done
when the diskless client is booted.
The discussion on freebsd-fs@ seemed to indicate returning an error
was preferable to silently ignoring the "udp/mntudp" option for this
case.
Hopefully this won't cause many people grief, rick
ps: Since doing the above could cause errors with both the NFS
clients for the root, I suspect few do the above.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
