From owner-freebsd-questions@FreeBSD.ORG Fri Jan 30 20:42:35 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E82B5106566C for ; Fri, 30 Jan 2009 20:42:35 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id B37838FC16 for ; Fri, 30 Jan 2009 20:42:35 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id DA043AFBCCB; Fri, 30 Jan 2009 11:42:34 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Fri, 30 Jan 2009 11:42:34 -0900 User-Agent: KMail/1.9.10 References: <200901291308.47418.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901301142.34624.fbsd.questions@rachie.is-a-geek.net> Cc: Arjan van der Oest Subject: Re: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 20:42:36 -0000 On Friday 30 January 2009 04:36:04 Arjan van der Oest wrote: > Mel wrote: > >> - why does the system tries to mount the nfs filesystem from the > > fstab > > >> while nfs_client_enable has been set to no in rc.conf? > > > >Because there is no relation between the two. You could be using a 3rd > >party nfs kernel module. > > Yes, but I am not. I'm using the default kernel option which I believe > is enabled with the mentioned rc.conf switch, or am I wrong here? Yes, but why should mount(8) check /etc/rc.conf? The relation is reverse, rc(8) should give services the right(tm) arguments. > >> And more bizarre: when interrupting the > >> mountcritremote script the share has been actually mounted, so it > > Also what puzzles me is the fact that a new identical setup box has no > problem. As I wrote earlier the only difference is that I did not select > the 'enable nfs client' from the sysinstall this time. I have not used > any of the mentioned flags on the second box too, so why does it work on > that machine? Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.