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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/