From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203943] ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails
Date: Fri, 21 Jun 2019 07:15:59 +0000 [thread overview]
Message-ID: <bug-203943-13602-Y41qbgmpqk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203943-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203943
Andreas Dilger (adilger.kernelbugzilla@dilger.ca) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adilger.kernelbugzilla@dilg
| |er.ca
--- Comment #1 from Andreas Dilger (adilger.kernelbugzilla@dilger.ca) ---
This seems like a RAID problem and not an ext4 problem. The RAID array
shouldn't be returning random garbage if one of the drives is unavailable.
Maybe it is not doing data parity verification on reads, so that it is blindly
returning bad blocks from the failed drive rather than reconstructing valid
data from parity if the drive does not fail completely?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-21 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:51 [Bug 203943] New: ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails bugzilla-daemon
2019-06-21 7:15 ` bugzilla-daemon [this message]
2019-06-21 12:40 ` [Bug 203943] " bugzilla-daemon
2019-06-21 14:52 ` bugzilla-daemon
2019-06-21 18:29 ` bugzilla-daemon
2019-06-21 19:34 ` bugzilla-daemon
2019-06-21 20:47 ` bugzilla-daemon
2019-06-22 7:48 ` bugzilla-daemon
2019-06-22 8:06 ` bugzilla-daemon
2025-10-31 1:33 ` 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-203943-13602-Y41qbgmpqk@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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