From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215731] New: Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”
Date: Wed, 23 Mar 2022 08:24:43 +0000 [thread overview]
Message-ID: <bug-215731-201763@https.bugzilla.kernel.org/> (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: filesystem_xfs@kernel-bugs.kernel.org
Reporter: xqjcool@gmail.com
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 ................
------------------
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-03-23 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 8:24 bugzilla-daemon [this message]
2022-03-23 21:02 ` [Bug 215731] Serial port continuously outputs “XFS (dm-0): Metadata corruption detected” bugzilla-daemon
2022-06-01 17:42 ` bugzilla-daemon
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=bug-215731-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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