From: "Christopher S. Aker" <caker@theshore.net>
To: linux-kernel@vger.kernel.org
Subject: [Feature Request?] Inline compression of process core dumps
Date: Thu, 12 Apr 2007 11:52:38 -0400 [thread overview]
Message-ID: <461E55C6.1030905@theshore.net> (raw)
I've been trying to find a method for compressing process core dumps
before they hit disk.
I ask because we've got some fairly large UML processes (1GB for some),
and we're trying to capture dumps to help Jeff debug an evasive bug.
Our systems use a small root partition and most of the other disk
resources on the host are allocated towards the UMLs.
There are userspace solutions to this problem: allowing the
uncompressed core dump to spin out to disk and then coming in afterwards
and doing the compression, or maybe even a compressed filesystem where
the core dumps land, but I just thought I'd throw this out there since
it seems it would be a useful feature :)
Thanks,
-Chris
next reply other threads:[~2007-04-12 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 15:52 Christopher S. Aker [this message]
2007-04-12 16:09 ` [Feature Request?] Inline compression of process core dumps Bill Rugolsky Jr.
2007-04-12 16:18 ` Guillaume Chazarain
2007-04-12 16:28 ` Alan Cox
2007-04-12 16:42 ` Bill Rugolsky Jr.
2007-04-12 17:45 ` Andi Kleen
2007-04-13 2:22 ` Christopher S. Aker
2007-04-13 2:38 ` Randy Dunlap
2007-04-13 2:57 ` Christopher S. Aker
2007-04-13 4:21 ` Jeff Dike
2007-04-13 10:55 ` Alan Cox
2007-04-13 12:23 ` Andi Kleen
2007-04-13 14:59 ` Randy Dunlap
2007-04-13 15:43 ` Andi Kleen
2007-04-13 16:17 ` Alan Cox
2007-04-13 19:42 ` Andi Kleen
2007-04-13 12:39 ` Alan Cox
2007-04-13 13:38 ` Christopher S. Aker
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=461E55C6.1030905@theshore.net \
--to=caker@theshore.net \
--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