Date: Tue, 02 Sep 2003 04:16:40 +0200 From: Pawel Worach <pawel.worach@telia.com> To: Scott Long <scottl@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: swapon vs savecore dilemma Message-ID: <3F53FD88.1050005@telia.com> In-Reply-To: <3F53E2CA.9020101@freebsd.org> References: <20030901165035.D58395@carver.gumbysoft.com> <3F53E2CA.9020101@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote:
> 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.
>>
>
> 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
>
Yes, I have seen this too.
Sep 2 02:16:30 darkstar savecore: /dev/da0s1b: Operation not permitted
Sep 2 02:16:30 darkstar savecore: no dumps found
Is fsck really that memory heavy so that it needs swap?
Wouldn't fsck -> mount -> savecore -> swapon be a more appropriate order?
- Pawel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F53FD88.1050005>