> On Fri, 29 Oct 1999, Ingo Molnar wrote:
>
> >2.3.24. I first suspected that the high memory patch did it, but it turned
> >out that unmap_underlying_metadata() hack either introduced or triggered
> >data/metadata corruption. (take a look at the buffer.c change) I cannot
>
> unmap_underlying_metadata is obviously right to my eyes.
well, it obviously and easily corrupted my filesystem (and others'
filesystems) about a 100 times until i found the change that triggered (or
caused) it, so would you mind testing it on low memory conditions?
(running with mem=32m for a while on an SMP box and hacking the kernel
should be just fine for you see the filesystem corruption)
> Better that you apply the inode bugfix posted by V. Ganesh today.
(yep, saw it too, that indeed might be the explanation - but i've had
enough filesystems trashed for the time being :)
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/