lkml.org 
[lkml]   [2003]   [Nov]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: EXT-3 bug with 2.6.0-test9
On Tue, Nov 25, 2003 at 08:51:15PM +0100, Gertjan van Wingerde wrote:
> Hi,
>
> (Please CC me in any replies, as I'm not subscribed to the list)
>
> I've just experienced the strange behaviour that my /usr mount auto-magically
> got mounted read-only, where it was mounted read-write (obviously).
> Investigating the cause of this I've found the following EXT-3 related BUG in
> my log-files:
>
> kernel BUG at fs/jbd/journal.c:1733!
> invalid operand: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01b9bc8>] Tainted: P
> EFLAGS: 00010282
> EIP is at __journal_remove_journal_head+0xf8/0x1c0
> eax: 0000006a ebx: f56a855c ecx: c02df014 edx: 00000286
> esi: df2f2ab0 edi: f7c04800 ebp: df2f2ab0 esp: f3525d80
> ds: 007b es: 007b ss: 0068
> Process kjournald (pid: 49, threadinfo=f3524000 task=f1f1b940)
> Stack: c02b1b40 c029fad7 c02b04ff 000006c5 c02b02ff f56a855c f3524000
> c01b9ccd
> f56a855c f56a855c c01b3669 f56a855c cce38180 df2f2ab0 00000000 df2f2db0
> c01b4967 f7c04800 df2f2ab0 00000003 00000edf 00000000 f7c04878 00000000
> Call Trace:
> [<c01b9ccd>] journal_remove_journal_head+0x3d/0x80
> [<c01b3669>] journal_refile_buffer+0x89/0xd3
> [<c01b4967>] journal_commit_transaction+0x1167/0x1580
> [<c0121f80>] autoremove_wake_function+0x0/0x50
> [<c0121f80>] autoremove_wake_function+0x0/0x50
> [<c011f72d>] schedule+0x33d/0x6a0
> [<c012ca66>] del_timer_sync+0x26/0x90
> [<c01b75c9>] kjournald+0xe9/0x2d0
> [<c0121f80>] autoremove_wake_function+0x0/0x50
> [<c0121f80>] autoremove_wake_function+0x0/0x50
> [<c0109472>] ret_from_fork+0x6/0x14
> [<c01b74c0>] commit_timeout+0x0/0x10
> [<c01b74e0>] kjournald+0x0/0x2d0
> [<c01072a9>] kernel_thread_helper+0x5/0xc
>
> Code: 0f 0b c5 06 ff 04 2b c0 eb 9c c7 44 24 10 15 03 2b c0 c7 44
> <6>note: kjournald[49] exited with preempt_count 2
>
> Also, it looks like the BUG is the result of a large series of events on this
> EXT-3 file-system. See the following logging generated by the kernel just
> prior to the BUG.
>
> Please note that this EXT-3 file-system has been running perfectly for many
> months before.

Did you do anything to this raid array recently, like replace a drive? What
kind of raid is it (software, hardware, 0, 1, 5?)

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

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.036 / U:0.952 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site