Re: Unable to fix metadata corruption with xfs_repair

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

> On 21 Jan 2019, at 21:31, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> 
> 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?

Sorry, my bad. Here’s the full log :

Jan 23 09:43:36 rescue kernel: XFS (sdb): Metadata corruption detected at xfs_inode_buf_verify+0x6d/0xf0, xfs_inode block 0x300160
Jan 23 09:43:36 rescue kernel: XFS (sdb): Unmount and run xfs_repair
Jan 23 09:43:36 rescue kernel: XFS (sdb): First 64 bytes of corrupted metadata buffer:
Jan 23 09:43:36 rescue kernel: ffff998f8f33b000: 49 4e 41 ed 02 01 00 00 00 00 03 e7 00 00 03 e7  INA.............
Jan 23 09:43:36 rescue kernel: ffff998f8f33b010: 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 01  ................
Jan 23 09:43:36 rescue kernel: ffff998f8f33b020: 59 c8 26 66 34 15 44 a6 59 c8 26 68 04 66 94 c0  Y.&f4.D.Y.&h.f..
Jan 23 09:43:36 rescue kernel: ffff998f8f33b030: 59 c8 26 68 04 66 94 c0 00 00 00 00 00 00 00 2f  Y.&h.f........./
Jan 23 09:43:36 rescue kernel: XFS (sdb): metadata I/O error: block 0x300160 ("xfs_trans_read_buf_map") error 117 numblks 16
Jan 23 09:43:36 rescue kernel: XFS (sdb): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.

> 
>> 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@xxxxxxxxxxxxx

Attachment: signature.asc
Description: Message signed with OpenPGP


[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux