From: Russ Anderson <rja@efs.americas.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: new utility for decoding salinfo records
Date: Tue, 11 Jan 2005 21:22:17 +0000 [thread overview]
Message-ID: <200501112122.j0BLMHZQ086482@efs.americas.sgi.com> (raw)
In-Reply-To: <1105458388.22104.7.camel@quince.llnl.gov>
David Mosberger wrote:
>
> Yes. While individual single-bit errors aren't terribly interesting,
> periodic summaries almost certainly would be. If only so you know
> when to order replacement DIMMs... ;-)
The only reason customers care about single bits (a recovered error)
is out of fear that they will soon lead to a multi-bit error (that
is not recoverable) that crashes the system. If the system recovers
from multi-bits without crashing, either by killing the app
that hit the multi-bit or (better) by backing up to the last
checkpoint (losing processing time, but not data), then the
customer won't even care about single bits.
Then the answer is you order the replacement DIMMs after they fail. :-)
Or maybe not even then. Hard drives have flaw tables that indicate
the parts of the disks to avoid. If memory DIMMs had flaw tables,
and the equivilent of badblocks, why would you replace a DIMM?
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2005-01-11 21:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 15:46 new utility for decoding salinfo records Ben Woodard
2005-01-11 19:03 ` David Mosberger
2005-01-11 19:49 ` Luck, Tony
2005-01-11 20:25 ` David Mosberger
2005-01-11 20:26 ` Ben Woodard
2005-01-11 20:53 ` Mark Goodwin
2005-01-11 21:03 ` Ben Woodard
2005-01-11 21:12 ` Ben Woodard
2005-01-11 21:22 ` Russ Anderson [this message]
2005-01-11 21:23 ` Luck, Tony
2005-01-11 21:25 ` David Mosberger
2005-01-11 21:36 ` David Mosberger
2005-01-11 21:36 ` Matthias Fouquet-Lapar
2005-01-11 21:37 ` Ben Woodard
2005-01-11 21:42 ` David Mosberger
2005-01-11 21:58 ` Russ Anderson
2005-01-11 22:02 ` David Mosberger
2005-01-11 22:26 ` Matthias Fouquet-Lapar
2005-01-12 4:10 ` Keith Owens
2005-01-12 6:08 ` Luck, Tony
2005-01-12 6:43 ` Keith Owens
2005-01-12 9:34 ` Matthias Fouquet-Lapar
2005-01-12 16:57 ` Ben Woodard
2005-01-12 20:46 ` Keith Owens
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=200501112122.j0BLMHZQ086482@efs.americas.sgi.com \
--to=rja@efs.americas.sgi.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