From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215731] Serial port continuously outputs “XFS (dm-0): Metadata corruption detected”
Date: Wed, 23 Mar 2022 21:02:20 +0000 [thread overview]
Message-ID: <bug-215731-201763-HySy5GPMA7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215731-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215731
Christian Kujau (lists@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #1 from Christian Kujau (lists@nerdbynature.de) ---
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
--
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 prev parent reply other threads:[~2022-03-23 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 8:24 [Bug 215731] New: Serial port continuously outputs “XFS (dm-0): Metadata corruption detected” bugzilla-daemon
2022-03-23 21:02 ` bugzilla-daemon [this message]
2022-06-01 17:42 ` [Bug 215731] " 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-HySy5GPMA7@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