From owner-freebsd-current@FreeBSD.ORG  Thu Feb 14 10:01:28 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AACF316A41A
	for <freebsd-current@freebsd.org>; Thu, 14 Feb 2008 10:01:28 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 865CB13C455;
	Thu, 14 Feb 2008 10:01:27 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47B41176.9070405@FreeBSD.org>
Date: Thu, 14 Feb 2008 11:01:26 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Scott Long <scottl@samsco.org>
References: <E1JPCWL-0000pN-IF@clue.co.za> <47B38809.5000500@FreeBSD.org>
	<47B3BA6B.7080106@samsco.org>
In-Reply-To: <47B3BA6B.7080106@samsco.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ian FREISLICH <ianf@clue.co.za>, Ken Smith <kensmith@cse.Buffalo.EDU>,
	freebsd-current@freebsd.org
Subject: Re: FreeBSD 7.0-RC2 Available
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: Thu, 14 Feb 2008 10:01:28 -0000

Scott Long wrote:
> Kris Kennaway wrote:
>> Ian FREISLICH wrote:
>>> Hi
>>>
>>> I just installed and only now noticed this oddity (to me at least).
>>> Maybe it's been explained before, but I can't quite remember.
>>>
>>> I selected auto defaults for the slice editor.  The system I installed
>>> (amd64) on has 16GB of RAM yet it only assigned 4GB for swap.  I
>>> remember reading that on amd64 minidumps could corrupt neighbouring
>>> filesystems, so a full dump could be up to 16GB.  There won't be
>>> enough space for a full dump.  That said, 16GB is quite a *lot* to
>>> swap out and I'm not sure how the system would perform under that
>>> scenario.
>>
>> I havent seen reports of problems with minidump on amd64.  I use it 
>> myself.
> 
> Until fairly recently, there were no seatbelts to prevent the dumpsys
> code from exceeding the dump partition.  It was discussed in several
> forums, and the fix was developed and committed to HEAD and 7-mumble
> by Ruslan a couple of weeks ago.  It was not a problem specific to any
> particular platform.

OK, so problem solved then.

Kris