[Ocfs2-users] kernel panic - ocfs2-1.4.1 - redhat EL5 2.6.18-92.el5xen

[James Masson]

Hi list,

We've just had a kernel panic/reboot on one of our ocfs2 cluster nodes.
It's a 3 node cluster of xen Dom U's running Redhat EL5.2, and they're
normally very stable.

Has anybody seen this particular fault before, or can anyone provide an
analysis?

thanks

James Masson

#############
(1796,1):ocfs2_unlock_ast:2739 ERROR: Dlm passes status 24 for lock
M000000000000000010031300000000, unlock_action 1
(1796,1):dlmunlock:685 ERROR: dlm status = DLM_BADPARAM
(1796,1):ocfs2_cancel_convert:3036 ERROR: Dlm error "DLM_BADPARAM" while
calling dlmunlock on resource M000000000000000010031300000000: invalid
lock mode specified
(1796,1):ocfs2_unblock_lock:3071 ERROR: status = -22
(1796,1):ocfs2_process_blocked_lock:3375 ERROR: status = -22
(1796,1):ocfs2_prepare_downconvert:2941 ERROR: lockres->l_level (0) <=
new_level (0)
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at ...uild/smushran/BUILD/ocfs2-1.4.1/fs/ocfs2/dlmglue.c:2942
invalid opcode: 0000 [1] SMP
last sysfs file: /block/dm-1/range
CPU 1
Modules linked in: i2c_dev i2c_core hidp l2cap bluetooth ocfs2(U)
ocfs2_dlmfs(U) ocfs2_dlm(U) ocfs2_nodemanager(U) configfs sunrpc xennet
ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib
_addr iscsi_tcp libiscsi scsi_transport_iscsi scsi_mod dm_multipath
parport_pc lp parport pcspkr dm_snapshot dm_zero dm_mirror dm_mod xenblk
ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 1796, comm: ocfs2dc Tainted: G      2.6.18-92.el5xen #1
RIP: e030:[<ffffffff882eaf5a>]  [<ffffffff882eaf5a>]
:ocfs2:ocfs2_prepare_downconvert+0x8e/0x10d
RSP: e02b:ffff8801f6b6be50  EFLAGS: 00010082
RAX: 0000000000000058 RBX: ffff88009c061300 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88009c061300 RDI: 0000000000000001
RBP: 0000000000000000 R08: ffffffff804db7a8 R09: 00000000000020db
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8801f68b9800
R13: 0000000000000005 R14: 0000000000000000 R15: 0000000000000000
FS:  00002b77a23df250(0000) GS:ffffffff805ae080(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process ocfs2dc (pid: 1796, threadinfo ffff8801f6b6a000, task
ffff8801ffa75100)
Stack:  ffff88009c061310  0000000000000000  ffff88009c061300 
ffffffff882f02ac
 0000000000000001  00000000802875cb  0000000000000000  ffff8801ffa75100
 ffffffff8029b941  ffff8801f6b6be98
Call Trace:
 [<ffffffff882f02ac>] :ocfs2:ocfs2_downconvert_thread+0x4db/0x83b
 [<ffffffff8029b941>] autoremove_wake_function+0x0/0x2e
 [<ffffffff8029b729>] keventd_create_kthread+0x0/0xc4
 [<ffffffff882efdd1>] :ocfs2:ocfs2_downconvert_thread+0x0/0x83b
 [<ffffffff8029b729>] keventd_create_kthread+0x0/0xc4
 [<ffffffff802339c8>] kthread+0xfe/0x132
 [<ffffffff80260b24>] child_rip+0xa/0x12
 [<ffffffff8029b729>] keventd_create_kthread+0x0/0xc4
 [<ffffffff802338ca>] kthread+0x0/0x132
 [<ffffffff80260b1a>] child_rip+0x0/0x12


MCode: 0f 0b 68 d7 da 31 88 c2 7e 0b f6 05 77 d5 f7 ff 08 74 4c f6
MRIP  [<ffffffff882eaf5a>] :ocfs2:ocfs2_prepare_downconvert+0x8e/0x10d
M RSP <ffff8801f6b6be50>
M <0>Kernel panic - not syncing: Fatal exception
###################