From: Robin Holt <holt@sgi.com>
To: Itsuro Oda <oda@valinux.co.jp>
Cc: Robin Holt <holt@sgi.com>,
linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: Yet another crash dump tool
Date: Fri, 15 Oct 2004 08:06:02 -0500 [thread overview]
Message-ID: <20041015130602.GA32020@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <20041015081246.26EB.ODA@valinux.co.jp>
On Fri, Oct 15, 2004 at 09:08:41AM +0900, Itsuro Oda wrote:
> Hi,
>
> > dump device. Can you dump device span multiple volumes? If I
> yes. (maybe. suppose logical volume.)
1TB of memory being written to device at 200Mb/sec will take
1 1/2 hours to dump. That seems like a long time. I start
getting frustrated at a few minutes of lost production. Can
you add a feature to only dump kernel pages, kernel pages +
page/buffer cache, or all of memory? If not, this is a step
backwards in dumping. We have seen RFPs from some potential
customers for as much as 16PB of memory. I am not sure that
anybody builds hardware that scales to that level, but it
certainly shows you a problem.
>
> > have a system using 1TB of physical memory, but 98% of that
> > is allocated as huge TLB pages for users, do I _REALLY_ need to
> > dump them all?
> yes, absolutely, for us.
>
> Our target is customer's production system, not developping/debugging
> system. The chance of capturing fault analysis materials may be only
> one time. If a kernel destroy the memory using user process(page cache
> , buffer cache), looking the pattern of destroy is great helpful to
> analyze. (note that I have encountered such case many times)
> We also analyze user proccesses at the crash time from the dump.
I have analyzed many dumps and never even had the desire to look at
the user processes. Additionally, some of our customers have
classified data. They require assurances that the minimal amount
of their unclassified data is being sent outside their control to
reduce the chance that someone can infer their methods.
>
> > lkcd, and I would hope others, only dump kernel pages unless
> > configured to do otherwise.
>
> You should chose a dump tool you like.
>
> We believe we need whole memory. But we understand there is an opinion
> like you (reduce saving memory is better). We don't force to use our
> tool. We make "mini kernel dump" as independent from kernel as possible.
>
Thanks,
Robin Holt
next prev parent reply other threads:[~2004-10-15 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 23:05 Itsuro Oda
2004-10-14 11:29 ` Robin Holt
2004-10-15 0:08 ` Itsuro Oda
2004-10-15 13:06 ` Robin Holt [this message]
2004-10-18 3:33 ` Itsuro Oda
2004-12-23 11:59 ` [Fastboot] " Eric W. Biederman
2005-01-06 1:54 ` Itsuro Oda
2005-01-06 5:25 ` Eric W. Biederman
2005-01-06 23:55 ` Itsuro Oda
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=20041015130602.GA32020@lnx-holt.americas.sgi.com \
--to=holt@sgi.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oda@valinux.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
all inboxes | Powered by JetHome®