On Fri, Oct 29, 2004 at 08:02:37PM +0530, Ritesh Agrawal wrote: > ~ In the migration process , when there were 3 nodes , all the systems > ~ were running smoothly > ~ but ! > ~ when I added some more load (mailboxes) with 2 more backend nodes, after > ~ some time 2-3 nodes (any of the nodes in cluster) hanged with the > ~ following error: > > ~ Oct 24 11:04:29 c5 kernel: GFS: Assertion failed on line 599 of file > ~ inode.c > ~ Oct 24 11:04:29 c5 kernel: GFS: assertion: "(tmp_gh->gh_flags > ~ &GL_LOCAL_EXCL) || !(gh->gh_flags & GL_LOCAL_EXCL)" > ~ Oct 24 11:04:29 c5 kernel: GFS: time = 1095145469 Oct 24 11:04:29 c5 > ~ kernel: GFS: fsid=310farm:gfs01.2: glock = (4, 0) > ~ Oct 24 11:04:29 c5 kernel: > ~ Oct 24 11:04:29 c5 kernel: Kernel panic: GFS: Record message above and > ~ reboot. Errr... I'm at a loss as to how you could have gotten this error message. There is no assertion like that in inode.c. The timestamp that GFS printed out "time = 1095145469" is no where near Oct 24 11:04:29. The panic message looks suspiciously similar to one posted in September when someone forgot to recompile their lock_harness module. https://www.redhat.com/archives/linux-cluster/2004-September/msg00075.html Maybe you had a cut-and-paste error? -- Ken Preslan <kpreslan@xxxxxxxxxx>
