From owner-freebsd-questions@FreeBSD.ORG Tue Apr 6 16:06:33 2010 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 03AA2106564A for ; Tue, 6 Apr 2010 16:06:33 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by mx1.freebsd.org (Postfix) with ESMTP id C8A6C8FC14 for ; Tue, 6 Apr 2010 16:06:32 +0000 (UTC) Received: by pzk35 with SMTP id 35so39929pzk.3 for ; Tue, 06 Apr 2010 09:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=wCnPqnEnMxYPcYYaCu6mpXkOQk1/mZWbyrI8m0goiyc=; b=xyzLtoRUC0rotdKTmweJkOZ67uB+LQKH33cnNApr2bauJ83u+KBl1xGavHLEgyeb2B bIpLk4I2CVfqK8VHGMZSUsTyeNvnrTFHNlgSf+4KJ+nppzSRz+37fnMvprOhziXpwf5M du+jAjnJzEKgrAmecoe/aksnvYEFNLHHSpDRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=I7Wb0UgICnZa6a8xNlrHxa18l5Pol5UY9mM55w7jaWUmprsEORVfTh6QRknqVzG2Lm /xvFS7qryfsMVV1repgp9AGIBrz3g/mjwk7LN5EAPxV+7lv2KucHB5tF7f/7R0L54Ynf BjhGUsjpsj41BGCSYt6AH4MyBWX7cBkLI9AAg= Received: by 10.143.20.13 with SMTP id x13mr2608269wfi.285.1270569992037; Tue, 06 Apr 2010 09:06:32 -0700 (PDT) Received: from orion.hsd1.pa.comcast.net (c-71-230-240-241.hsd1.pa.comcast.net [71.230.240.241]) by mx.google.com with ESMTPS id e40sm9399wfj.11.2010.04.06.09.06.29 (version=SSLv3 cipher=RC4-MD5); Tue, 06 Apr 2010 09:06:30 -0700 (PDT) Date: Tue, 6 Apr 2010 12:03:02 -0400 From: Glen Barber To: Tim Daneliuk Message-ID: <20100406160301.GA37004@orion.hsd1.pa.comcast.net> References: <4BBB56E2.10801@tundraware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BBB56E2.10801@tundraware.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Mailing List Subject: Re: Preventing Bad SMB Mount From Stalling A Boot 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: Tue, 06 Apr 2010 16:06:33 -0000 Hi Tim, Tim Daneliuk wrote: > I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine like > this: > > //USER@WINSERVER/SHARE /mountpoint smbfs rw 0 0 > > The problem is that after an outage, "WINSERVER" doesn't come up > before the FBSD machine. So, the FBSD machine tries to boot and then > hangs permanently because it cannot get the SMB share points mounted. > This recently happened after a catastrophic power outage that cooked > the share info on "WINSERVER". Even after it came up, it was no longer > serving the proper shares and the FBSD machine could never find the > SMB shares and thus hung permanently. > > The SMB mounts are not essential for systems operations. Is there a > way to tell the FBSD to try and mount SMB, but keep going and complete > the boot if it cannot? > I have a similar problem with a D-Link NAS I use for rsnapshot, however my NAS does not come up after a power outage _period_. The solution I use is to 'noauto' the nfs mount to prevent the stall until I can boot the NAS. I then created /mountpoint/NO, which the existence of the 'NO' file is checked before rsnapshot via cron telling rsnapshot if it is okay to backup to the mountpoint. The result is that my machine will continue to boot after a power failure, and the filesystem will not get clobbered by recursive backups. Though this isn't the same situation you are experiencing, you could always script the mount to occur "@reboot" via cron. Of course, there is always rcorder(8), but I have not looked at it too much, as it would not help in my situation. HTH and regards, -- Glen Barber