From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Stef Epardaud <stef@epardaud.net>
Cc: Krzysztof Halasa <khc@pm.waw.pl>, linux-kernel@vger.kernel.org
Subject: Re: [Resolved: bad RAM] Filesystem silent crash with EXT3
Date: Thu, 13 Sep 2007 11:15:35 +0200 [thread overview]
Message-ID: <46E8FFB7.5010508@aitel.hist.no> (raw)
In-Reply-To: <20070912141604.GB24461@inforealm.org>
Stef Epardaud wrote:
> I feel like a fool now. You're absolutely right, my RAM is corrupted.
> Sorry for the trouble folks, I'm very happy to come to the conclusion I
> can rely on EXT3. Now I have to start worrying about how to detect RAM
> corruption before it screws up my data next time.
That is what memory with parity is for. Don't know if
that exists for laptops though.
Helge Hafting
prev parent reply other threads:[~2007-09-13 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 12:02 Filesystem silent crash with EXT3 Stef Epardaud
2007-09-12 13:03 ` Jan Kara
2007-09-12 13:52 ` [OT] Ubuntu GG 2.6.22 (Was: Re: Filesystem silent crash with EXT3) Michael B. Trausch
2007-09-12 14:12 ` Stef Epardaud
2007-09-12 13:53 ` Filesystem silent crash with EXT3 Krzysztof Halasa
2007-09-12 14:16 ` [Resolved: bad RAM] " Stef Epardaud
2007-09-13 9:15 ` Helge Hafting [this message]
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=46E8FFB7.5010508@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=stef@epardaud.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.