Why did a gfs2 withdraw "function = jhead_scan, file = fs/gfs2/recovery.c, line = 239"?

Issue

• Why did a gfs2 withdraw function = jhead_scan, file = fs/gfs2/recovery.c, line = 239?

Mar 10 04:04:44 node5 clvmd: Cluster LVM daemon started - connected to CMAN
Mar 10 04:04:44 node5 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "rh6cluster:mydata"
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: Joined cluster. Now mounting FS...
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: jid=0, already locked for use
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: jid=0: Looking at journal...
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: fatal: filesystem consistency error
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0:   inode = 4 25
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0:   function = jhead_scan, file = fs/gfs2/recovery.c, line = 239
Mar 10 04:04:44 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: about to withdraw this file system
Mar 10 04:04:45 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: telling LM to unmount
Mar 10 04:04:45 node5 gfs_controld[9245]: recovery_uevent mg not found mydata
Mar 10 04:04:45 node5 kernel: GFS2: fsid=rh6cluster:mydata.0: withdrawn
Mar 10 04:04:45 node5 kernel: Pid: 2760, comm: kslowd001 Not tainted 2.6.32-504.8.1.el6.x86_64 #1
Mar 10 04:04:45 node5 kernel: Call Trace:
Mar 10 04:04:45 node5 kernel: [<ffffffffa02ec9b8>] ? gfs2_lm_withdraw+0x128/0x160 [gfs2]
Mar 10 04:04:45 node5 kernel: [<ffffffffa02ecbcd>] ? gfs2_consist_inode_i+0x5d/0x60 [gfs2]
Mar 10 04:04:45 node5 kernel: [<ffffffffa02e3d20>] ? gfs2_find_jhead+0x120/0x170 [gfs2]
Mar 10 04:04:45 node5 kernel: [<ffffffffa02e3e71>] ? gfs2_recover_work+0x101/0x7b0 [gfs2]
Mar 10 04:04:45 node5 kernel: [<ffffffff81063bf3>] ? perf_event_task_sched_out+0x33/0x70
Mar 10 04:04:45 node5 kernel: [<ffffffff810096f0>] ? __switch_to+0xd0/0x320
Mar 10 04:04:45 node5 kernel: [<ffffffff815299de>] ? thread_return+0x4e/0x7d0
Mar 10 04:04:45 node5 kernel: [<ffffffff81117ef3>] ? slow_work_execute+0x233/0x310
Mar 10 04:04:45 node5 kernel: [<ffffffff81118127>] ? slow_work_thread+0x157/0x360
Mar 10 04:04:45 node5 kernel: [<ffffffff8109eb00>] ? autoremove_wake_function+0x0/0x40
Mar 10 04:04:45 node5 kernel: [<ffffffff81117fd0>] ? slow_work_thread+0x0/0x360
Mar 10 04:04:45 node5 kernel: [<ffffffff8109e66e>] ? kthread+0x9e/0xc0
Mar 10 04:04:45 node5 kernel: [<ffffffff8100c20a>] ? child_rip+0xa/0x20
Mar 10 04:04:45 node5 kernel: [<ffffffff8109e5d0>] ? kthread+0x0/0xc0
Mar 10 04:04:45 node5 kernel: [<ffffffff8100c200>] ? child_rip+0x0/0x20

• A gfs2 filesystem had a withdrawal after mounting the filesystem with lock_nolock.