From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: "Libor Klepáč" <libor.klepac@bcom.cz>, linux-xfs@vger.kernel.org
Subject: Re: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify
Date: Sat, 22 Oct 2016 09:20:05 +1100 [thread overview]
Message-ID: <20161021222005.GU23194@dastard> (raw)
In-Reply-To: <20161021175912.GB54851@bfoster.bfoster>
On Fri, Oct 21, 2016 at 01:59:13PM -0400, Brian Foster wrote:
> On Fri, Oct 21, 2016 at 07:09:06PM +0200, Libor Klepáč wrote:
> > Hello,
> > sorry for last incomplete email (if it arrives), i hit some send button by accident.
> >
> > Last week we have started to have problems with one virtual machine running debian jessie, with kernel 3.16.7-ckt20-1+deb8u4.
> > virtualization is done on vmware 5.5 on dell r610, disks are on perc h700.
> >
> > XFS is on data disk (/dev/mapper/vgDisk2-lvData) running cyrus, mysql, apache+php.
> > It resides on single disk LVM, without partitions.
> > #pvs
> > PV VG Fmt Attr PSize PFree
> > /dev/sda2 vgDisk1 lvm2 a-- 15.76g 0
> > /dev/sdb vgDisk2 lvm2 a-- 410.00g 0
> >
> > #lvs
> > LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
> > lvSwap vgDisk1 -wi-ao---- 1.86g
> > lvSystem vgDisk1 -wi-ao---- 13.90g
> > lvData vgDisk2 -wi-ao---- 410.00g
> >
> > #grep xfs /etc/fstab
> > /dev/mapper/vgDisk2-lvData /mountpoint xfs noatime,logbufs=8 0 1
> >
> > It was created in Debian Squeeze on kernel 2.6.32 OR Wheezy on 3.2.0.
> >
> >
> > There are some logs, this one repeats but doesn't cause shutdown
> >
> > Oct 14 07:02:58 vps2 kernel: [18855093.206725] XFS (dm-2): Metadata corruption detected at xfs_attr3_leaf_read_verify+0x46/0xd0 [xfs], block 0x24c17ba8
> > Oct 14 07:02:58 vps2 kernel: [18855093.210393] XFS (dm-2): Unmount and run xfs_repair
> > Oct 14 07:02:58 vps2 kernel: [18855093.211224] XFS (dm-2): First 64 bytes of corrupted metadata buffer:
> > Oct 14 07:02:58 vps2 kernel: [18855093.212092] ffff8801853da000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 ................
> > Oct 14 07:02:58 vps2 kernel: [18855093.213932] ffff8801853da010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 ..... ..........
> > Oct 14 07:02:58 vps2 kernel: [18855093.215915] ffff8801853da020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > Oct 14 07:02:58 vps2 kernel: [18855093.218054] ffff8801853da030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ffff8801853da000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 ................
| forw | back |magic| pad |count|usedbytes
ffff8801853da010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 ..... ..........
firstused|hl|pd|base0|size0|base1|size1|base2|size2|
ffff8801853da020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
entry data....
ffff8801853da030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Ok, that's a completely empty attribute leaf block. It's got no
attribute entries in it, and because the entry data is zero, it's
never had any data in it. It's failing the verifier because the
entry count in the header is zero. i.e. this sort of empty buffer
should never end up on disk.
This rings a bell, but I can't put my finger on it right now. It may
be a really old corruption that has been sitting on disk for a long
time (i.e. from whatever kernel the fs was originally created and
run on) that is only manifest now on a more recent kernel that has
better validity checking...
> > Is there some way to stop this? Maybe upgrading to kernel 4.7 from backports?
> > Is there a way to map those "block 0x12f4ca30" , "block 0x24c17ba8" to a specific file?
> >
>
> v3.16 is certainly kind of old. For starters though, I would suggest to
> grab the most recent xfsprogs release you can (you can even grab the
> source and run it right out of the build tree), run 'xfs_repair -n' and
> report the results.
This, please, and paste the output for us to see. If repair is not
detecting and correcting the corrupt attribute block you'll continue
to see the problem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-10-21 22:20 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 [this message]
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áč
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=20161021222005.GU23194@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).