From owner-freebsd-stable@FreeBSD.ORG Fri Nov 18 23:13:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46FE816A41F; Fri, 18 Nov 2005 23:13:39 +0000 (GMT) (envelope-from parv@pair.com) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF17F43D46; Fri, 18 Nov 2005 23:13:38 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([68.67.248.52]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051118231337.LLQS15290.mta11.adelphia.net@default.chvlva.adelphia.net>; Fri, 18 Nov 2005 18:13:37 -0500 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id BC7C1B509; Fri, 18 Nov 2005 18:13:51 -0500 (EST) Date: Fri, 18 Nov 2005 18:13:51 -0500 From: Parv To: Michal Mertl Message-ID: <20051118231351.GA46946@holestein.holy.cow> Mail-Followup-To: Michal Mertl , Johan =?iso-8859-1?Q?Str=F6m?= , pjd@freebsd.org, delphij@delphij.net, freebsd-stable@freebsd.org References: <991F35AA-151B-4AEA-82BD-5F4AEDF28424@stromnet.org> <74994962-5050-47BD-897B-DE3880B9EBD5@stromnet.org> <1132353600.903.19.camel@genius1.i.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1132353600.903.19.camel@genius1.i.cz> Cc: delphij@delphij.net, Johan =?iso-8859-1?Q?Str=F6m?= , pjd@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Page fault, GEOM problem?? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 23:13:39 -0000 in message <1132353600.903.19.camel@genius1.i.cz>, wrote Michal Mertl thusly... > > Johan Ström wrote: > > > > On 18 nov 2005, at 18.43, Xin LI wrote: ... > > So, it seems it does run savecore after running dumpon and > > mounting disks etc... Is that wrong? > > No, this is normal. When you run savecore you need to have mounted > filesystems. In order to mount the filesystems they may have to be > checked. The fsck program requires big amount of memory to check > larger filesystems so the swap has to be enabled. Core dumps are > written to the dump device (swap) from the end whereas the swap is > normally used from the beginning (or the other way around). > Therefore there's quite a big chance that, even when the swap has > to be used for fsck, the core dump is intact and usable. Is there any formula to calculate the size of swap to account for fsck & core dump while assigning swap size (short of having two swap partitions)? > If the usage of the swap file by fsck corrupts the core dump you > may start after next crash in single user mode and run the > commands manually (without enabling swap). Is that after kernel (re)boots? And would the commands to be executed be savecore followed by swapon? - Parv --