From owner-freebsd-hackers@FreeBSD.ORG Fri May 19 00:48:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDD3F16A433 for ; Fri, 19 May 2006 00:48: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 C8F7343D48 for ; Fri, 19 May 2006 00:48:11 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 46849 invoked by uid 1001); 19 May 2006 00:48:10 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 18 May 2006 20:48:10 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17517.5578.499715.568791@bhuda.mired.org> Date: Thu, 18 May 2006 20:48:10 -0400 To: "Steven Hartland" In-Reply-To: <008c01c67adc$590a2a30$b3db87d4@multiplay.co.uk> References: <008c01c67adc$590a2a30$b3db87d4@multiplay.co.uk> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" 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.0.3 (Seattle Slew) From: Mike Meyer X-Mailman-Approved-At: Fri, 19 May 2006 02:34:00 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: NFS server not responding prevents boot 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, 19 May 2006 00:48:20 -0000 In <008c01c67adc$590a2a30$b3db87d4@multiplay.co.uk>, Steven Hartland typed: > I was doing some kernel patches the other day and rebooted > a FreeBSD 5.4 machine to pick them up, unfortunately I didn't > notice someone had put in a bad nfs mount in /etc/fstab > i.e. to a machine that no longer existed. > > This prevented the server coming back onto the network > enough to fix the error ( sshd never started ). With the > machine being remote I ended up having to send an engineer > in to press CTRL + C on the keyboard to enable the machine > to boot ( didn't know it would be that simple before he got > there ). > > Anyway the big question is how can I change all our NFS > mounts so that failed mounts dont prevent the machines > booting to the point where they can be fixed remotely > i.e. have started sshd. Add -b to the options column for nfs-mounted volumes. That will cause the mount attempt to be done in the background if the first attempt fails. Of course you should beware of nfs volumes that are required for a system to boot properly. You have to decide whether "hung waiting for the remote file system" is better or worse than the state you get if the system boots without that file system mounted. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.