I like to catch those (to
> encrypted media) as they can provide insight into the reasons for
> system crash e.g. resolve hardware instability or kernel bug.
>
The system is designed for the developers not the users.
> Dumps are stored to the "dump device", which is the swap pa
into the reasons for
system crash e.g. resolve hardware instability or kernel bug.
Dumps are stored to the "dump device", which is the swap partition on
the system disk - and that has the consequence that dumps never are
stored to swap files, right?
Is there a deliberate thought here that a crash co
[4.8/amd64]
Hello,
Is there a way to change the dump device without rebuilding the kernel?
That's not clear if config(8) -e is able to do this.
Thanks, regards.
space.
Since you are running Root on RAID, how are you managing your swap space?
Do you have a dump device assigned?
: no device
and then during rc I get:
savecore: no core dump
I have tried modifying the config line. If I use:
configbsd root on wd0a swap on wd0b
then I do get an unmirrored partition as my swap_device, and it is also a
dump device.
Does the config syntax support
.
Could you clarify what you mean? I have a raid1b partition markes as
swap, and a wd0b partition marked as swap, and I have not figured out how
to get a dump device assigned, so far, unless I use swap on wd0b -- which
is unmirrored. I have no problem with having an unprotected dump area, but
I am
to get a dump device assigned, so far, unless I use swap on wd0b -- which
is unmirrored. I have no problem with having an unprotected dump area, but
I am concerned about using the partition as swap space.
Right... If you're going to all the trouble of having a system on
RAID, you really want swap
:
config bsd root on wd0a swap on wd0b
then I do get an unmirrored partition as my swap_device, and it is also a
dump device. But ... adding /dev/raid1b doesn't work -- adding this device
to /etc/fstab seems to be ignored, and swapctl -a /dev/raid1b fails with
file not found. raid1b
8 matches
Mail list logo
