Skip to contentSkip to conversation

New: Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”

Bug 215731 [email protected] 1 participant 3 messages Mar 23, 2022 – Jun 1, 2022

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=215731

            Bug ID: 215731
           Summary: Serial port continuously outputs “XFS (dm-0): Metadata
                    corruption detected”
           Product: File System
           Version: 2.5
    Kernel Version: 3.10.0-514.26.2.el7.x86_64
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 300607
--> https://bugzilla.kernel.org/attachment.cgi?id=300607&action=edit
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 ................
------------------

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw

[Bug 215731] Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”

https://bugzilla.kernel.org/show_bug.cgi?id=215731

Christian Kujau ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Christian Kujau ([email protected]) --- 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

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#2 lore raw

[Bug 215731] Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=215731

Eric Sandeen ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]
         Resolution|---                         |INVALID

--- Comment #2 from Eric Sandeen ([email protected]) ---
Agreed, this is simply a report of corruption, and there is not nearly enough information to act on or triage.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.