From: Vivek Goyal <vgoyal@redhat.com>
To: "HATAYAMA, Daisuke" <d.hatayama@jp.fujitsu.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
"bhe@redhat.com" <bhe@redhat.com>
Subject: Re: [PATCH] Makedumpfile: vmcore size estimate
Date: Fri, 11 Jul 2014 09:51:55 -0400 [thread overview]
Message-ID: <20140711135155.GE15611@redhat.com> (raw)
In-Reply-To: <53B6091F.4010707@jp.fujitsu.com>
On Fri, Jul 04, 2014 at 10:53:35AM +0900, HATAYAMA, Daisuke wrote:
[..]
> For fail safe, it should address ENOSPC case more. Sadly, preparing too small disks for vmcores is human error. In general, we cannot avoid this in real world. It's important to make vmcore valid even in case of ENOSPC in the sense that at least generated part of vmcore can correctly be analized by crash.
I agree. Dealing with ENOSPC makes sense. Save as much as possible and
display a warning message that dump got truncated. Still dump file should
be readable by "crash". That way we will not lose the whole dump and
whatever has been saved, might be sufficient to analyze the dump.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-07-11 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 12:39 [PATCH] Makedumpfile: vmcore size estimate Baoquan He
2014-06-11 13:57 ` Baoquan He
2014-06-20 1:07 ` Atsushi Kumagai
2014-06-20 1:58 ` bhe
2014-06-20 2:33 ` bhe
2014-06-23 12:57 ` Vivek Goyal
2014-06-26 8:21 ` Atsushi Kumagai
2014-06-26 12:31 ` Vivek Goyal
2014-07-02 0:25 ` Atsushi Kumagai
2014-07-02 8:13 ` bhe
2014-07-04 1:53 ` HATAYAMA, Daisuke
2014-07-04 9:44 ` bhe
2014-07-11 13:51 ` Vivek Goyal [this message]
2014-06-23 12:36 ` Vivek Goyal
2014-06-23 13:05 ` Baoquan He
2014-06-23 13:55 ` Anders Rayner-Karlsson
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=20140711135155.GE15611@redhat.com \
--to=vgoyal@redhat.com \
--cc=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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