From: Dave Chinner <david@fromorbit.com>
To: Mike Grant <mggr@pml.ac.uk>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair segfault + debug info
Date: Sat, 30 May 2015 08:27:17 +1000 [thread overview]
Message-ID: <20150529222717.GB24666@dastard> (raw)
In-Reply-To: <556871CD.6090507@pml.ac.uk>
On Fri, May 29, 2015 at 03:03:57PM +0100, Mike Grant wrote:
> We recently had a 180TB XFS filesystem go down after following some
> ill-considered advice from a Dell tech (re-onlining a maybe-failed disk,
> which one might think was ok..). It's not irreplaceable data, but
> xfs_repair segfaults when trying to fix up and I thought that might be
> of interest here to help fix the segfault. We're not expecting to
> recover the data, though it would be nice.
>
> Partial logs & backtraces of xfs_repair runs using the latest Centos-7
> xfsprogs package and also run with the xfs_repair built from the git
> master, copies of core dumps and a metadump are at:
> https://rsg.pml.ac.uk/shared_files/mggr/xfs_segfault
Given it is choking on directory corruption repair, I'd strong
recommend trying the current git version (3.2.3-rc1) here:
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> Maximum memory use was only about 1GB by the time of the crash, and
> there was 120GB+ of swap available, so I don't think that was an issue.
> The command was "xfs_repair -v /dev/md0 -t 60 -P".
>
> Run time is about 2 hours to a crash and we'll probably want to wipe and
Probably because you turned off prefetch, which makes it *slow*. :P
I'd build the new xfsprogs, restore the metadump to a file on a
different machine, and then run the new xfs_repair binary on the
restored metadump image. That will tell you pretty quickly if the
problem is solved. If it is solved, then you can run the new
xfs_repair on the real server.
Just remember, though, that even once the FS has been repaired,
you'll still have to search for data corruption manually and deal
with that...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-05-29 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 14:03 xfs_repair segfault + debug info Mike Grant
2015-05-29 22:27 ` Dave Chinner [this message]
2015-06-01 7:32 ` Mike Grant
2015-06-12 18:49 ` [PATCH] " Mike Grant
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=20150529222717.GB24666@dastard \
--to=david@fromorbit.com \
--cc=mggr@pml.ac.uk \
--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