From nobody@FreeBSD.org  Sun Jul 11 07:45:06 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 48CBC106566C
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 11 Jul 2010 07:45:06 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 377348FC13
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 11 Jul 2010 07:45:06 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o6B7j5Vj057449
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 11 Jul 2010 07:45:05 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o6B7j56h057448;
	Sun, 11 Jul 2010 07:45:05 GMT
	(envelope-from nobody)
Message-Id: <201007110745.o6B7j56h057448@www.freebsd.org>
Date: Sun, 11 Jul 2010 07:45:05 GMT
From: "Reed L O'Brien" <reed@koansys.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 8.0-RELEASE #0 won't boot if it can't mount smbfs entries in fstab
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         148493
>Category:       misc
>Synopsis:       8.0-RELEASE #0 won't boot if it can't mount smbfs entries in fstab
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 11 07:50:02 UTC 2010
>Closed-Date:    Sun Jul 11 08:18:12 UTC 2010
>Last-Modified:  Sun Jul 11 08:18:12 UTC 2010
>Originator:     Reed L O'Brien
>Release:        8.0-RELEASE #0
>Organization:
Koansys, LLC
>Environment:
FreeBSD babahoya.retroconference.org 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009     root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386


>Description:
Machine went down due to a very extended power outage.

It was running fine, but after reboot it wouldn't come up at all. It dropped back to single user mode.

The actual cause was a firewall rule blocking wins resolution when trying to mount /etc/fstab during init.

I don't know if this qualifies as a bug, but it seems rather silly that the system can't boot after mounting all the local filesystems. I understand that if init exits nonzero from mount it can't tell if it was / or an smbfs mount that failed. So, maybe the non-essential mount points should go in a /usr/local/fstab or something.

I wanted to report it though as I am sure someone else has been or will be bitten by this. it was especially painful as the machine runs headless...Your call. If you need me to follow up on anything let me know.
>How-To-Repeat:
mount a win2kx server share in /etc/fstab and then enable pf without creating a rule to allow smb/cifs traffic. Wait until there is a 6 hours power outage. The machine functions fine until it reboots. Then init exits non zero from trying to mount the entries in fstab.

Logged error:
Jul  8 14:48:53 babahoya kernel: netsmb_dev: loaded
Jul  8 14:49:22 babahoya init: /bin/sh on /etc/rc terminated abnormally, going to single user mode

Console error was something close to:
smbfs: can't get server address: syserr = Operation timed out
>Fix:
Easy enough just add the correct rules to allow smb/cifs traffic in the firewall; pf in this case.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Sun Jul 11 08:18:11 UTC 2010 
State-Changed-Why:  
Well this is not a situation that we can easily fix. If you as the owner 
/ administrator of the system tell it to mount a remote file system, you 
have obvious reasons for it. FreeBSD will try its best to mount the 
disk, but since a firewall, or network or remote host can be down and we 
cannot tell from the mount command itself, it retries a few times, 
aborting mounting because the system does not want to start the system 
without the by your issued mountlist. The disk could be vital to the 
success of the startup and usage. So sadly, this is the reality and we 
should live with it. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=148493 
>Unformatted:
