From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 8 04:34:17 2007 Return-Path: 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 143E216A405 for ; Thu, 8 Mar 2007 04:34:17 +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 9537E13C4AA for ; Thu, 8 Mar 2007 04:34:16 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 27111 invoked by uid 1001); 8 Mar 2007 04:35:55 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 07 Mar 2007 23:35:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <17903.37547.207909.316479@bhuda.mired.org> Date: Wed, 7 Mar 2007 23:35:55 -0500 To: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) In-Reply-To: <86lki8u1al.fsf@dwp.des.no> References: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk> <17896.23312.980989.68558@bhuda.mired.org> <86lki8u1al.fsf@dwp.des.no> 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 Cc: freebsd-hackers@freebsd.org, Steven Hartland 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2007 04:34:17 -0000 In <86lki8u1al.fsf@dwp.des.no>, Dag-Erling Sm=F8rgrav type= d: > Mike Meyer writes: > > Steven Hartland writes: > > > 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 > > > [...] > > How about an extra flag in your fstab? The default behavior for > > mount_nfs is to keep retrying until the mount succeeds. >=20 > No, it will fail immediately (as seen above) if it can't resolve the > server name. The only way to fix this is to modify mount_nfs to slee= p > and retry in such cases. The *current* sleep-and-retry code is in th= e > NFS mount code in the kernel, which doesn't come into play until afte= r > DNS lookup. In that case, there's a bug in the mount_nfs man page, which just says that it keeps retrying until it succeeds. PR #110062 =09=09=09http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more informatio= n.