Issue

• We were unable to start our splunk service, the following messages were found in the kernel logs.

kernel: XFS (dm-5): Internal error xfs_trans_cancel at line 984 of file fs/xfs/xfs_trans.c.  Caller xfs_rename+0x418/0x900 [xfs]
kernel: CPU: 12 PID: 18596 Comm: splunkd Not tainted 3.10.0-693.17.1.el7.x86_64 #1
kernel: Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
kernel: Call Trace:
kernel: [<ffffffff816a6071>] dump_stack+0x19/0x1b
kernel: [<ffffffffc057a4fb>] xfs_error_report+0x3b/0x40 [xfs]
kernel: [<ffffffffc058cd18>] ? xfs_rename+0x418/0x900 [xfs]
kernel: [<ffffffffc059695d>] xfs_trans_cancel+0xbd/0xe0 [xfs]
kernel: [<ffffffffc058cd18>] xfs_rename+0x418/0x900 [xfs]
kernel: [<ffffffff8120e448>] ? inode_permission+0x18/0x50
kernel: [<ffffffff81210311>] ? link_path_walk+0x81/0x8b0
kernel: [<ffffffffc0586ea0>] xfs_vn_rename+0xb0/0xf0 [xfs]
kernel: [<ffffffff81213890>] vfs_rename+0x5a0/0x930
kernel: [<ffffffffc0586df0>] ? xfs_vn_follow_link+0xa0/0xa0 [xfs]
kernel: [<ffffffff81214b93>] SYSC_renameat2+0x503/0x5a0
kernel: [<ffffffffc058955c>] ? xfs_iunlock+0xec/0x130 [xfs]
kernel: [<ffffffff812051de>] ? ____fput+0xe/0x10
kernel: [<ffffffff81215a7e>] SyS_renameat2+0xe/0x10
kernel: [<ffffffff81215abe>] SyS_rename+0x1e/0x20
kernel: [<ffffffff816b89fd>] system_call_fastpath+0x16/0x1b
kernel: XFS (dm-5): xfs_do_force_shutdown(0x8) called from line 985 of file fs/xfs/xfs_trans.c.  Return address = 0xffffffffc0596976
kernel: XFS (dm-5): Corruption of in-memory data detected.  Shutting down filesystem
kernel: XFS (dm-5): Please umount the filesystem and rectify the problem(s)