German Staltari wrote:
Hi, we have a 6 node cluster with FC4, kernel 2.6.16 and the last
stable cluster tarball. The cluster was OK until we had a little SAN
failure, since then, the cluster (entirely) is getting kernel panic.
This is the dump:
qmail-be-04 kernel: ------------[ cut here ]------------
qmail-be-04 kernel: kernel BUG at
/soft/kernel/cluster-1.02.00/gfs-kernel/src/dlm/lock.c:357!
qmail-be-04 kernel: invalid opcode: 0000 [#1]
qmail-be-04 kernel: SMP
qmail-be-04 kernel: CPU: 0
qmail-be-04 kernel: EIP is at do_dlm_unlock+0xd1/0xe5 [lock_dlm]
qmail-be-04 kernel: eax: 00000004 ebx: 00000084 ecx: ffffeb92
edx: 00000000
qmail-be-04 kernel: esi: 00010001 edi: ffffffea ebp: dc9495c0
esp: e382fef4
qmail-be-04 kernel: ds: 007b es: 007b ss: 0068
qmail-be-04 kernel: Process gfs_glockd (pid: 29218,
threadinfo=e382f000 task=f3524550)
qmail-be-04 kernel: Stack: <0>f8e95673 f3b9f700 ffffffea 00000002
007798a8 00000000 00010001 00000084
qmail-be-04 kernel: 00000002 f9618000 00000003 dc9495c0
eaa6ae84 f8e8f52e f8eb46b5 eaa6aeb4
All nodes dies at the same time with this kernel panic.
Thanks
German
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
I think this would help too:
Jun 21 14:59:58 qmail-be-04 kernel: lock_dlm: Assertion failed on line
357 of file /soft/kernel/cluster-1.02.00/gfs-kernel/src/dlm/lock.c
Jun 21 14:59:58 qmail-be-04 kernel: lock_dlm: assertion: "!error"
Jun 21 14:59:58 qmail-be-04 kernel: lock_dlm: time = 2512697
Jun 21 14:59:58 qmail-be-04 kernel: mstore008-002: error=-22
num=2,7798a8 lkf=10001 flags=84
Thanks again
German
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
