[Lustre-discuss] 1.8.1.1
Papp Tamas
tompos at martos.bme.hu
Thu Dec 10 15:37:01 PST 2009
On 2009. 12. 06. 1:47, Andreas Dilger wrote:
>>
>> ./configure
>> --with-linux=/usr/src/kernels/2.6.18-128.7.1.el5_lustre.1.8.1.1-x86_64/
>
>
> This should be the right kernel for b1_8, according to lustre/ChangeLog
>
>
> This is trying to build the ldiskfs module from the ext3 sources. It
> _should_ work, given that you have the right kernel sources, but
> clearly either the patch was changed, or something is different
> between your ext3 and what the patch expects. This is normally just a
> simple context error.
>
> To fix this:
>
> cd ldiskfs/ldiskfs/linux-stage
> quilt push -f
> {apply include/linux/ext3_fs.h.rej to ext3_fs.h by hand}
> quilt refresh
> cd -
>
> then "make" should work again.
>
Well, it was not working, and by the way, my guess is that it should not
work. I didn't write, but
/usr/src/kernels/2.6.18-128.7.1.el5_lustre.1.8.1.1-x86_64/ belongs to
the official kernel-lustre-devel-2.6.18-128.7.1.el5_lustre.1.8.1.1 package.
Anyway, a build an own kernel and lustre b1_8 with the patches from the
bug 19557:
Linux meta1 2.6.18-prep #1 SMP Sun Dec 6 14:40:15 CET 2009 x86_64 x86_64
x86_64 GNU/Linux
I installed it on the MDS and the tw OSSs. Unofortunately no luck:
Dec 9 18:41:36 node1 kernel: ll_ost_io_05 S ffff81023f353860 0
4421 1 4422 4420 (L-TLB)
Dec 9 18:41:36 node1 kernel: ffff810229cf9990 0000000000000046
00000000000000fd ffffffff88491b91
Dec 9 18:41:36 node1 kernel: ffff8101ff1d65a0 000000000000000a
ffff810229c080c0 ffff81023f353860
Dec 9 18:41:36 node1 kernel: 0000f4410ae68bb7 0000000000000825
ffff810229c082a8 0000000300000000
Dec 9 18:41:36 node1 kernel: Call Trace:
Dec 9 18:41:36 node1 kernel: [<ffffffff88491b91>]
:lnet:LNetMDBind+0x301/0x450
Dec 9 18:41:36 node1 kernel: [<ffffffff8003dacd>]
lock_timer_base+0x1b/0x3c
Dec 9 18:41:36 node1 kernel: [<ffffffff8001caa7>] __mod_timer+0xb0/0xbe
Dec 9 18:41:36 node1 kernel: [<ffffffff8006387b>]
schedule_timeout+0x8a/0xad
Dec 9 18:41:36 node1 kernel: [<ffffffff80096ff3>] process_timeout+0x0/0x5
Dec 9 18:41:36 node1 kernel: [<ffffffff888234ca>]
:ost:ost_brw_write+0x137a/0x23a0
Dec 9 18:41:36 node1 kernel: [<ffffffff8859f998>]
:ptlrpc:ptlrpc_send_reply+0x5c8/0x5e0
Dec 9 18:41:36 node1 kernel: [<ffffffff8856aab0>]
:ptlrpc:target_committed_to_req+0x40/0x120
Dec 9 18:41:36 node1 kernel: [<ffffffff8881f81d>]
:ost:ost_brw_read+0x189d/0x1a70
Dec 9 18:41:36 node1 kernel: [<ffffffff885a3e25>]
:ptlrpc:lustre_msg_get_version+0x35/0xf0
Dec 9 18:41:36 node1 kernel: [<ffffffff8008c3ba>]
default_wake_function+0x0/0xe
Dec 9 18:41:36 node1 kernel: [<ffffffff885a3ee8>]
:ptlrpc:lustre_msg_check_version_v2+0x8/0x20
Dec 9 18:41:36 node1 kernel: [<ffffffff8882709e>]
:ost:ost_handle+0x2bae/0x53e0
Dec 9 18:41:36 node1 kernel: [<ffffffff8858233e>]
:ptlrpc:ldlm_refresh_waiting_lock+0xbe/0x110
Dec 9 18:41:36 node1 kernel: [<ffffffff88499485>]
:lnet:lnet_match_blocked_msg+0x375/0x390
Dec 9 18:41:36 node1 kernel: [<ffffffff8855e1d4>]
:ptlrpc:ldlm_lock_get+0x4/0x10
Dec 9 18:41:36 node1 kernel: [<ffffffff885ae45d>]
:ptlrpc:ptlrpc_check_req+0x1d/0x110
Dec 9 18:41:36 node1 kernel: [<ffffffff885b10b9>]
:ptlrpc:ptlrpc_server_handle_request+0xa79/0x1150
Dec 9 18:41:36 node1 kernel: [<ffffffff8008a7e4>]
__wake_up_common+0x3e/0x68
Dec 9 18:41:36 node1 kernel: [<ffffffff885b4ae8>]
:ptlrpc:ptlrpc_main+0x1258/0x1420
Dec 9 18:41:36 node1 kernel: [<ffffffff8008c3ba>]
default_wake_function+0x0/0xe
Dec 9 18:41:36 node1 kernel: [<ffffffff8005dfb1>] child_rip+0xa/0x11
Dec 9 18:41:36 node1 kernel: [<ffffffff885b3890>]
:ptlrpc:ptlrpc_main+0x0/0x1420
Dec 9 18:41:36 node1 kernel: [<ffffffff8005dfa7>] child_rip+0x0/0x11
Dec 9 18:41:36 node1 kernel:
Dec 9 18:41:36 node1 kernel: LustreError: dumping log to
/tmp/lustre-log.1260380496.4421
Should I install this patched lustre on the clients too? Or is the
problem something else?
I'm sorry for the messy mail.
Thank you,
tamas
More information about the lustre-discuss
mailing list