From: Dave Chinner <david@fromorbit.com>
To: "Libor Klepáč" <libor.klepac@bcom.cz>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify
Date: Fri, 11 Nov 2016 08:30:57 +1100 [thread overview]
Message-ID: <20161110213057.GH28922@dastard> (raw)
In-Reply-To: <2152865.L3K5Xz7SXO@libor-nb>
On Thu, Nov 10, 2016 at 05:04:48PM +0100, Libor Klepáč wrote:
> On čtvrtek 10. listopadu 2016 16:29:15 CET Dave Chinner wrote:
> > Which:
> > > > Phase 3 - for each AG...
> > > >
> > > > - scan (but don't clear) agi unlinked lists...
> > > > - process known inodes and perform inode discovery...
> > > > - agno = 0
> > > > - agno = 1
> > > >
> > > > Metadata corruption detected at xfs_attr3_leaf block 0x12645ef8/0x1000
> > > > Metadata corruption detected at xfs_attr3_leaf block 0x12f63f40/0x1000
> >
> > These two blocks. It looks like repair didn't clean them up?
> >
> > Hmmmm - looking at the code I'm not sure that repair detects and
> > removes empty attr leaf blocks, which would explain why the error
> > showed up again.. Can you provide a metadump of the filesystem so we
> > can did into the exact neature of the problem you are seeing?
>
> Sure not a problem. How much time will it take giving xfs_repair took approx 40 minutes?
No longer than that, with agood possibility it will be much faster
as metadump only needs 1 pass over the metadata, not three...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-10 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 17:09 BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify Libor Klepáč
2016-10-21 17:59 ` Brian Foster
2016-10-21 22:20 ` Dave Chinner
2016-10-23 6:48 ` Libor Klepáč
2016-10-24 2:40 ` Dave Chinner
2016-10-25 6:52 ` Libor Klepáč
2016-10-31 8:54 ` Libor Klepáč
2016-10-31 11:57 ` Brian Foster
2016-10-31 12:02 ` Dave Chinner
2016-10-31 15:36 ` Libor Klepáč
2016-11-08 11:09 ` Libor Klepáč
2016-11-08 11:28 ` Libor Klepáč
2016-11-10 5:29 ` Dave Chinner
[not found] ` <2152865.L3K5Xz7SXO@libor-nb>
2016-11-10 21:30 ` Dave Chinner [this message]
2016-11-23 11:40 ` Libor Klepáč
2016-11-26 6:05 ` Eric Sandeen
2016-12-06 9:08 ` Libor Klepáč
-- strict thread matches above, loose matches on Subject: below --
2016-10-21 12:46 Libor Klepáč
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=20161110213057.GH28922@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=libor.klepac@bcom.cz \
--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).