From owner-freebsd-fs@FreeBSD.ORG Tue Nov 8 01:10:01 2011 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 3E5F0106564A for ; Tue, 8 Nov 2011 01:10:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id EF01C8FC12 for ; Tue, 8 Nov 2011 01:10:00 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAKSAuE6DaFvO/2dsb2JhbABDhHumAIFyAQEFI1YbDgoCAg0ZAlkGE64BkjGBMIIXhE6BFgSIC4wWkgo X-IronPort-AV: E=Sophos;i="4.69,473,1315195200"; d="scan'208";a="143026268" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 07 Nov 2011 20:09:59 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id EBE67B3F0F; Mon, 7 Nov 2011 20:09:59 -0500 (EST) Date: Mon, 7 Nov 2011 20:09:59 -0500 (EST) From: Rick Macklem To: Robert Simmons Message-ID: <1275468075.1341984.1320714599943.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: rpc.umntall error on boot 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: Tue, 08 Nov 2011 01:10:01 -0000 Robert Simmons wrote: > On Sun, Nov 6, 2011 at 7:44 PM, Rick Macklem > wrote: > > What happens is that /etc/rc.d/nfsclient is executed before > > /etc/rc.d/mountd. It finds /var/db/mountdtab non-empty and tries to > > get a port from rpcbind for mountd. Since mountd isn't running yet, > > so it fails. Since telling the server on the same machine to clear > > out /var/db/mountdtab for the client is basically meaningless, > > failing > > shouldn't be a problem. > > Would there be any drawbacks to moving /etc/rc.d/nfsclient to later in > the process so that mountd is already running? > I don't quite know how to do that. nfsclient can be set to require mountd to be done first, but most clients won't want mountd to be done at all. I think the only time this happens is when an NFS server has mounted file systems on itself. Although some do this (for testing?), I don't think this is a practical configuration for production use. As such, I don't see the message as an issue? rick