On Tue, Feb 22, 2005 at 08:39:21PM +0100, Andreas Steinmetz <[EMAIL PROTECTED]>
wrote:
> To clarify: there were no disk I/O errors, only I/O errors were reported
> by find during operation so it is definitely filesystem corruption
> that is going on here.
> Though find performs heavy read activity there could well be heavy write
> activity be involved due to atime updates so this fits your description.
That wouldn't fill my definition for "heavy", but as it is a race
somewhere, it can happen undr many circumstances, I guess.
> >A reboot fixes this for both ext3 and reiserfs (i.e. the error is gone).
> >
>
> Well, it didn't fix it for me. The fs was trashed for good. The major
> question for me is now usability of md/dm for any purpose with 2.6.x.
> For me this is a showstopper for any kind of 2.6 production use.
Well, I do use reiserfs->aes-loop->lvm/dm->md5/raid5, and it never failed
for me, except once, and the error is likely to be outside reiserfs, and
possibly outside lvm.
However, your case *is* different, as corruption wasn't permament for me,
so chances are that you are hitting sth. else.
Of course, many people find 2.6 too unstable for production use (remember
2.4.x, it was the same), and the most important rule is: if it fails for
you, it's a showstopper.
Also, mild corruption is likely to be more disastrous to reiserfs as it
uses a much denser representation on disk (in other words: it uses space
more efficiently, but that comes at the price of redundancy).
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ [EMAIL PROTECTED]
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
-
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/
