From owner-freebsd-current@FreeBSD.ORG Wed Jan 25 00:32:03 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 732A1106566B for ; Wed, 25 Jan 2012 00:32:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 30ABA8FC13 for ; Wed, 25 Jan 2012 00:32:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAPRLH0+DaFvO/2dsb2JhbABChQmqM4IcgQsCDRkCoWCOC5E2gS+CT4UMAQYGCQUBAQIBCQIYCgIDgkgGAgUBBQoBAwkKAQYCAl0zggaBFgSIP4xekmw X-IronPort-AV: E=Sophos;i="4.71,565,1320642000"; d="scan'208";a="156644400" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 24 Jan 2012 19:32:02 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 206FAB3F08 for ; Tue, 24 Jan 2012 19:32:02 -0500 (EST) Date: Tue, 24 Jan 2012 19:32:02 -0500 (EST) From: Rick Macklem To: freebsd-current@freebsd.org Message-ID: <666472979.73336.1327451522107.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Subject: Heads Up: NFS clients can now fail "mount -u -o udp..." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 00:32:03 -0000 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.