linux-2.6.10 has some bio problems that are fixed in the current
linux-2.6.11 release candidates. The bio problems wreaked havoc with
XFS and there were people reporting EXT3 problems as well with this
bug. I'd recommend trying the latest release candidate and see if your
problem vanishes.
--
jeffrey hundstad
jmerkey wrote:
jmerkey wrote:
Jean-Marc Valin wrote:
Le lundi 28 février 2005 à 08:31 -0700, jmerkey a écrit :
I see this problem infrequently on systems that have low memory
conditions and
with heavy swapping. I have not seen it on 2.6.9 but I have seen
it on 2.6.10.
My machine has 1 GB RAM and I wasn't using much of it at that time (2GB
free on the swap), so I doubt that's the problem in my case.
Jean-Marc
Running the ext2 recover program seems to trigger some good bugs in
2.6.10 with ext3 -- try it. I was doing this
to test some disk tools and I managed to cause these errors with
forcing ext2 recovery from an ext3 fs (which is
probably something to be expected. The recover tools need to get
syncrhonized -- have not tried with
mc yet.) Doesn't happen every time though.
Jeff
lde also causes some problems as well with ext3. Just caused one on
2.6.10. stale or poisoned
cache blocks perhaps?
Jeff
-
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/
-
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/
