Bug 215731 - Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”
Summary: Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”
Status: RESOLVED INVALID
Alias: None
Product: File System
Classification: Unclassified
Component: XFS (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: FileSystem/XFS Default Virtual Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-23 08:24 UTC by Jack Xing
Modified: 2022-06-01 17:42 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.10.0-514.26.2.el7.x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Serial log (66.82 KB, application/octet-stream)
2022-03-23 08:24 UTC, Jack Xing
Details

Description Jack Xing 2022-03-23 08:24:43 UTC
Created attachment 300607 [details]
Serial log

We can't access device through SSH. Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”.


------------------------------------------------------
[5150496.250010] XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xe0 [xfs], xfs_inode block 0x1092340
[5150496.250011] XFS (dm-0): Unmount and run xfs_repair
[5150496.250011] XFS (dm-0): First 64 bytes of corrupted metadata buffer:
[5150496.250012] ffff8808fe6cc000: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250012] ffff8808fe6cc010: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250013] ffff8808fe6cc020: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250013] ffff8808fe6cc030: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250024] XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xe0 [xfs], xfs_inode block 0x1092340
[5150496.250067] XFS (dm-0): Unmount and run xfs_repair
[5150496.250067] XFS (dm-0): First 64 bytes of corrupted metadata buffer:
[5150496.250067] ffff8808fe6cc000: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250068] ffff8808fe6cc010: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250080] ffff8808fe6cc020: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250080] ffff8808fe6cc030: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250091] XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xe0 [xfs], xfs_inode block 0x1092340
[5150496.250094] XFS (dm-0): Unmount and run xfs_repair
[5150496.250094] XFS (dm-0): First 64 bytes of corrupted metadata buffer:
[5150496.250322] ffff8800360ea000: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250323] ffff8800360ea010: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250323] ffff8800360ea020: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250324] ffff8800360ea030: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250336] XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xe0 [xfs], xfs_inode block 0x1092340
[5150496.250343] XFS (dm-0): Unmount and run xfs_repair
[5150496.250344] XFS (dm-0): First 64 bytes of corrupted metadata buffer:
[5150496.250344] ffff8800360ea000: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250345] ffff8800360ea010: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250346] ffff8800360ea020: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250346] ffff8800360ea030: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250356] XFS (dm-0): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xe0 [xfs], xfs_inode block 0x1092340
[5150496.250361] XFS (dm-0): Unmount and run xfs_repair
[5150496.250361] XFS (dm-0): First 64 bytes of corrupted metadata buffer:
[5150496.250362] ffff8800360ea000: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250362] ffff8800360ea010: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250362] ffff8800360ea020: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
[5150496.250363] ffff8800360ea030: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00  ................
------------------
Comment 1 Christian Kujau 2022-03-23 21:02:20 UTC
This is the kernel bug tracker. What's the kernel bug here? From the log above it's unclear what lead to these corruptions. There should be messages preceding the above, maybe something is wrong with the underlying disk device.

According to the message one should "unmount and run xfs_repair" -- did you try that?[0]. Did it help?

For further assistance, maybe the mailing list[1] can be consulted, but the folks over there will possibly need more details also: which kernel version, what kind of file system setup, what happened before these errors, etc.

[0] Be sure to do have a (block level) backup before running xfs_repair.
[1] https://xfs.org/index.php/XFS_email_list_and_archives
Comment 2 Eric Sandeen 2022-06-01 17:42:22 UTC
Agreed, this is simply a report of corruption, and there is not nearly enough information to act on or triage.

Note You need to log in before you can comment on or make changes to this bug.