From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 9 08:12:00 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 A29F416A402 for ; Fri, 9 Mar 2007 08:12:00 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp805.mail.ird.yahoo.com (smtp805.mail.ird.yahoo.com [217.146.188.65]) by mx1.freebsd.org (Postfix) with SMTP id 18CA313C467 for ; Fri, 9 Mar 2007 08:11:59 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: (qmail 89256 invoked from network); 9 Mar 2007 07:45:18 -0000 Received: from unknown (HELO ?192.168.1.2?) (thomasjudge@btinternet.com@81.157.42.3 with plain) by smtp805.mail.ird.yahoo.com with SMTP; 9 Mar 2007 07:45:18 -0000 X-YMail-OSG: DJJJFPUVM1n9oerGVNsBtZBTBn9SUQUz_h9Czz82x21Z40fnaBG_sBGtc44GOXtY1QEfGIInGrXc65j4iiuEpb_n.Hh79VFU0E33oAaBfOixA.npFj6yx_wFwr_HKg-- Message-ID: <45F1110C.1070709@tomjudge.com> Date: Fri, 09 Mar 2007 07:47:24 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: Steven Hartland References: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk> In-Reply-To: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2007 08:12:00 -0000 Steven Hartland wrote: > 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? > > This was bought up some time ago on the current > list but no answers where forth coming: > http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058935.html > > > Test details: > Network card: bge0 > Switch: Cisco 6509 > Switch Blade: WS-X6748-GE-TX > fstab line: nfs1:/fs/usr /usr nfs rw 0 0 > On our systems I have modified /etc/rc.d/mountcritremote to have a 15 second sleep at the beginning to allow for slow port setup time. Its not really a nice fix but it does the job. Tom