From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify
Date: Wed, 23 Nov 2016 12:40:15 +0100 [thread overview]
Message-ID: <1673187.nXukm9ZPb1@libor-nb> (raw)
In-Reply-To: <20161110213057.GH28922@dastard>
Hello,
collegue of mine was trying metadump, but it segfaults :-(
# xfs_metadump -g /dev/vgDisk2/lvData /mnt/xfs_dump/vps2_metadump
Copied 2588032 of 5767488 inodes (1 of 3 AGs) Segmentation fault
He ran it twice, segfault occured on same place
dmesg says
Nov 23 05:04:42 vps2 kernel: [1294386.804427] xfs_db[25156]: segfault at fffffffffffffff0 ip 00007f6bd7bc567d sp 00007ffc1a2897b8 error 7 in libc-2.19.so[7f6bd7b40000+1a1000]
Nov 23 05:20:22 vps2 kernel: [1295327.311413] xfs_db[28241]: segfault at fffffffffffffff0 ip 00007f7b7426d67d sp 00007ffddefeb4f8 error 7 in libc-2.19.so[7f7b741e8000+1a1000]
Are you interested in this partial metadump? It has over 3GB decompressed.
I will keep it here for few days:
https://download.bcom.cz/vps2_metadump_20161123.xz
btw, it seems to contain strings from inside of files, is that normal?
It also contains strings from mail.log which is on another (ext4) filesystem.
Thanks,
Libor
> 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.
>
next prev parent reply other threads:[~2016-11-23 11:40 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
2016-11-23 11:40 ` Libor Klepáč [this message]
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=1673187.nXukm9ZPb1@libor-nb \
--to=libor.klepac@bcom.cz \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.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).