public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Dump driver module
Date: Wed, 14 May 2003 06:33:33 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705778@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705751@msgid-missing>

On Wed, May 14, 2003 at 12:32:17PM +1000, Martin Pool wrote:
> But you also need to know which disk to write to, and where.
...
> If any of this got screwed up, you might
> write your dump over /home instead -- and then rather than a possibly
> once-off kernel crash, you've lost lots of data.

I'll take that risk since I've never seen it nor heard of it
happening with HPUX after ~6 years of working HPUX IO subsystems.
I'm sure HPUX has done things to help mitigate that risk.
(like storing paths in NVRAM or some other hard to reach place.)
All problem reports (including memory corruption problems) came with
crash dumps.

Besides, fsck after the reboot is much more likely to trash data
on disk than the original memory corruption problem.

While it's clearly feasible to dump over gigabit networks,
I'm not sure how pervasive gigabit networks are.
Probably standard now for core commercial/scientific centers.
I fear dumping 4GB of memory over 100BT would be painful.
(I pulled 4GB out of a hat; rx5670 supports 48GB of RAM).

grant


  parent reply	other threads:[~2003-05-14  6:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  7:02 [Linux-ia64] Dump driver module Bruno Vidal
2003-05-13  7:18 ` Stephane Eranian
2003-05-13  7:25 ` David Mosberger
2003-05-13  7:38 ` Bruno Vidal
2003-05-13  8:08 ` David Mosberger
2003-05-13 13:29 ` Howell, David P
2003-05-13 14:39 ` Bruno Vidal
2003-05-14  2:13 ` Keith Owens
2003-05-14  2:14 ` Martin Pool
2003-05-14  2:21 ` David Mosberger
2003-05-14  2:32 ` Martin Pool
2003-05-14  2:40 ` David Mosberger
2003-05-14  6:33 ` Grant Grundler [this message]
2003-05-14  6:50 ` Bruno Vidal
2003-05-14 13:29 ` Matthew Wilcox
2003-05-14 15:41 ` Grant Grundler

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=marc-linux-ia64-105590723705778@msgid-missing \
    --to=iod00d@hp.com \
    --cc=linux-ia64@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