From owner-freebsd-current@FreeBSD.ORG Thu Feb 14 03:50:13 2008 Return-Path: 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 9D06816A418 for ; Thu, 14 Feb 2008 03:50:13 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 45C8813C4CE for ; Thu, 14 Feb 2008 03:50:12 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1E3o3Y2067945; Wed, 13 Feb 2008 20:50:03 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47B3BA6B.7080106@samsco.org> Date: Wed, 13 Feb 2008 20:50:03 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Kris Kennaway References: <47B38809.5000500@FreeBSD.org> In-Reply-To: <47B38809.5000500@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Ian FREISLICH , Ken Smith , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2008 03:50:13 -0000 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. Scott