From: stress_buster <leo1783@yahoo.com>
To: linux-xfs@oss.sgi.com
Subject: corrupt inode
Date: Tue, 10 May 2011 22:22:00 -0700 (PDT) [thread overview]
Message-ID: <31591438.post@talk.nabble.com> (raw)
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
--
View this message in context: http://old.nabble.com/corrupt-inode-tp31591438p31591438.html
Sent from the linux-xfs mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-05-11 5:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31591438.post@talk.nabble.com \
--to=leo1783@yahoo.com \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.