Date: Mon, 01 Sep 2003 18:22:34 -0600 From: Scott Long <scottl@freebsd.org> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-current@freebsd.org Subject: Re: swapon vs savecore dilemma Message-ID: <3F53E2CA.9020101@freebsd.org> In-Reply-To: <20030901165035.D58395@carver.gumbysoft.com> References: <20030901165035.D58395@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote: > Hey folks, > > It looks like we may need to rethink the way swap is mounted at boot time > if we want crashdumps to work. > > Recently(?), a change was made so you can no longer open a swap partition > read/write after it is activated with swapon(8). In the current boot > sequence, swap is mounted before the root fsck starts so additional space > is available if the root fsck needs it. But at that point no partitions > are available for writing a core to, so we can't run savecore then. > > Without crashdumps debugging gets kind of interesting. > > Suggestions, other than have separate dump and swap partitions? > I question the wizdom of what you're describing. If swap space needs to be made available for fsck to run, then what happens to the crashdump data that used to be on the swap partition? Doing a swapon(8) means that nothing in the swap partition is reliable or consistent anymore. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F53E2CA.9020101>