linux-ext4 - [Bug 203943] ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-203943-13602-Y41qbgmpqk@https.bugzilla.kernel.org/>
Date:   Fri, 21 Jun 2019 07:15:59 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 203943] ext4 corruption after RAID6 degraded; e2fsck skips
 block checks and fails

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

Andreas Dilger (adilger.kernelbugzilla@...ger.ca) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@...g
                   |                            |er.ca

--- Comment #1 from Andreas Dilger (adilger.kernelbugzilla@...ger.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.