From: katmai <katmai@keptprivate.com>
To: xfs@oss.sgi.com
Subject: xfs corrupted
Date: Tue, 15 Oct 2013 01:41:47 -0700 (PDT) [thread overview]
Message-ID: <1381826507281-35009.post@n7.nabble.com> (raw)
i guys,
i have a problem. yesterday there was a power outage at one of my
datacenters, where i have a relatively large fileserver. 2 arrays, 1 x 14 tb
and 1 x 18 tb both in raid6, with an adaptec card.
after the outage, the server came back online, the xfs partitions were
mounted, and everything looked okay. i could access the data and everything
seemed just fine.
today i woke up to lots of i/o errors, and when i rebooted the server, the
partitions would not mount:
Oct 14 04:09:17 kp4 kernel:
Oct 14 04:09:17 kp4 kernel: XFS internal error XFS_WANT_CORRUPTED_RETURN
a<ffffffff80056933>] pdflush+0x0/0x1fb
Oct 14 04:09:17 kp4 kernel: [<ffffffff80056a84>] pdflush+0x151/0x1fb
Oct 14 04:09:17 kp4 kernel: [<ffffffff800cd931>] wb_kupdate+0x0/0x16a
Oct 14 04:09:17 kp4 kernel: [<ffffffff80032c2b>] kthread+0xfe/0x132
Oct 14 04:09:17 kp4 kernel: [<ffffffff8005dfc1>] child_rip+0xa/0x11
Oct 14 04:09:17 kp4 kernel: [<ffffffff800a3ab7>]
keventd_create_kthread+0x0/0xc4
Oct 14 04:09:17 kp4 kernel: [<ffffffff80032b2d>] kthread+0x0/0x132
Oct 14 04:09:17 kp4 kernel: [<ffffffff8005dfb7>] child_rip+0x0/0x11
Oct 14 04:09:17 kp4 kernel:
Oct 14 04:09:17 kp4 kernel: XFS internal error XFS_WANT_CORRUPTED_RETURN at
line 279 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff88342331
Oct 14 04:09:17 kp4 kernel:
got a bunch of these in dmesg.
i googled for solutions and i think i jumped the horse by doing xfs_repair
-L /dev/sdc. it would not clean it with xfs_repair /dev/sdc, and everybody
pretty much says the same thing.
this is what i was getting when trying to mount the array.
Filesystem Corruption of in-memory data detected. Shutting down filesystem
xfs_check
Did i jump the gun by using the -L switch :/ ?
--
View this message in context: http://xfs.9218.n7.nabble.com/xfs-corrupted-tp35009.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:[~2013-10-15 8:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 8:41 katmai [this message]
2013-10-15 18:34 ` xfs corrupted Emmanuel Florac
2013-10-15 18:45 ` Stefanita Rares Dumitrescu
2013-10-15 19:07 ` Chris Murphy
2013-10-15 19:52 ` Emmanuel Florac
2013-10-15 19:34 ` Emmanuel Florac
2013-10-15 19:57 ` Stefanita Rares Dumitrescu
2013-10-15 20:05 ` Emmanuel Florac
2013-10-15 20:17 ` Stefanita Rares Dumitrescu
2013-10-15 20:18 ` Stefanita Rares Dumitrescu
2013-10-15 20:26 ` Dave Chinner
2013-10-16 12:23 ` Stefanita Rares Dumitrescu
2013-10-16 13:32 ` Stefanita Rares Dumitrescu
2013-10-16 17:33 ` Keith Keller
2013-10-16 22:16 ` Dave Chinner
2013-10-16 14:32 ` Stefanita Rares Dumitrescu
2013-10-16 20:52 ` Stefanita Rares Dumitrescu
2013-10-17 18:04 ` Stefanita Rares Dumitrescu
2013-10-15 20:02 ` Stefanita Rares Dumitrescu
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=1381826507281-35009.post@n7.nabble.com \
--to=katmai@keptprivate.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox