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: Thu, 10 Nov 2016 16:29:15 +1100 [thread overview]
Message-ID: <20161110052915.GG28922@dastard> (raw)
In-Reply-To: <2639114.hBi4OJ80y2@libor-nb>
On Tue, Nov 08, 2016 at 12:28:54PM +0100, Libor Klepáč wrote:
> Adding more output from dmesg
>
> XFS (dm-2): Metadata corruption detected at xfs_attr3_leaf_read_verify+0x5a/0x100 [xfs], xfs_attr3_leaf block 0x12f63f40
> XFS (dm-2): Unmount and run xfs_repair
> XFS (dm-2): First 64 bytes of corrupted metadata buffer:
> ffff88018fe02000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 ................
> ffff88018fe02010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 ..... ..........
> ffff88018fe02020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> ffff88018fe02030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> XFS (dm-2): metadata I/O error: block 0x12f63f40 ("xfs_trans_read_buf_map") error 117 numblks 8
So, again, it is empty attribute blocks that are being tripped over
at blkno 0x12f63f40 and 0x12645ef8
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?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-10 5:29 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 [this message]
[not found] ` <2152865.L3K5Xz7SXO@libor-nb>
2016-11-10 21:30 ` Dave Chinner
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=20161110052915.GG28922@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 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.