From owner-freebsd-fs@FreeBSD.ORG Mon Jan 23 00:53:27 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84950106566C for ; Mon, 23 Jan 2012 00:53:27 +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 3F42F8FC08 for ; Mon, 23 Jan 2012 00:53:26 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAOquHE+DaFvO/2dsb2JhbABDhQmqIYIcgQsCDRkCoU+OC5B2gS+HW4IGgRYEiDuMXpJs X-IronPort-AV: E=Sophos;i="4.71,553,1320642000"; d="scan'208";a="156281201" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 22 Jan 2012 19:53:26 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 19C18B3FF1 for ; Sun, 22 Jan 2012 19:53:26 -0500 (EST) Date: Sun, 22 Jan 2012 19:53:26 -0500 (EST) From: Rick Macklem To: freebsd-fs@freebsd.org Message-ID: <700804423.708964.1327280006066.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: should mount -u fail or silently ignore options? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2012 00:53:27 -0000 Hi, There is a bug in the NFS clients, where a "mount -u -o udp /mnt" will cause any threads that have an RPC in progress to hang, if the mount previously was using too large an rsize/wsize. This case can easily be detected in nfs_mount(). However, my question is... - Should the "mount -u" fail and return an error OR Silently ignore the "udp" option and return ok. I ask because the NFS clients currently silently clear flags like NFSMNT_NFSV3 and NFSMNT_NOLOCKD because they can't be changed and then nfs_mount() returns 0, assuming any other options work. I am also not sure if having a "mount -u" fail for a diskless root fs will result in serious problems. (I don't currently have a diskless root setup to try this on.) Any comments w.r.t. which is the preferred way to handle this? rick