From: Dave Chinner <david@fromorbit.com>
To: Julien Lutran <julien.lutran@corp.ovh.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: Unable to fix metadata corruption with xfs_repair
Date: Tue, 22 Jan 2019 07:31:33 +1100 [thread overview]
Message-ID: <20190121203133.GK6173@dastard> (raw)
In-Reply-To: <68A7E1A3-8AE1-4CD5-86E2-ABDD5F64D2CB@corp.ovh.com>
On Mon, Jan 21, 2019 at 03:36:11PM +0000, Julien Lutran wrote:
> Hello,
>
> I’m experiencing an issue with metadata corruption while trying to fix several corrupted xfs filesystems.
> Here’s an excerpt of the kernel messages when the disk is mounted :
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> […]
> Jan 21 15:44:16 rescue kernel: XFS (sdb): Metadata corruption detected at xfs_inode_buf_verify+0x6d/0xf0, xfs_inode block 0x300160
> Jan 21 15:44:16 rescue kernel: XFS (sdb): Unmount and run xfs_repair
> Jan 21 15:44:16 rescue kernel: XFS (sdb): First 64 bytes of corrupted metadata buffer:
> Jan 21 15:44:16 rescue kernel: XFS (sdb): metadata I/O error: block 0x300160 ("xfs_trans_read_buf_map") error 117 numblks 16
> Jan 21 15:44:16 rescue kernel: XFS (sdb): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
What's in the 64 bytes of the corrupted metadata buffer output?
i.e. you trimmed away the bit of the error message that we actually
need to see what went wrong. Can you paste the uneditted log of the
error, including the output from mount time from the filesystem?
> I tried to run a xfs_repair (see attached log) but it ends up the same way : metadata error on block 0x300160
> Is there a way to fix this corruption ?
Likely a repair bug - the inode cluster has been trashed for some
reason and it's not fixing it properly so it's refusing to write
back corrupt inode metadata.
I really need to see what was in the first 64 bytes of that buffer
and xfs_info output to determine if we have a corrupt cluster, a
corrupt filessystem block, or the hardware has returned a compeltely
zeroed sector....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-01-21 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 15:36 Unable to fix metadata corruption with xfs_repair Julien Lutran
2019-01-21 16:42 ` Eric Sandeen
2019-01-23 9:21 ` Julien Lutran
2019-01-24 13:07 ` Julien Lutran
2019-01-21 20:31 ` Dave Chinner [this message]
2019-01-23 9:33 ` Julien Lutran
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=20190121203133.GK6173@dastard \
--to=david@fromorbit.com \
--cc=julien.lutran@corp.ovh.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