All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ricardo J. Barberis" <ricardo.barberis@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Brian Foster <bfoster@redhat.com>,
	Linux-XFS list <linux-xfs@vger.kernel.org>
Subject: Re: Metadata CRC error detected at xfs_dquot_buf_read_verify
Date: Fri, 8 Feb 2019 19:19:24 -0300	[thread overview]
Message-ID: <201902081919.24466.ricardo.barberis@gmail.com> (raw)
In-Reply-To: <201902081357.39265.ricardo.barberis@gmail.com>

El Viernes 08/02/2019 a las 13:57, Ricardo J. Barberis escribió:
> El Viernes 08/02/2019 a las 13:26, Darrick J. Wong escribió:
> > On Fri, Feb 08, 2019 at 12:49:24PM -0300, Ricardo J. Barberis wrote:
> > > El Viernes 08/02/2019 a las 10:17, Brian Foster escribió:
> > > > On Thu, Feb 07, 2019 at 01:09:38PM -0300, Ricardo J. Barberis wrote:
> [ ... ]
> > > > Does xfs_repair find and fix anything? Please show the associated repair
> > > > output.
> > > 
> > > Unfotunately I didn't save xfs_repair output, but I don't believe it fixed
> > > anything other than the log that first time.
> > 
> > Eric Sandeen amended xfs_repair in xfsprogs 4.17 to detect and zap
> > corrupt quota blocks.  I don't know what version of xfsprogs centos 7.6
> > ships with, but you might try running something newer?
> > 
> > (Run it with -n first to make sure repair identifies the corrupt dquot
> > blocks, as is customary...)
>  
> I can try to compile 4.17 (CentOS 7.6 has 4.5.0) and see if it helps

Indeed, 4.19 found the corruption:

Metadata corruption detected at 0x460184, xfs_dquot block 0x4170/0x1000
User quota: bad UUID for id 55197. Would correct.

And fixed it when ran without '-n':

Metadata corruption detected at 0x460184, xfs_dquot block 0x4170/0x1000
User quota: bad UUID for id 55197. Corrected.


After that, I mounted it and ran "xfs_quota -x -c 'report /home -b'" without issues.

Thanks!
-- 
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

      reply	other threads:[~2019-02-08 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 16:09 Metadata CRC error detected at xfs_dquot_buf_read_verify Ricardo J. Barberis
2019-02-08 13:17 ` Brian Foster
2019-02-08 15:49   ` Ricardo J. Barberis
2019-02-08 16:26     ` Darrick J. Wong
2019-02-08 16:57       ` Ricardo J. Barberis
2019-02-08 22:19         ` Ricardo J. Barberis [this message]

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=201902081919.24466.ricardo.barberis@gmail.com \
    --to=ricardo.barberis@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.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 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.