From owner-freebsd-current@FreeBSD.ORG  Fri Sep 30 20:04:16 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D2D6316A41F
	for <freebsd-current@freebsd.org>; Fri, 30 Sep 2005 20:04:16 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 378AF43D5A
	for <freebsd-current@freebsd.org>; Fri, 30 Sep 2005 20:04:16 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with ESMTP id 424B346BE0;
	Fri, 30 Sep 2005 16:04:15 -0400 (EDT)
Date: Fri, 30 Sep 2005 21:04:15 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20050930190403.GA93829@xor.obsecurity.org>
Message-ID: <20050930210228.D71864@fledge.watson.org>
References: <433D8B12.9020801@informatica.info>
	<20050930190403.GA93829@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-current@freebsd.org, Listas <listas@informatica.info>
Subject: Re: Losing ssh session when doing intensive disk I/O & background
 fsck with RELENG_6
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2005 20:04:16 -0000


On Fri, 30 Sep 2005, Kris Kennaway wrote:

>> The boot process is trying to configure the dump device before swapon 
>> and it fails, but that's not the real problem I report here.
>
> It's not clear that it's a problem at all.  dump devices don't have to 
> be pre-existing swap devices.  If you tell your kernel to dump on 
> /dev/ar0s1b it should be fine.

At some point someone changed the default setting to "automatically 
configure dumping" which resulted in odd warnings during the boot.  I've 
trimmed a few, and hope to trim the last few.  Autoconfiguration of dumps 
is neat and all, but lots of odd warnings for users isn't really.  It 
would be interesting to know if it works though -- the warnings suggest 
that dumps aren't found because the dump device isn't autoconfigured until 
after dumps are checked for...

Robert N M Watson