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-W8IXdDUfWA@https.bugzilla.kernel.org/>
Date:   Sat, 22 Jun 2019 07:48:47 +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

--- Comment #7 from Yann Ormanns (yann@...anns.net) ---
I changed the locale to en_GB and got now the actual 5 or 6 inodes, which
caused the extremely slow procedure of e2fsck. I zeroed them with debugfs and
afterwards, e2fsck was able to fix many, many errors.
lost+found contains 934G of data (53190 entries). During the next days, I will
try to examine them.

While copying files out of my backup, I re-tested a failure of a disk an
removed it from the array. After a while I re-added it and now the array is
rsyncing. I will watch the logs for possible FS errors - for now, all seems
clean.

Thanks a lot for your support!

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