page allocation failure on host with GFS2 file-systems mounted

Issue

A cluster node with a mounted GFS2 file-system is throwing page allocation failure errors:

Nov 18 03:46:37 node42 kernel: converting: page allocation failure. order:5, mode:0x50
Nov 18 03:46:37 node42 kernel: Pid: 32431, comm: converting Tainted: P           ---------------    2.6.32-358.14.1.el6.x86_64 #1
Nov 18 03:46:37 node42 kernel: Call Trace:
Nov 18 03:46:37 node42 kernel: [<ffffffff8112c197>] ? __alloc_pages_nodemask+0x757/0x8d0
Nov 18 03:46:37 node42 kernel: [<ffffffff81166b42>] ? kmem_getpages+0x62/0x170
Nov 18 03:46:37 node42 kernel: [<ffffffff8116775a>] ? fallback_alloc+0x1ba/0x270
Nov 18 03:46:37 node42 kernel: [<ffffffff811671af>] ? cache_grow+0x2cf/0x320
Nov 18 03:46:37 node42 kernel: [<ffffffff811674d9>] ? ____cache_alloc_node+0x99/0x160
Nov 18 03:46:37 node42 kernel: [<ffffffffa0688e6a>] ? gfs2_dir_get_hash_table+0x8a/0x3e0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffff811682a9>] ? __kmalloc+0x189/0x220
Nov 18 03:46:37 node42 kernel: [<ffffffffa0688bf0>] ? gfs2_dirent_find+0x0/0x60 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa0688e6a>] ? gfs2_dir_get_hash_table+0x8a/0x3e0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffff8150dd80>] ? thread_return+0x4e/0x76e
Nov 18 03:46:37 node42 kernel: [<ffffffff81096b87>] ? bit_waitqueue+0x17/0xd0
Nov 18 03:46:37 node42 kernel: [<ffffffffa0688bf0>] ? gfs2_dirent_find+0x0/0x60 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa06891e0>] ? get_leaf_nr+0x20/0x50 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa0689784>] ? get_first_leaf+0x24/0x50 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffff8118de63>] ? generic_permission+0x23/0xb0
Nov 18 03:46:37 node42 kernel: [<ffffffffa0689859>] ? gfs2_dirent_search+0xa9/0x1a0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa06a3a22>] ? gfs2_permission+0xc2/0x100 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa0689e5a>] ? gfs2_dir_search+0x2a/0x80 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa06978ce>] ? gfs2_lookupi+0xde/0x1e0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa069793d>] ? gfs2_lookupi+0x14d/0x1e0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffffa06a46d6>] ? gfs2_lookup+0x36/0xd0 [gfs2]
Nov 18 03:46:37 node42 kernel: [<ffffffff8119ae67>] ? d_alloc+0x137/0x1b0
Nov 18 03:46:37 node42 kernel: [<ffffffff811905a5>] ? do_lookup+0x1a5/0x230
Nov 18 03:46:37 node42 kernel: [<ffffffff81190d64>] ? __link_path_walk+0x734/0x1030
Nov 18 03:46:37 node42 kernel: [<ffffffff811438cd>] ? handle_pte_fault+0x2cd/0xb50
Nov 18 03:46:37 node42 kernel: [<ffffffff811918ea>] ? path_walk+0x6a/0xe0
Nov 18 03:46:37 node42 kernel: [<ffffffff81191abb>] ? do_path_lookup+0x5b/0xa0
Nov 18 03:46:37 node42 kernel: [<ffffffff81192747>] ? user_path_at+0x57/0xa0
Nov 18 03:46:37 node42 kernel: [<ffffffff810e6d45>] ? call_rcu_sched+0x15/0x20
Nov 18 03:46:37 node42 kernel: [<ffffffff810e6d5e>] ? call_rcu+0xe/0x10
Nov 18 03:46:37 node42 kernel: [<ffffffff8119944f>] ? d_free+0x3f/0x60
Nov 18 03:46:37 node42 kernel: [<ffffffff81186b3c>] ? vfs_fstatat+0x3c/0x80
Nov 18 03:46:37 node42 kernel: [<ffffffff81182971>] ? __fput+0x1a1/0x210
Nov 18 03:46:37 node42 kernel: [<ffffffff81186cab>] ? vfs_stat+0x1b/0x20
Nov 18 03:46:37 node42 kernel: [<ffffffff81186cd4>] ? sys_newstat+0x24/0x50
Nov 18 03:46:37 node42 kernel: [<ffffffff810dc867>] ? audit_syscall_entry+0x1d7/0x200
Nov 18 03:46:37 node42 kernel: [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b