Date: Thu, 14 Feb 2008 11:01:26 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Scott Long <scottl@samsco.org> Cc: Ian FREISLICH <ianf@clue.co.za>, Ken Smith <kensmith@cse.Buffalo.EDU>, freebsd-current@freebsd.org Subject: Re: FreeBSD 7.0-RC2 Available Message-ID: <47B41176.9070405@FreeBSD.org> In-Reply-To: <47B3BA6B.7080106@samsco.org> References: <E1JPCWL-0000pN-IF@clue.co.za> <47B38809.5000500@FreeBSD.org> <47B3BA6B.7080106@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47B41176.9070405>