From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Cc: "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: [REQUEST] makedumpfile: stream compress flat ELF format with libz
Date: Tue, 12 May 2020 17:25:46 +0000 [thread overview]
Message-ID: <20200512172546.GL31850@zorba> (raw)
Hi,
I created an enhancement request for makedumpfile here,
https://github.com/makedumpfile/makedumpfile/issues/1
I found that compressing a flat core with gzip significantly reduces the size of
the core. Here were my findings,
32G flat elf core -E -F -d 0
33G kdump core -d 0
16G kdump compressed -c -d 0
1.9G flat elf core stream compressed with gzip -E -F -d 0
My feature request was to implement an option inside makedumpfile to gzip
compress the core output. This can already be accomplished by piping the core
thru the gzip tool, however, because makedumpfile already links against libz
having the option for makedumpfile to do it allows the gzip tools to be removed
from the crash kernels initramfs there by reducing the size.
Kazuhito Hagio had suggest adding the -C option instead of repurposing -c to do
this.
So a resulting command line might looks like this,
makedumpfile -C -F -E -d 31 /proc/vmcore core.gz
Thanks,
Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2020-05-12 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:25 Daniel Walker (danielwa) [this message]
2020-05-12 17:38 ` [REQUEST] makedumpfile: stream compress flat ELF format with libz John Donnelly
2020-05-12 17:45 ` Daniel Walker (danielwa)
2020-05-12 18:14 ` Guilherme Piccoli
2020-05-12 18:27 ` Daniel Walker (danielwa)
2020-05-12 18:32 ` Guilherme Piccoli
2020-05-12 18:56 ` Daniel Walker (danielwa)
2020-05-12 19:20 ` HAGIO KAZUHITO(萩尾 一仁)
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=20200512172546.GL31850@zorba \
--to=danielwa@cisco.com \
--cc=kexec@lists.infradead.org \
--cc=xe-linux-external@cisco.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