From owner-freebsd-rc@FreeBSD.ORG Wed Feb 15 11:57:57 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D460216A420; Wed, 15 Feb 2006 11:57:57 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64A0343D45; Wed, 15 Feb 2006 11:57:49 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k1FBv6sY097562; Wed, 15 Feb 2006 14:57:06 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k1FBv6uk097561; Wed, 15 Feb 2006 14:57:06 +0300 (MSK) (envelope-from yar) Date: Wed, 15 Feb 2006 14:57:05 +0300 From: Yar Tikhiy To: Doug Barton Message-ID: <20060215115705.GL85260@comp.chem.msu.su> References: <200602131930.k1DJU8gA008815@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602131930.k1DJU8gA008815@freefall.freebsd.org> User-Agent: Mutt/1.5.9i Cc: nge@cs.hmc.edu, freebsd-rc@freebsd.org Subject: Re: conf/73834: Bad dependencies for /etc/rc.d/savecore X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2006 11:57:58 -0000 On Mon, Feb 13, 2006 at 07:30:08PM +0000, Doug Barton wrote: > > First, it turns out that you can actually recover a dump > even after the partition has been swapon'ed. Second, the > problem you describe here has been discussed at great > length on the freebsd-current mailing list. The short > version is that there is a chicken and egg problem. In > order to capture the dump, you need a file system to write > to. In order to get a file system to write to, you need > fsck. In order to allow fsck to run on a memory constrained > system, you may need swap. Thus, the current thinking is > that the status quo is the best of our current options. IMHO it's worth to note in addition that one can always arrange a separate dump-only partition if dumps to swap get overwritten due to heavy paging activity during early boot stages, such as fsck of a large file system in small RAM. -- Yar