[Linux-cluster] GFS panic in check_seg_usage

[Sridharan Ramaswamy (srramasw)]

I'm hitting this crash while testing small file create/write/delete test
with low journal size. It happened twice for me, once when I enable data
journaling and the other without that.
 
This seems similar to bugzilla,
 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=146672
 
Has anyone seen this lately?
 
>From /var/log/message,
 
Feb 12 16:37:42 cfs1 kernel: GFS: fsid=cisco:gfs2.0: head_off = 62144,
head_wrap = 16
Feb 12 16:37:42 cfs1 kernel: GFS: fsid=cisco:gfs2.0: head_off = 62144,
head_wrap = 16
Feb 12 16:37:42 cfs1 kernel: GFS: fsid=cisco:gfs2.0: dump_off = 62144,
dump_wrap = 15
Feb 12 16:37:42 cfs1 kernel: GFS: fsid=cisco:gfs2.0: dump_off = 62144,
dump_wrap = 15
Feb 12 16:37:42 cfs1 kernel:  [<e1086506>] gfs_assert_i+0x48/0x69 [gfs]
Feb 12 16:37:42 cfs1 kernel:  [<e1086506>] gfs_assert_i+0x48/0x69 [gfs]
Feb 12 16:37:42 cfs1 kernel:  [<e106e880>] check_seg_usage+0x197/0x19f
[gfs]
Feb 12 16:37:42 cfs1 kernel:  [<e106e880>] check_seg_usage+0x197/0x19f
[gfs]
Feb 12 16:37:42 cfs1 kernel:  [<e106ea03>] sync_trans+0x143/0x1b1 [gfs]

>From console,
 
gfs_log_reserve+0x19e/0x20e [gfs]
glock_wait_internal
gfs_glock_nq
gfs_trans_begin_i
iinode_init_and_link
gfs_lock_nq_init
gfs_lock_nq_num
gfs_createi
gfs_create
vfs_create
open_namei
filp_open
__cond_resched
direct_strncpy_from_user
sys_open
sys_create
syscall_call
packet_rcv


Kernel panic - not syncing: GFS: fsid=cisco:gfs2.0: assertion "FALSE"
failed
GFS: fsid=cisco:gfs2.0:  function = check_seg_usage
GFS: fsid=cisco:gfs2.0:  file =
/download/gfs/cluster/gfs-kernel/src/gfs/log.c, line 590
GFS: fsid=cisco:gfs2.0:  time=1171047359

 
 
thanks,
Sridharan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20070213/b4475192/attachment.htm>