From owner-freebsd-bugs@FreeBSD.ORG  Sun Jul 11 08:18:12 2010
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28100106566C;
	Sun, 11 Jul 2010 08:18:12 +0000 (UTC)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 18F438FC16;
	Sun, 11 Jul 2010 08:18:12 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6B8IBUj076979;
	Sun, 11 Jul 2010 08:18:11 GMT
	(envelope-from remko@freefall.freebsd.org)
Received: (from remko@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6B8IBUt076975;
	Sun, 11 Jul 2010 08:18:11 GMT (envelope-from remko)
Date: Sun, 11 Jul 2010 08:18:11 GMT
Message-Id: <201007110818.o6B8IBUt076975@freefall.freebsd.org>
To: reed@koansys.com, remko@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: remko@FreeBSD.org
Cc: 
Subject: Re: misc/148493: 8.0-RELEASE #0 won't boot if it can't mount smbfs
	entries in fstab
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 08:18:12 -0000

Synopsis: 8.0-RELEASE #0 won't boot if it can't mount smbfs entries in fstab

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