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

[Srinivas Murthy]

Eric,

 I got the output you asked for.

<3>journal_commit_transaction 694 c60b54d0
<4>WARNING: at fs/jbd/commit.c:695 journal_commit_transaction()
<4> [<c0203a1a>] show_trace_log_lvl+0x1a/0x30
<4> [<c0203a42>] show_trace+0x12/0x20
<4> [<c0203b66>] dump_stack+0x16/0x20
<4> [<c02c0e9d>] journal_commit_transaction+0x5cd/0xe60
<4> [<c02c38a5>] kjournald+0xb5/0x1f0
<4> [<c0232a5c>] kthread+0x5c/0xa0
[1]more> q
[1]kdb> bh 0xc60b54d0
buffer_head at 0xc60b54d0
  bno 3297 size 4096 dev 0x900005
  count 1 state 0x8029 [Uptodate Req Mapped Private]
  b_data 0xf5c80000
  b_page 0xc16b9000 b_this_page 0x00000000 b_private 0xf7fb05b0
  b_end_io 0xc02c03a0 journal_end_buffer_io_sync
[1]kdb>

What do you think?

Thanks.

On Tue, Jun 3, 2008 at 8:52 PM, Eric Sandeen <sandeen at redhat.com> wrote:
> Srinivas Murthy wrote:
>
>>
>> [0]kdb> md 0xf76bcf00
>> 0xf76bcf00 f7f63400 00701310 00000004 000001ca   .4....p.........
>> 0xf76bcf10 00000000 00000000 00000000 00000000   ................
>> 0xf76bcf20 00000000 c6320b98 00000000 00000000   ......2.........
>> 0xf76bcf30 00000000 f7386498 f7386b28 00000001   .....d8.(k8.....
>
> ... doesn't look right ...
>
> If you hit this often enough (and since you have kdb) you could modify
> the assert to print the bh address first ....
>
> then it'd be easy to print out, might offer some clues.
>
> -Eric
>