From: tachibana@mxm.nes.nec.co.jp
To: Don Zickus <dzickus@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: makedumpfile memory usage grows with system memory size
Date: Mon, 2 Apr 2012 15:53:53 +0900 [thread overview]
Message-ID: <20120402155353tachibana@mail.jp.nec.com> (raw)
Hi Don,
On 2012/03/30 09:19:16 -0400, Don Zickus <dzickus@redhat.com> wrote:
> On Fri, Mar 30, 2012 at 06:43:34PM +0900, Atsushi Kumagai wrote:
> > Hello Don,
> > Does setting TMPDIR solve your problem ? Please refer to the man page.
> >
> >
> > ENVIRONMENT VARIABLES
> > TMPDIR This environment variable is for a temporary memory bitmap
> > file. If your machine has a lots of memory and you use tmpfs
> > on /tmp, makedumpfile can fail for a little memory in the 2nd
> > kernel because makedumpfile makes a very large temporary memory
> > bitmap file in this case. To avoid this failure, you can set a
> > TMPDIR environment variable. If you do not set a TMPDIR envi-
> > ronment variable, makedumpfile uses /tmp directory for a tempo-
> > rary bitmap file as a default.
>
> I do not think it will because we run the second kernel inside the
> initramfs and do not mount any extra disks. So the only location available
> for the temporary memory bitmap would be memory either tmpfs or something
> else. Regardless the file ends up in memory.
If a file system for a dump file is on the local system, it is effective that
we specify a directory as TMPDIR in the same file system, isn't it?
Thanks
tachibana
>
> >
> >
> > On the other hand, I'm considering the enhancement suggested by Hatayama-san now.
>
> His idea looks interesting if it works. Thanks.
>
> Cheers,
> Don
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-04-02 6:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 6:53 tachibana [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-28 21:22 makedumpfile memory usage grows with system memory size Don Zickus
2012-03-29 8:09 ` Ken'ichi Ohmichi
2012-03-29 12:56 ` HATAYAMA Daisuke
2012-03-29 13:25 ` Don Zickus
2012-03-30 0:51 ` HATAYAMA Daisuke
2012-04-02 7:46 ` Atsushi Kumagai
2012-04-05 6:52 ` HATAYAMA Daisuke
2012-04-05 14:34 ` Vivek Goyal
2012-04-06 1:12 ` HATAYAMA Daisuke
2012-04-06 8:59 ` Atsushi Kumagai
2012-04-06 9:29 ` HATAYAMA Daisuke
2012-04-09 18:57 ` Vivek Goyal
2012-04-09 23:58 ` HATAYAMA Daisuke
2012-04-10 12:52 ` Vivek Goyal
2012-04-12 3:40 ` Atsushi Kumagai
2012-04-12 7:47 ` HATAYAMA Daisuke
[not found] ` <20120427164649.9932a33f.kumagai-atsushi@mxc.nes.nec.co.jp>
2012-04-27 12:52 ` Don Zickus
2012-05-11 1:19 ` Atsushi Kumagai
2012-05-11 13:26 ` Don Zickus
2012-05-15 5:57 ` Atsushi Kumagai
2012-05-15 12:35 ` Don Zickus
2012-04-27 13:33 ` Vivek Goyal
2012-05-14 5:44 ` HATAYAMA Daisuke
2012-05-16 8:02 ` Atsushi Kumagai
2012-05-17 0:21 ` HATAYAMA Daisuke
2012-04-09 19:00 ` Vivek Goyal
2012-03-29 13:05 ` Don Zickus
2012-03-30 9:43 ` Atsushi Kumagai
2012-03-30 13:19 ` Don Zickus
2012-04-02 17:15 ` Michael Holzheu
2012-04-06 8:09 ` Atsushi Kumagai
2012-04-11 8:04 ` Michael Holzheu
2012-04-12 8:49 ` Atsushi Kumagai
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=20120402155353tachibana@mail.jp.nec.com \
--to=tachibana@mxm.nes.nec.co.jp \
--cc=dzickus@redhat.com \
--cc=kexec@lists.infradead.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