corrupt inode

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

corrupt inode

stress_buster
I see the following traces in dmesg:

Filesystem "cciss/c0d0": corrupt inode 3758098465 (bad size 460626 for local inode).  Unmount and run xfs_repair.
00000000: 49 4e 41 c9 01 01 00 03 00 00 00 00 00 00 00 00  INAƉ............
Filesystem "cciss/c0d0": XFS internal error xfs_iformat(5) at line 419 of file fs/xfs/xfs_inode.c.  Caller 0xffffffff881d4026

Call Trace:
 [<ffffffff881d3c51>] :xfs:xfs_iformat+0xe6/0x3d7
 [<ffffffff881d4026>] :xfs:xfs_iread+0xe4/0x1ea
 [<ffffffff881d4026>] :xfs:xfs_iread+0xe4/0x1ea
 [<ffffffff881cf7e9>] :xfs:xfs_iget_core+0x2f2/0x563
 [<ffffffff800257ae>] alloc_inode+0xeb/0x192
 [<ffffffff881cfb2c>] :xfs:xfs_iget+0xd2/0x17a
 [<ffffffff881e6086>] :xfs:xfs_lookup+0x76/0xa8
 [<ffffffff8000d3e9>] dput+0x2c/0x114
 [<ffffffff881f124a>] :xfs:xfs_vn_lookup+0x3d/0x7b
 [<ffffffff8000cf46>] do_lookup+0xe5/0x1e6
 [<ffffffff8000a23c>] __link_path_walk+0xa01/0xf42
 [<ffffffff8000ea11>] link_path_walk+0x42/0xb2
 [<ffffffff8000cce1>] do_path_lookup+0x275/0x2f1
 [<ffffffff8001283d>] getname+0x15b/0x1c2
 [<ffffffff800238c3>] __user_walk_fd+0x37/0x4c
 [<ffffffff8002889d>] vfs_stat_fd+0x1b/0x4a
 [<ffffffff800235f5>] sys_newstat+0x19/0x31
 [<ffffffff8005e116>] system_call+0x7e/0x83

Filesystem "cciss/c0d0": XFS internal error xfs_iformat(7) at line 440 of file fs/xfs/xfs_inode.c.  Caller 0xffffffff881d4026

Call Trace:
 [<ffffffff881d3e5a>] :xfs:xfs_iformat+0x2ef/0x3d7
 [<ffffffff881d4026>] :xfs:xfs_iread+0xe4/0x1ea
 [<ffffffff881cf7e9>] :xfs:xfs_iget_core+0x2f2/0x563
 [<ffffffff800257ae>] alloc_inode+0xeb/0x192
 [<ffffffff881cfb2c>] :xfs:xfs_iget+0xd2/0x17a
 [<ffffffff881e6086>] :xfs:xfs_lookup+0x76/0xa8
 [<ffffffff8000d3e9>] dput+0x2c/0x114
 [<ffffffff881f124a>] :xfs:xfs_vn_lookup+0x3d/0x7b
 [<ffffffff8000cf46>] do_lookup+0xe5/0x1e6
 [<ffffffff8000a23c>] __link_path_walk+0xa01/0xf42
 [<ffffffff8000ea11>] link_path_walk+0x42/0xb2
 [<ffffffff8000cce1>] do_path_lookup+0x275/0x2f1
 [<ffffffff8001283d>] getname+0x15b/0x1c2
 [<ffffffff800238c3>] __user_walk_fd+0x37/0x4c
 [<ffffffff8002889d>] vfs_stat_fd+0x1b/0x4a
 [<ffffffff800235f5>] sys_newstat+0x19/0x31
 [<ffffffff8005e116>] system_call+0x7e/0x83

I'm losing connectivity to iscsi targets randomly . This maybe unrelated to the fs errors though.

Any thoughts on what the above backtraces are pointing to?

Thanks in advance