Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "shahar.salzman@kaminario.com" <shahar.salzman@kaminario.com>
To: kexec@lists.infradead.org, Eran Mann <eran.mann@kaminario.com>,
	open-source-contrib@kaminario.com
Subject: Crash kernel to dump specific pages
Date: Sun, 26 Jan 2014 10:04:40 +0200	[thread overview]
Message-ID: <52E4C198.9010505@kaminario.com> (raw)

Hi all,

We have been using the CentOS kexec (currently 2.0.0) as our recovery 
plan for kernel panic, up to now only dumping the dmesg.
Since we are using a server with a large amount of RAM, we are reluctant 
to perform a full memory dump, both in terms of the time it will take to 
return from the crash kernel, and in terms of disk space reservation.

Recently we where in need of a tweak to kexec so that one of our 
journals will be able to be saved when there is a kernel panic.
I implemented what I call a "raw PFN dump" which receives as input a 
file containing physical frames, and their contiguous length, and will 
dump this "scatter gather" as raw data.

This allows us to perform the following cycle:
1. Setup the journal
2. Get the physical memory mappings (using /proc/<self ot PID>/maps and 
/proc/<self or PID>/pagemap).
3. Format the physical memory mappings to a list of "PFN range" file
4. Add the file to the kdump.conf in the extra_bins
5. restart the kdump service
6. Activate the journal

I have tested this numerous times with CentOS6.4 and kexec-tools2.0.0 
(with makedumpfile 1.3.5).

Would you be interested in this feature for kdump?
If so, over which version should I rebase the patch?

Shahar

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

                 reply	other threads:[~2014-01-26  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E4C198.9010505@kaminario.com \
    --to=shahar.salzman@kaminario.com \
    --cc=eran.mann@kaminario.com \
    --cc=kexec@lists.infradead.org \
    --cc=open-source-contrib@kaminario.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox