Thanks Dave. I'll try to play around with journal segment size. Didn't notice this knob till now. FWIW, this crash happens only when Journal size is reduced from 6M to 4M on 3-node cluster w/ 512M filesystem. - Sridharan > -----Original Message----- > From: David Teigland [mailto:teigland@xxxxxxxxxx] > Sent: Wednesday, February 14, 2007 1:12 PM > To: Sridharan Ramaswamy (srramasw) > Cc: linux-cluster@xxxxxxxxxx > Subject: Re: GFS journaling related crash > > On Wed, Feb 14, 2007 at 12:49:31PM -0800, Sridharan Ramaswamy > (srramasw) wrote: > > Feb 14 11:41:50 cfs1 kernel: GFS: fsid=cisco:gfs2.0: > head_off = 61856, > > head_wrap = 8 > > Feb 14 11:41:50 cfs1 kernel: GFS: fsid=cisco:gfs2.0: > dump_off = 61856, > > dump_wrap = 7 > > Feb 14 11:41:50 cfs1 kernel: GFS: fsid=cisco:gfs2.0: > assertion "FALSE" > > failed > > Feb 14 11:41:50 cfs1 kernel: GFS: fsid=cisco:gfs2.0: function = > > check_seg_usage > > Feb 14 11:41:50 cfs1 kernel: GFS: fsid=cisco:gfs2.0: file = > > /download/gfs/cluster.cvs-rhel4/gfs-kernel/src/gfs/log.c, line = 590 > > Have you tried playing with the journal segment size with > gfs_mkfs -s ? > Scaling that down along with the journal size might have some effect. > You might also disable quotas if you haven't yet which should > reduce the > transaction sizes. WRT the assertion, that might be something that's > fixable, but it would require delving into the logging code a bit. > > Dave > -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
