Date: Wed, 15 Feb 2006 14:57:05 +0300 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Doug Barton <dougb@freebsd.org> Cc: nge@cs.hmc.edu, freebsd-rc@freebsd.org Subject: Re: conf/73834: Bad dependencies for /etc/rc.d/savecore Message-ID: <20060215115705.GL85260@comp.chem.msu.su> In-Reply-To: <200602131930.k1DJU8gA008815@freefall.freebsd.org> References: <200602131930.k1DJU8gA008815@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060215115705.GL85260>