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-YMs04YG4Er@https.bugzilla.kernel.org/>
Date:   Thu, 22 Nov 2018 11:51:56 +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

Henrique Rodrigues (henrique.rodrigues@....utl.pt) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |henrique.rodrigues@....utl.
                   |                            |pt

--- Comment #30 from Henrique Rodrigues (henrique.rodrigues@....utl.pt) ---
(In reply to Theodore Tso from comment #23)
> So from a personally very selfish perspective, I'm hoping someone who has
> already suffered corruption problems is willing to try either 4.19.3, or
> disabling CONFIG_SCSI_MQ_DEFAULT, or both, and report that they are no
> longer seeing problems, than my putting my own personal data at risk....

On a Ubuntu 18.10 machine I've upgraded to 4.19.0 and started getting these
corruption errors. Yesterday I've upgraded to 4.19.3 and was still getting
corrupted. 4.18 was fine. Unfortunately the latest corruption rendered the
operating system unbootable. I'm going to try and fix it tonight and then will
try to disable CONFIG_SCSI_MQ_DEFAULT and test.

I'm in a somewhat fortunate position since the data that I care about lives on
another disk with a different filesystem type, so the corruption on the root
filesystem is just annoying and not really that dangerous.

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