From: Stef Epardaud <stef@epardaud.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: [Resolved: bad RAM] Filesystem silent crash with EXT3
Date: Wed, 12 Sep 2007 16:16:05 +0200 [thread overview]
Message-ID: <20070912141604.GB24461@inforealm.org> (raw)
In-Reply-To: <m3hcm0dm6z.fsf@maximus.localdomain>
On Wed, Sep 12, 2007 at 03:53:40PM +0200, Krzysztof Halasa wrote:
> Filesystem clean = the "dirty" flag is not set. With journaling
> fs it basically means the kernel didn't found errors during
> operation.
> It doesn't mean there are no errors.
That's what I assumed, and that's why I forced fsck.
> > If not, what can I do to figure out what went wrong ?
> I'd check with memtest86. Silent fs corruption is usually caused
> by faulty hardware such as RAM.
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.
> A system crash or especially power failure shouldn't damage ext3fs.
That's what I assumed, and I'm glad to see it's still true.
Once again, sorry for the trouble.
--
Stéphane Epardaud
next prev parent reply other threads:[~2007-09-12 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 12:02 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 ` Stef Epardaud [this message]
2007-09-13 9:15 ` [Resolved: bad RAM] " Helge Hafting
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=20070912141604.GB24461@inforealm.org \
--to=stef@epardaud.net \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®