mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: joe shmoe <joeshmoeypeter@yahoo.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	daniel.kiper@oracle.com
Subject: Re: kdump/kexec vmcore size doubles each time
Date: Mon, 23 Jul 2012 16:48:19 -0700 (PDT)	[thread overview]
Message-ID: <1343087299.65126.YahooMailNeo@web160606.mail.bf1.yahoo.com> (raw)
In-Reply-To: <20120720093648.GA3909@router-fw-old.local.net-space.pl>

Hi,
Thank you for the reply. I ended up opting for writing to filesystem rather than raw_device and this seems to have helped me sidestep the problem for now. Unfortunately, I can't quite make a jump to later sources.

I do have another question, I see KDUMP_KEEP_OLD_DUMPS mentioned to automatically clean up prior dumps (for ex: http://dedoimedo.com/computers/kdump.html and other SUSE docs).
However, I cannot find any logic in sources to do this (and sure enough I don't see older cores in my /var/crash/ path clean up as new cores are dumped).

Could someone please comment if:
(i) KDUMP_KEEP_OLD_DUMPS is unsupported or not. If it IS supported, could someone please help with the relevant source code so I could debug why it isn't working? Yes, I did download kexec-tools git but cannot find anything relevant.

(ii) If there is NO explicit source code to achieve this -- then do folks achieve such a cleanup through KDUMP_PRE and KDUMP_POST scripts? If yes, is there a standard-ish script out there to achieve this?

Thanks much.

----- Original Message -----
From: Daniel Kiper <dkiper@net-space.pl>
To: joe shmoe <joeshmoeypeter@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>; daniel.kiper@oracle.com
Sent: Friday, July 20, 2012 2:36 AM
Subject: Re: kdump/kexec vmcore size doubles each time

On Thu, Jul 19, 2012 at 03:08:44PM -0700, joe shmoe wrote:
> Hi,
> I am trying to configure kexec/kdump on 2.6.35-14.
>
>
> $> kexec --version
> kexec-tools-testing 20080330 released 30th March 2007

[...]

It is very ancient version. Please use at least Ver. 2.0.3
(http://kernel.org/pub/linux/utils/kernel/kexec/) or current
development version (git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git).

Daniel


  reply	other threads:[~2012-07-23 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 22:08 joe shmoe
2012-07-20  9:36 ` Daniel Kiper
2012-07-23 23:48   ` joe shmoe [this message]
2012-07-24 14:06     ` Daniel Kiper

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=1343087299.65126.YahooMailNeo@web160606.mail.bf1.yahoo.com \
    --to=joeshmoeypeter@yahoo.com \
    --cc=daniel.kiper@oracle.com \
    --cc=dkiper@net-space.pl \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®