lkml.org 
[lkml]   [2007]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Filesystem silent crash with EXT3
From
Date
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-09-12 15:57    [W:0.039 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site