From: "Chris" <chris2014@postbox.xyz>
To: linux-xfs@vger.kernel.org
Cc: Brian Foster <bfoster@redhat.com>
Subject: Re: XFS_WANT_CORRUPTED_GOTO
Date: Mon, 14 Nov 2016 19:39:03 +0100 [thread overview]
Message-ID: <25b69ec53ba731ddd2f04d4e70341bdd.squirrel@mail2.postbox.xyz> (raw)
In-Reply-To: <20161114125654.GA37689@bfoster.bfoster>
Dear Brian,
thank you for your detailed answer.
Brian Foster wrote:
> On Sat, Nov 12, 2016 at 11:52:02AM +0100, Chris wrote:
>> I tried XFS-repair, but it couldn't find the first or second super block
>> after four hours.
>>
>
> That sounds like something more significant is going on either with the
> fs, the storage or xfs_repair has been pointed in the wrong place. The
> above issue should at worst require zeroing the log, dealing with the
> resulting inconsistency and rebuilding the fs btrees accurately.
Well, did it crash, because I called
xfs_db -c "freespc -s" /dev/...
while it was still in this unmount-loop?
> I suspect it's too late to inspect what's going on there if you have
> already restored from backup. In the future, you can use xfs_metadump to
> capture a metadata only image of a broken fs to share with us and help
> us diagnose what might have gone wrong.
OK.
> I'd suggest to run "xfs_repair -n" on those as soon as possible to see
> if they are affected by the same problem. It might also be a good idea
> to run it against the fs you've restored from backup to see if it
> returns and possibly get an idea on what might have caused the problem.
On those filesystems, that aren't in use now, xfs_repair hasn't found any
problems.
Thanks again for your help. Next time, I'll do a metadump.
- Chris
next prev parent reply other threads:[~2016-11-14 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 10:52 XFS_WANT_CORRUPTED_GOTO Chris
2016-11-14 12:56 ` XFS_WANT_CORRUPTED_GOTO Brian Foster
2016-11-14 18:39 ` Chris [this message]
2016-11-14 19:53 ` XFS_WANT_CORRUPTED_GOTO Brian Foster
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=25b69ec53ba731ddd2f04d4e70341bdd.squirrel@mail2.postbox.xyz \
--to=chris2014@postbox.xyz \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).