linux-ext4 - [Bug 201685] ext4 file system corruption

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-201685-13602-QKgx1M949K@https.bugzilla.kernel.org/>
Date:   Sun, 02 Dec 2018 16:57:57 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption

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

Jukka Santala (donwulff@....fi) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |donwulff@....fi

--- Comment #150 from Jukka Santala (donwulff@....fi) ---
Whole block corrupted at once with each inode/file returning "Structure needs
cleaning" and bad extra_isizes in syslog while three hours in doing plain cp
-ax from ext4 to BTRFS mdraid in Ubuntu 18.04.1 mainline kernel 4.19.6 in init
level 1 (Ubuntu rescue mode with almost nothing else running).

Saved the corrupted block via debugfs, filesystem mounts read-only, dropped
disk caches and block is fine again with files accessible. Seeing if I can find
the corrupted block contents anywhere else in the filesystem. Error first
happened for me in 4.19.5 after running cleanly for days, now it comes
constantly.

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