From owner-freebsd-stable@FreeBSD.ORG Mon May 6 23:09:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4E8A960E for ; Mon, 6 May 2013 23:09: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 18C29E43 for ; Mon, 6 May 2013 23:09:26 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEAAA3iFGDaFvO/2dsb2JhbABQgz6DPLtMgRx0gh8BAQEEAQEBIAQnIAsFFg4KAgINGQIpAQkmBggHBAEcBIdrDK91kHCBJIxbfjQHgkCBEwOUbIJCgSaQDoMpIDKBBDU X-IronPort-AV: E=Sophos;i="4.87,624,1363147200"; d="scan'208";a="28612602" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 06 May 2013 19:09:20 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 4C5F0B3F26; Mon, 6 May 2013 19:09:20 -0400 (EDT) Date: Mon, 6 May 2013 19:09:20 -0400 (EDT) From: Rick Macklem To: Zaphod Beeblebrox Message-ID: <1344702318.161364.1367881760297.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: multiple NFS mounts with bg,retrycount=0 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) Cc: FreeBSD Stable , Navdeep Parhar X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 23:09:27 -0000 Zaphrod Beeblebrox wrote: > [about double background NFS mounts] > > I'm not sure on the fix to this, but I'm pretty sure it's because we > retry > the mount -a stuff twice at startup. If you watch your console, you'll > see > two places where it will "mount NFS filesystems" during boot. > > ... well... a fix to this would be to _not_ do that twice ... but hey > :). There was just a commit to head (r250253) which adds a "-L" option to mount, so that only "late" file systems are mounted, to avoid this. Without this, what I think happens is: A - "mount -a" --> initial mount attempt fails and goes background B - "mount -a -l" --> succeeds in doing the mount, since it isn't mounted yet - background mount_nfs from (A) wakes up and does the mount again Yes, doing the mount twice will work and the second mount covers up the first one. This is relatively harmless, although it will take 2 umounts to get rid of the mount (the first umount just uncovers the first mount). You could try marking the /etc/fstab line(s) for the mounts "late". (since you use "bg", I'm assuming they aren't needed to be done for the startup scripts) That way they would only be mounted for the "mount -a -l" case, I think. rick > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org"