Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted

["Jesper Juhl" <jesper.juhl@gmail.com>]

On 18/05/07, Martin Mokrejs <mmokrejs@ribosome.natur.cuni.cz> wrote:
> Hi,
>   I just tried the 2.6.22-r1 candidate to test whether some bug I have
> hit in the past still exists. I did use 2.6.20.6 so far. So, I have
> cleanly rebooted to use the new kernel, after the machine came up I
> tried to mess with the bug, and had to reboot again to play with kernel
> commandline parameters. Unfortunately, on the next reboot fsck was
> schedules on my filesystem after 38 clean mounts. :( And the problem
> started. The fsck found some unused inodes, but probably did not know
> where do they belong to, but it deleted them automagically. Finally, the
> fsck died because it cannot fine some '..' entry.

How do you know that the corruption was caused by 2.6.21-rc1 ?
Isn't it possible that the corruption was created by an earlier
kernel, but only detected when a forced fsck was run - which just
happened to be while you were running 2.6.21-rc1 ...

My point is that, as far as I can see, there's nothing tying
2.6.21-rc1 specifically to this corruption... or?

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/