From owner-freebsd-questions@FreeBSD.ORG Tue Apr 6 15:44:39 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 58BA01065675 for ; Tue, 6 Apr 2010 15:44:39 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 182558FC1D for ; Tue, 6 Apr 2010 15:44:38 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o36FiX3G005223 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 6 Apr 2010 10:44:33 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4BBB56E2.10801@tundraware.com> Date: Tue, 06 Apr 2010 10:44:34 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Mailing List X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (ozzie.tundraware.com [75.145.138.73]); Tue, 06 Apr 2010 10:44:33 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o36FiX3G005223 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: 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 15:44:39 -0000 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? -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/