Re: GFS: assertion failure in add_to_queue

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

 



Robert Clark <cluster@xxxxxxxxxxxxxx> writes:

> On Fri, 2008-01-04 at 15:49 +0100, Ferenc Wagner wrote:
>
>> I'm using a 1-node GFS1 "cluster" with DLM locking and sporadically
>> (say once a week) get the following in the kernel logs (Linux 2.6.23):
>> 
>> GFS: fsid=noc:cricket.0: warning: assertion "(tmp_gh->gh_flags & GL_LOCAL_EXCL) || !(gh->gh_flags & GL_LOCAL_EXCL)" failed
>> GFS: fsid=noc:cricket.0:   function = add_to_queue
>> GFS: fsid=noc:cricket.0:   file = /home/wferi/cluster/cluster-2.01.00/gfs-kernel/src/gfs/glock.c, line = 1420
>> GFS: fsid=noc:cricket.0:   time = 1197666253
>
>   Could be this:
>
>     https://bugzilla.redhat.com/show_bug.cgi?id=272301
>
> We're seeing it too. The trigger is a process attempting multiple locks
> on a single file. Occasionally it seems to cause an oops & panic as
> well.
>
> As far as I know, there's no fix available for it at the moment.

Thanks for the reply.  Though that's far from comforting...
-- 
Regards,
Feri.

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux