> On Tue, Jan 16, 2001 at 10:36:43AM -0800, Linus Torvalds wrote:
>> > I seem to remember more possibly useful information scrolling by my
>> > screen, but it seems to not have made it to the logs, and I will shut
>> > down and fsck the filesystem now...
>>
>> It really needs the stack-trace to debug this sanely (along with
>> translations of what the hex numbers are - see the bugreporting
>> documentation in the kernel source tree).
>
> Got that in the other mail subjected "More information ... ". In the
> meantime it seems the filesystem is unhurt because of this, but reiserfsck
> says
>
> uread_super_block: bad block is found at a new superblock location
> uread_super_block: bad block is found at an old superblock location
>
> which seems bogus. This is reiserfsck from the same suite that mkreiserfs
> came from ("reiserfsprogs 3.x") so they should be talking about the same
> sort of filesystem.
>
The BUG you hit should not corrupt anything, that debugging code is
actually there to prevent silent corruption due to lack of locking.
It is likely you are using an fsck version that can't read the 3.6.x
format. They are still packaging the beta fsck tool for the new format,
I'm not sure the exact download URL yet.
When you mount the FS it tells you which version it is, please include that
info as well.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/