A gfs2 filesystem had a withdraw "function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 437" on RHEL 7

Issue

A gfs2 filesystem had a withdrawal on a gfs2 filesystem:

Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1: fatal: invalid metadata block
Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1:   bh = 151977123 (magic number)
Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1:   function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 437
Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1: about to withdraw this file system
Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1: telling LM to unmount
Mar  2 15:09:44 node42 kernel: GFS2: fsid=mycluster:gfs.1: withdrawn
Mar  2 15:09:44 node42 kernel: CPU: 51 PID: 44275 Comm: simstrategy Tainted: G           OE  ------------   3.10.0-514.el7.x86_64 #1
Mar  2 15:09:44 node42 kernel: Hardware name: Dell Inc. PowerEdge M910/003R1K, BIOS 2.2.3 04/05/2011
Mar  2 15:09:44 node42 kernel: ffff8810fce6e000 00000000ac7113b5 ffff882059a3b9e8 ffffffff81685eac
Mar  2 15:09:44 node42 kernel: ffff882059a3ba60 ffffffffa0809c56 0000000000000030 ffff882059a3ba90
Mar  2 15:09:44 node42 kernel: ffff882059a3ba18 00000000ac7113b5 ffff882059a3baa8 ffff882059a3ba30
Mar  2 15:09:44 node42 kernel: Call Trace:
Mar  2 15:09:44 node42 kernel: [<ffffffff81685eac>] dump_stack+0x19/0x1b
Mar  2 15:09:44 node42 kernel: [<ffffffffa0809c56>] gfs2_lm_withdraw+0x146/0x180 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffffa0809f45>] gfs2_meta_check_ii+0x45/0x50 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffffa07f1419>] gfs2_meta_indirect_buffer+0xe9/0x150 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffffa0807c7d>] gfs2_dirty_inode+0x11d/0x250 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffffa0807c38>] ? gfs2_dirty_inode+0xd8/0x250 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffff81228dba>] __mark_inode_dirty+0xca/0x290
Mar  2 15:09:44 node42 kernel: [<ffffffff81219981>] update_time+0x81/0xd0
Mar  2 15:09:44 node42 kernel: [<ffffffff81219bd0>] file_update_time+0xa0/0xf0
Mar  2 15:09:44 node42 kernel: [<ffffffff81182a88>] __generic_file_aio_write+0x198/0x400
Mar  2 15:09:44 node42 kernel: [<ffffffff81182d49>] generic_file_aio_write+0x59/0xa0
Mar  2 15:09:44 node42 kernel: [<ffffffffa07f4500>] gfs2_file_aio_write+0xd0/0x160 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffff81183105>] ? filemap_fault+0x215/0x410
Mar  2 15:09:44 node42 kernel: [<ffffffff811fd979>] do_sync_readv_writev+0x79/0xd0
Mar  2 15:09:44 node42 kernel: [<ffffffff811ff01e>] do_readv_writev+0xce/0x260
Mar  2 15:09:44 node42 kernel: [<ffffffffa07f4430>] ? gfs2_release+0x50/0x50 [gfs2]
Mar  2 15:09:44 node42 kernel: [<ffffffff811fd830>] ? do_sync_read+0xd0/0xd0
Mar  2 15:09:44 node42 kernel: [<ffffffff816919b1>] ? __do_page_fault+0x171/0x450
Mar  2 15:09:44 node42 kernel: [<ffffffff811ff245>] vfs_writev+0x35/0x60
Mar  2 15:09:44 node42 kernel: [<ffffffff811ff3ff>] SyS_writev+0x7f/0x110
Mar  2 15:09:44 node42 kernel: [<ffffffff816964c9>] system_call_fastpath+0x16/0x1b