<div>i'm looking to move forward on this, so sorry if I seem a little anxious, I'm excited to get it going correctly. </div>
<div> </div>
<div>Are there patches that I can get somewhere to apply? Or a path I can explore to begin getting this kernel up to speed with the correct ocfs2-dlm?</div>
<div>Or possibly are the correct ocfs2-dlm files in the kernel source tree for later kernels that I could upgrade to?</div>
<div> </div>
<div>Thanks for the replies so far!</div>
<div><br> </div>
<div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Sunil Mushran</b> <<a href="mailto:Sunil.Mushran@oracle.com">Sunil.Mushran@oracle.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The ocfs2 shipping with that kernel is missing few dlm patches.<br>I'll put together some patches. There is a bugzilla logged on this.
<br><br>Bleeding Edge wrote:<br>><br>> I've gotten the error below several times on different builds on<br>> different hardware:<br>><br>> The setup is a bit different from the norm, it's a xenofied 2.6.16<br>
> kernel runing Debian Etch with block device backends for the ocfs2<br>> storage. (yes I know it's an adventerous setup). I'm using the ocfs2<br>> from the kernel, and the ocfs2-tools from Debian, ( 1.2.1-1).<br>
><br>> 99% of the time it's great, fences well, does it's job. Only one node<br>> is actually being "used" but both are on and mounted. I have seen<br>> these errors when just leaving it overnight, and after a while it
<br>> bombs, system load doesn't seem to be a factor. When I logged in this<br>> morning, on the node that had very little load, I found this in the<br>> console:<br>><br>> (2016,0):dlm_proxy_ast_handler:321 ERROR: got ast for unknown lockres!
<br>> cookie=144115188078155225, name=M0000000000000006676050a149f878,<br>> namelen=31<br>><br>> When I attempted to shutdown the 2nd node, it exploded with the<br>> following error, and locked up both nodes, and I'm looking for
<br>> clarification, or even just a starting point:<br>><br>> Thanks<br>><br>><br>><br>><br>> kernel BUG at <bad filename>:58347!<br>> invalid opcode: 0000 [#1]<br>> SMP<br>> Modules linked in: ocfs2 ipv6 ocfs2_dlmfs ocfs2_dlm ocfs2_nodemanager
<br>> configfs dm_snapshot dm_mirror dm_mod ext3 jbd<br>> CPU: 0<br>> EIP: 0061:[<d113cec5>] Not tainted VLI<br>> EFLAGS: 00010202 (2.6.16-xen-domU #1)<br>> EIP is at __dlm_lockres_reserve_ast+0x35/0x40 [ocfs2_dlm]
<br>> eax: 00000028 ebx: cd9bfa80 ecx: f578d000 edx: 00000000<br>> esi: 00000002 edi: cb695200 ebp: cd9bfa80 esp: cb079d3c<br>> ds: 007b es: 007b ss: 0069<br>> Process umount (pid: 8046, threadinfo=cb078000 task=cf7ac030)
<br>> Stack: <0>cd9bfa80 cd9bfa8c d1140c57 cd9bfa80 cc412ea0 0000001f<br>> 00000002 00000028<br>> 00000000 c03b8203 00000400 c011e200 cb695230 cd9bfa8c d114c6cc<br>> cd9bfac8<br>> 02000000 c4fe7000 c82d2e00 c4fe7000 00000000 cc412ea0 0000001f
<br>> 00000000<br>> Call Trace:<br>> [<d1140c57>] dlm_migrate_lockres+0x677/0x15f0 [ocfs2_dlm]<br>> [<c011e200>] vprintk+0x290/0x330<br>> [<c02f45d6>] schedule+0x536/0x860<br>> [<d11347a5>] dlm_purge_lockres+0x75/0x230 [ocfs2_dlm]
<br>> [<d1131868>] dlm_unregister_domain+0x108/0x740 [ocfs2_dlm]<br>> [<c02f49cf>] wait_for_completion+0xaf/0x110<br>> [<c0116b70>] default_wake_function+0x0/0x20<br>> [<d126ae8d>] ocfs2_remove_lockres_tracking+0xd/0x40 [ocfs2]
<br>> [<c0133552>] kthread_stop_sem+0x82/0xb0<br>> [<d127038d>] ocfs2_dlm_shutdown+0xed/0x360 [ocfs2]<br>> [<d129f295>] ocfs2_unregister_net_handlers+0x25/0xc0 [ocfs2]<br>> [<d129a521>] ocfs2_dismount_volume+0x181/0x4c0 [ocfs2]
<br>> [<d129aa81>] ocfs2_put_super+0x31/0xe0 [ocfs2]<br>> [<c016c3f2>] generic_shutdown_super+0x92/0x150<br>> [<c016c4d9>] kill_block_super+0x29/0x50<br>> [<c016c5ea>] deactivate_super+0x7a/0xa0
<br>> [<c018453b>] sys_umount+0x4b/0x2d0<br>> [<c0105171>] syscall_call+0x7/0xb<br>> Code: 43 48 84 c0 7f 21 0f b7 43 5a a8 20 75 0b a8 20 75 19 f0 ff 43<br>> 44 59 5b c3 89 1c 24 e8 15 6a ff ff 0f b7 43 5a eb e7 0f 0b eb db <0f>
<br>> 0b eb e3 8d b4 26 00 00 00 00 53 8b 5c 24 0c 8d 43 48 e8 73<br>> Badness in do_exit at kernel/exit.c:802<br>> [<c012134d>] do_exit+0x89d/0x8b0<br>> [<c011007b>] prepare_for_smp+0x4b/0x160<br>
> [<c0105c9a>] die+0x23a/0x240<br>> [<c0106590>] do_invalid_op+0x0/0xc0<br>> [<c010663f>] do_invalid_op+0xaf/0xc0<br>> [<d113cec5>] __dlm_lockres_reserve_ast+0x35/0x40 [ocfs2_dlm]<br>
> [<d113d7a5>] dlm_init_mle+0x85/0x180 [ocfs2_dlm]<br>> [<c0105303>] error_code+0x2b/0x30<br>> [<d113cec5>] __dlm_lockres_reserve_ast+0x35/0x40 [ocfs2_dlm]<br>> [<d1140c57>] dlm_migrate_lockres+0x677/0x15f0 [ocfs2_dlm]
<br>> [<c011e200>] vprintk+0x290/0x330<br>> [<c02f45d6>] schedule+0x536/0x860<br>> [<d11347a5>] dlm_purge_lockres+0x75/0x230 [ocfs2_dlm]<br>> [<d1131868>] dlm_unregister_domain+0x108/0x740 [ocfs2_dlm]
<br>> [<c02f49cf>] wait_for_completion+0xaf/0x110<br>> [<c0116b70>] default_wake_function+0x0/0x20<br>> [<d126ae8d>] ocfs2_remove_lockres_tracking+0xd/0x40 [ocfs2]<br>> [<c0133552>] kthread_stop_sem+0x82/0xb0
<br>> [<d127038d>] ocfs2_dlm_shutdown+0xed/0x360 [ocfs2]<br>> [<d129f295>] ocfs2_unregister_net_handlers+0x25/0xc0 [ocfs2]<br>> [<d129a521>] ocfs2_dismount_volume+0x181/0x4c0 [ocfs2]<br>> [<d129aa81>] ocfs2_put_super+0x31/0xe0 [ocfs2]
<br>> [<c016c3f2>] generic_shutdown_super+0x92/0x150<br>> [<c016c4d9>] kill_block_super+0x29/0x50<br>> [<c016c5ea>] deactivate_super+0x7a/0xa0<br>> [<c018453b>] sys_umount+0x4b/0x2d0
<br>> [<c0105171>] syscall_call+0x7/0xb<br>> (6766,0):o2net_idle_timer:1284 connection to node vserver1-3 (num 2)<br>> at <a href="http://10.10.69.113:7777">10.10.69.113:7777</a> <<a href="http://10.10.69.113:7777">
http://10.10.69.113:7777</a>> has been idle for 10<br>> seconds, shutting it down.<br>> (6766,0):o2net_idle_timer:1297 here are some times that might help<br>> debug the situation: (tmr 1160659302.852081 now 1160659312.846775
dr<br>> 1160659307.850562 adv 1160659302.852111:1160659302.852111 func<br>> (b9bad2f8:506) 1160659302.852082:1160659302.852088)<br>> BUG: soft lockup detected on CPU#0!<br>><br>> Pid: 6766, comm: dlm_thread
<br>> EIP: 0061:[<c02f5e57>] CPU: 0<br>> EIP is at _spin_lock+0x7/0x10<br>> EFLAGS: 00000286 Not tainted (2.6.16-xen-domU #1)<br>> EAX: cd9bfac8 EBX: cd9bfac8 ECX: cb69520c EDX: cb695200<br>> ESI: cd9bfaa4 EDI: 00000000 EBP: cb695214 DS: 007b ES: 007b
<br>> CR0: 8005003b CR2: b7eec83c CR3: 00e76000 CR4: 00000660<br>> [<d1134e0c>] dlm_thread+0x26c/0x11f0 [ocfs2_dlm]<br>> [<c0133720>] kthread+0xc0/0x110<br>> [<c0133960>] autoremove_wake_function+0x0/0x60
<br>> [<c0133734>] kthread+0xd4/0x110<br>> [<d1134ba0>] dlm_thread+0x0/0x11f0 [ocfs2_dlm]<br>> [<c0133660>] kthread+0x0/0x110<br>> [<c0102bd5>] kernel_thread_helper+0x5/0x10<br>>
<br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> Ocfs2-users mailing list<br>> <a href="mailto:Ocfs2-users@oss.oracle.com">
Ocfs2-users@oss.oracle.com</a><br>> <a href="http://oss.oracle.com/mailman/listinfo/ocfs2-users">http://oss.oracle.com/mailman/listinfo/ocfs2-users</a><br>><br></blockquote></div><br>