kernel BUG with 2.4.1-pre7 reiserfs

kernel BUG with 2.4.1-pre7 reiserfs

[Jakob Borg]

Hi,

I recently got this in my logs after moving /home to reiserfs. It is a plain
2.4.1-pre7 SMP system (.config attached).

Jan 16 19:15:02 narayan kernel: journal_begin called without kernel lock held
Jan 16 19:15:02 narayan kernel: kernel BUG at journal.c:423!
Jan 16 19:15:02 narayan kernel: CPU:   0

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...

Regards,

-- 
Jakob Borg            mailto:jakob@borg.pp.se       (personal)
UNIX/network admin    mailto:jakob@debian.org    (development)
systems programmer    mailto:jakob@morotsmedia.se       (work)
                      http://jakob.borg.pp.se/
-
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/

Re: kernel BUG with 2.4.1-pre7 reiserfs

[Linus Torvalds]

In article <20010116192041.A466@borg.pp.se>,
Jakob Borg  <jakob@borg.pp.se> wrote:
>Hi,
>
>I recently got this in my logs after moving /home to reiserfs. It is a plain
>2.4.1-pre7 SMP system (.config attached).
>
>Jan 16 19:15:02 narayan kernel: journal_begin called without kernel lock held
>Jan 16 19:15:02 narayan kernel: kernel BUG at journal.c:423!
>Jan 16 19:15:02 narayan kernel: CPU:   0
>
>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). 

		Linus
-
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/

Re: kernel BUG with 2.4.1-pre7 reiserfs

[Jakob Borg]

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.

Regards,

-- 
Jakob Borg            mailto:jakob@borg.pp.se       (personal)
UNIX/network admin    mailto:jakob@debian.org    (development)
systems programmer    mailto:jakob@morotsmedia.se       (work)
                      http://jakob.borg.pp.se/
-
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/

Re: kernel BUG with 2.4.1-pre7 reiserfs

[Chris Mason]

On Tuesday, January 16, 2001 07:58:37 PM +0100 Jakob Borg
<jakob@borg.pp.se> wrote:

> 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/

Re: kernel BUG with 2.4.1-pre7 reiserfs

[Jakob Borg]

On Tue, Jan 16, 2001 at 02:18:43PM -0500, Chris Mason wrote:
> When you mount the FS it tells you which version it is, please include that
> info as well.

I am rebooting with the patch from you (Chris) in about 30 seconds. This is
the output from reiserfs when booting:

reiserfs: checking transaction log (device 16:41) ...
reiserfs: replayed 5 transactions in 4 seconds
Using tea hash to sort names
reiserfs: using 3.5.x disk format
ReiserFS version 3.6.25

-- 
Jakob Borg            mailto:jakob@borg.pp.se       (personal)
UNIX/network admin    mailto:jakob@debian.org    (development)
systems programmer    mailto:jakob@morotsmedia.se       (work)
                      http://jakob.borg.pp.se/
-
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/