[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] kernel panic - help!

On Wed, Jun 21, 2006 at 03:10:30PM -0300, 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:

Any messages before this?  The best you could hope for with a SAN failure
is that all the cluster nodes withdraw gfs, allowing you to reboot them
without the panic.  So, the end result wouldn't be all that different than
the panics.


> 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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]