Hi, What version of GFS2 are you using? This has been seen before, but not for a fair time now, so I suspect you might be using old code, Steve. On Mon, 2007-06-04 at 10:59 +0200, Kristoffer Lippert wrote: > Hi, > > I get a slightly strange problem: > > I'm setting up a new 2. node cluster, and one of my nodes gives this > in the message log: > > Jun 4 10:10:33 app01 kernel: GFS2: fsid=onmagcluster:onmag_gfs.1: > fatal: assertion "gfs2_glock_is_held_excl(gl)" failed > > Jun 4 10:10:33 app01 kernel: GFS2: fsid=onmagcluster:onmag_gfs.1: > function = glock_lo_after_commit, file = fs/gfs2/lops.c, line = 61 > > Jun 4 10:10:33 app01 kernel: GFS2: fsid=onmagcluster:onmag_gfs.1: > about to withdraw this file system > Jun 4 10:10:33 app01 kernel: GFS2: fsid=onmagcluster:onmag_gfs.1: > telling LM to withdraw > > After the error, the san is locked. I can't get the second node off > the lock. I did a ls of /sandata (where the san is mounted), and i > can't kill the process. > > I cannot even reboot the server with reboot. I have to powercycle it > to get it back online. > > I found one similar error on google, posted to this list, but i did > not find any replys. > Have anyone got any clues? > > > Mvh / Kind regards > > Kristoffer Lippert > Systemansvarlig > JP/Politiken A/S > Online Magasiner > > Tlf. +45 8738 3032 > Cell. +45 6062 8703 > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
