[Linux-cluster] GFS2 interesting death with error

[Steven Whitehouse]

Hi,

On Thu, 2009-11-05 at 14:36 -0500, Allen Belletti wrote:
> Saw an interesting and different GFS2 death this morning that I wanted 
> to pass along in case anyone has insights.  We have not seen any of the 
> "hanging in dlm_posix_lock" since fsck'ing early Sunday morning.  In any 
> case I'm pretty confident that's being triggered by the creation & 
> deletion of ".lock" files within Dovecot.  This was something completely 
> different and it left some potentially useful debug info in the logs.
> 
> Things were running fine when the machine "post2" abruptly died.  The 
> following was found to have been enscribed upon its stone logs:
> 
> Nov  5 10:56:28 post2 kernel: original: gfs2_rindex_hold+0x32/0x153 [gfs2]
> Nov  5 10:56:28 post2 kernel: pid : 27197
> Nov  5 10:56:28 post2 kernel: lock type: 2 req lock state : 3
> Nov  5 10:56:28 post2 kernel: new: gfs2_rindex_hold+0x32/0x153 [gfs2]
> Nov  5 10:56:28 post2 kernel: pid: 27197
> Nov  5 10:56:28 post2 kernel: lock type: 2 req lock state : 3
> Nov  5 10:56:28 post2 kernel:  G:  s:SH n:2/2053b f:s t:SH d:EX/0 l:0 
> a:0 r:4
> Nov  5 10:56:28 post2 kernel:   H: s:SH f:H e:0 p:27197 [procmail] 
> gfs2_rindex_hold+0x32/0x153 [gfs2]
> Nov  5 10:56:28 post2 kernel:   I: n:23/132411 t:8 f:0x00000010
> Nov  5 10:56:28 post2 kernel: ----------- [cut here ] --------- [please 
> bite here ] ---------
> Nov  5 10:56:32 post2 kernel: Kernel BUG at 
> ...ir/build/BUILD/gfs2-kmod-1.92/_kmod_build_/glock.c:950
> 
There should have been a stack trace following this message which is
critical to tracking down the bug. What kernel version is this?

Did you run gfs2_grow at any time?

Steve.