LinuxKernelCrashDumpSpec

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2006-06-11 21:31:44 →
Size: 732
Editor: syndicate
Comment: swap idea
← Revision 3 as of 2006-06-11 22:04:20 → ⇥
Size: 1172
Editor: granit-ext
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:

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.

Summary

Rationale

Use cases

Scope

Design

Implementation

Code

Data preservation and migration

Outstanding issues

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.

CategorySpec

LinuxKernelCrashDumpSpec (last edited 2009-07-14 13:29:18 by p54A64F3F)