From: stress_buster <leo1783@yahoo.com>
To: xfs@oss.sgi.com
Subject: fs corruption
Date: Tue, 12 Apr 2011 02:33:07 -0700 (PDT) [thread overview]
Message-ID: <31377534.post@talk.nabble.com> (raw)
My dmesg output shows the below trace. It repeats over and over again.
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1545 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff881a8961
Call Trace:
[<ffffffff881a6e27>] :xfs:xfs_free_ag_extent+0x19e/0x67e
[<ffffffff881a8961>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff881d96cf>] :xfs:xlog_recover_process_efi+0x112/0x16c
[<ffffffff881f31b4>] :xfs:xfs_fs_fill_super+0x0/0x3e4
[<ffffffff881da8c2>] :xfs:xlog_recover_process_efis+0x4f/0x8d
[<ffffffff881da914>] :xfs:xlog_recover_finish+0x14/0xad
[<ffffffff881f31b4>] :xfs:xfs_fs_fill_super+0x0/0x3e4
[<ffffffff881df420>] :xfs:xfs_mountfs+0x498/0x5e2
[<ffffffff881dfb42>] :xfs:xfs_mru_cache_create+0x113/0x143
[<ffffffff881f33b7>] :xfs:xfs_fs_fill_super+0x203/0x3e4
[<ffffffff800e544f>] get_sb_bdev+0x10a/0x16c
[<ffffffff800e4dec>] vfs_kern_mount+0x93/0x11a
[<ffffffff800e4eb5>] do_kern_mount+0x36/0x4d
[<ffffffff800ef2ed>] do_mount+0x6a9/0x719
[<ffffffff80008d84>] __handle_mm_fault+0x5f2/0xfaa
[<ffffffff80022127>] __up_read+0x19/0x7f
[<ffffffff80067b88>] do_page_fault+0x4fe/0x874
[<ffffffff8012c580>] inode_doinit_with_dentry+0x86/0x47c
[<ffffffff800cd378>] zone_statistics+0x3e/0x6d
[<ffffffff8000f2ff>] __alloc_pages+0x78/0x308
[<ffffffff8004c9fd>] sys_mount+0x8a/0xcd
[<ffffffff8005e116>] system_call+0x7e/0x83
Failed to recover EFIs on filesystem: cciss/c0d0
XFS: log mount finish failed
Can someone shed some light on what is happening here?
Also what the next steps I need to take to repair the fs? (assuming my xfs
fs is corrupted)
Will running xfs_repair be good enough in this case?
Thanks in advance
--
View this message in context: http://old.nabble.com/fs-corruption-tp31377534p31377534.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-04-12 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 9:33 stress_buster [this message]
2011-04-12 9:49 ` fs corruption Dave Chinner
2011-04-12 10:51 ` Leo Davis
2011-04-12 11:05 ` Dave Chinner
2011-04-12 11:37 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2011-04-25 5:47 Leo Davis
2002-07-01 13:35 FS corruption Joakim Tjernlund
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=31377534.post@talk.nabble.com \
--to=leo1783@yahoo.com \
--cc=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.