From owner-freebsd-hackers@FreeBSD.ORG  Fri Mar  2 17:11:19 2007
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id A34F516A400
	for <freebsd-hackers@freebsd.org>; Fri,  2 Mar 2007 17:11:19 +0000 (UTC)
	(envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org)
Received: from mired.org (vpn.mired.org [66.92.153.74])
	by mx1.freebsd.org (Postfix) with SMTP id 4649813C49D
	for <freebsd-hackers@freebsd.org>; Fri,  2 Mar 2007 17:11:19 +0000 (UTC)
	(envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org)
Received: (qmail 21141 invoked by uid 1001); 2 Mar 2007 17:12:49 -0000
Received: by bhuda.mired.org (tmda-sendmail, from uid 1001);
	Fri, 02 Mar 2007 12:12:49 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17896.23312.980989.68558@bhuda.mired.org>
Date: Fri, 2 Mar 2007 12:12:48 -0500
To: "Steven Hartland" <killing@multiplay.co.uk>
In-Reply-To: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk>
References: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk>
X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid
X-Primary-Address: mwm@mired.org
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;
	h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
X-Delivery-Agent: TMDA/1.1.5 (Fettercairn)
From: Mike Meyer <mwm-keyword-freebsdhackers2.e313df@mired.org>
Cc: freebsd-hackers@freebsd.org
Subject: Re: NFS based /usr prevents normal startup due to slow net init
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2007 17:11:19 -0000

In <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk>, Steven Hartland <killing@multiplay.co.uk> typed:
> Another observation from my recent dealings with using
> NFS based /usr is that the remote critical mounts via
> nfs dont always give the network enough time to
> initialise before running. The first error displayed
> is:
> Mounting NFS file systems:mount_nfs: nfs1: hostname nor servname provided, or not known
> 
> This is particularly noticeable when the machine is
> connected to Cisco equipment as they take quite a
> while link to the connected host after initialisation.

> The result of this is that other services such as
> ldconfig fail to initialise properly due to the
> mount not being available until some point later
> in the boot process once link has been established.
> 
> Has anyone else experienced this?
> 
> Should mountcritremote use "mount -a -t nfs" when this
> appears to return after a short period without said FS's
> being successfully mounted? Is there a way to ensure that
> mount doesnt return without success i.e. a missing flag
> in my fstab or should mountcritremote be updated to test
> for failure and retry?

How about an extra flag in your fstab?  The default behavior for
mount_nfs is to keep retrying until the mount succeeds. For
non-critical file systems, you can specify -b to cause the mount
attempt to go into the background, and -R to limit the number of
retries. It sounds like you have one of those set.

	<mike
-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.