LinuxKernelCrashDumpSpec
1172
Comment:
|
1222
|
Deletions are marked like this. | Additions are marked like this. |
Line 24: | Line 24: |
== See also == http://mkdump.sourceforge.net/ |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/linux-kernel-crash-dump/
Created: 2006-05-09 by SimonLaw
Contributors: SimonLaw
Packages affected: linux-source-2.6.xx
Summary
Rationale
Use cases
Scope
Design
Implementation
Code
Data preservation and migration
Outstanding issues
See also
http://mkdump.sourceforge.net/
BoF agenda and discussion
ScottJamesRemnant: if there's no obvious and easy way, one hacky way occurs -- write it to the top of the swap disk with a simple to detect header and then pick it up on reboot and put it on the real filesystem -- I suspect there's far simpler ways though
SorenHansen: That's not quite safe, though. There's no way to know if the particular crash has messed up the kernel's perception of where the swap space starts. If it has, the dump could potentially overwrite actual data. If this could be done via a SysRq magic combo, the user could make an informed decision as to whether this is likely (based on stack dumps and whatnot) and based on that decide if he/she wants to write the dump.
LinuxKernelCrashDumpSpec (last edited 2009-07-14 13:29:18 by p54A64F3F)