[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Fwd: md_thread and kjournald race w/ raid1 on 2-way x86



Srinivas Murthy wrote:

> <6>EXT3-fs: mounted filesystem with ordered data mode.
> <0>Assertion failure in journal_commit_transaction() at
> fs/jbd/commit.c:693: "((&bh->b_count)->counter) == 0"
> <0>------------[ cut here ]------------
> <2>kernel BUG at fs/jbd/commit.c:693!
> <0>invalid opcode: 0000 [#1]
> <0>PREEMPT SMP
> <0>CPU:    1
> <0>EIP:    0060:[<c02c1149>]    Tainted: P        VLI
> <0>EFLAGS: 00010296   (2.6.23.waas #4)
> <0>EIP is at journal_commit_transaction+0x879/0xe00
> <0>eax: 00000096   ebx: f76bcf00   ecx: ffffffff   edx: f7588ac0
> <0>esi: f6c66f88   edi: c0651dcd   ebp: c6549f5c   esp: c6549ec4
> <0>ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
> <0>Process kjournald (pid: 1684, ti=c6548000 task=c39db580 task.ti=c6548000)
> <0>Stack: c0651de8 c0651dcd c0651e44 000002b5 c0651fa0 00000000
> 00000000 f7f63414
> <0>       f7f634dc 00000000 00000fcc f7435034 00000000 00000000
> c6402000 00000000
> <0>       f7f63400 f7386fc0 000005d7 f77fb580 c39db580 f70bdd74
> 00000202 c70f8000
> <0>Call Trace:
> <0> [<c0203a1a>] show_trace_log_lvl+0x1a/0x30
> <0> [<c0203aea>] show_stack_log_lvl+0x9a/0xc0
> <0> [<c0203d46>] show_registers+0x1d6/0x340
> <0> [<c020403d>] die+0x10d/0x220
> <0> [<c02041e1>] do_trap+0x91/0xd0
> <0> [<c0204419>] do_invalid_op+0x89/0xa0
> <0> [<c06317e2>] error_code+0x72/0x78
> <0> [<c02c3845>] kjournald+0xb5/0x1f0
> <0> [<c0232a5c>] kthread+0x5c/0xa0
> <0> [<c020388b>] kernel_thread_helper+0x7/0x1c
> <0> =======================
> <0>Code: 65 c0 b8 a0 1f 65 c0 bf cd 1d 65 c0 89 44 24 10 b8 b5 02 00
> 00 89 44 24 0c b8 44 1e 65 c0 89 7c 24 04 89 44 24 08 e8 57 de f5 ff
> <0f> 0b eb fe 8b 43 34 85 c0 75 4e 8b 53 38 85 d2 0f 84 9e 00 00
> <0>EIP: [<c02c1149>] journal_commit_transaction+0x879/0xe00 SS:ESP 0068:c6549ec4
> <6>SysRq : Changing Loglevel
> <4>Loglevel set to 7
> 
> [0]kdb> btc
> btc: cpu status: Currently on cpu 0

Also, I'd backtrace pid 1684 (kjournald) and dump the bh, see what it
looks like...

kdb> btp 1684
kdb> bh <whatever the address of the buffer head is>

if i remember correctly...

-Eric


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]