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

Re: [Linux-cluster] Kernel panic in fs/gfs_locking/lock_dlm/lock.c



On Thu, Jul 01, 2004 at 03:00:48AM +0200, Joerg Wendland wrote:
> Hi,
> 
> I am running the cluster package rev. 0406282100 using a custom 2.6.7
> kernel (vanilla) on three VMware ESX virtual machines sharing one SCSI
> disc with GFS on a 10GB logical volume. Setup as proposed in doc/usage.txt, 
> mkfs, mount and first tests all went fine until the first machine crashed 
> after 20 minutes with the following assertion (messages wrapped):
> 
>   lock_dlm:  Assertion failed on line 363 of file 
>       fs/gfs_locking/lock_dlm/lock.c
>   lock_dlm:  assertion:  "!error"
>   lock_dlm:  time = 2482179
>   testfs: num=2,178 err=-22 cur=-1 req=5 lkf=0
> 
>   Kernel panic: lock_dlm:  Record message above and reboot.

This is a bug we know of and are working on right now.

> The other two machines were still running although any process accessing
> the GFS mountpoint would block infinitely with the effect that the whole
> cluster is torn down.

You're using manual fencing so I suspect the remaining nodes are waiting for
you to verify the node is dead and then run "fence_ack_manual" on the node
that's running fence_manual (look in /var/log/messages for the relevant
message on that machine.)

-- 
Dave Teigland  <teigland redhat com>


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