Subject: misc/30427: guide raidframe chapter has lost dump information
To: None <email@example.com, firstname.lastname@example.org,>
From: None <email@example.com>
Date: 06/04/2005 19:39:00
>Synopsis: guide raidframe chapter has lost dump information
>Arrival-Date: Sat Jun 04 19:39:00 +0000 2005
>Originator: Tracy Di Marco White
>Release: NetBSD 2.0
any web browser
<title>Setting up kernel dumps</title>
The normal swap area in our case is on raid0b but this can not be used
for crash dumps as process scheduling is stopped when dumps happen.
Therefore we must use a real disk device. However, nothing stops us from
defining a dump area which overlaps with raid0b. The trick here is to
calculate the correct start offset for our crash dump area. This is
dangerous and it is possible to destroy valuable data if we make a mistake
in these calculations! Data corruption will happen when the kernel
write its memory dump over a normal filesystem. So we must be extra
(The author destroyed his 100+ GB /home with a kernel crash dump!)
<para>First we need to take a look at the disklabel for swap (raid0b)
and the real physical disk (wd1).</para>
and more. It's gone now. It shouldn't be.
note that "setting up kernel dumps" is still gone.
Put that information back. Or else explain how it's no longer needed.