From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stef Epardaud <stef@epardaud.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Filesystem silent crash with EXT3
Date: Wed, 12 Sep 2007 15:53:40 +0200 [thread overview]
Message-ID: <m3hcm0dm6z.fsf@maximus.localdomain> (raw)
In-Reply-To: <20070912120203.GA23510@inforealm.org> (Stef Epardaud's message of "Wed, 12 Sep 2007 14:02:03 +0200")
Stef Epardaud <stef@epardaud.net> writes:
> I had no idea my EXT3 filesystem could go wrong without notifying me
> (fsck thought the filesystem was clean before I forced it). Is this
> normal ?
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.
> 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 am in the process of getting a live linux CD to look at the disk,
> maybe there are some logs that can help.
I wouldn't count on it.
> Note that it's the first time I've lost a EXT3 (or EXT2) filesystem
> without having experienced any system crash or power failure to explain
> the filesystem problem.
A system crash or especially power failure shouldn't damage ext3fs.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-09-12 13:53 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 ` Krzysztof Halasa [this message]
2007-09-12 14:16 ` [Resolved: bad RAM] Filesystem silent crash with EXT3 Stef Epardaud
2007-09-13 9:15 ` 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=m3hcm0dm6z.fsf@maximus.localdomain \
--to=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 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®