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
| ||
|
Date: Thu, 29 Nov 2018 22:38:21 +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 Michael Orlitzky (michael@...itzky.com) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael@...itzky.com --- Comment #74 from Michael Orlitzky (michael@...itzky.com) --- (In reply to Laurent Bonnaud from comment #67) > I am also experiencing ext4 corruptions with 4.19.x kernels. > > One way to trigger this bug that works almost every time on my system is to > backup the whole FS with BorgBackup using this command: > Ouch, me too. I've already been through two hard drives and a new SATA controller. I was just about to resign myself to replacing the whole PC. My system is an older AMD Phenom, with absolutely nothing fancy going on. Boring spinning disks, no RAID, and exactly the symptom above. After upgrading to 4.19.0 everything was fine for a week, and then Borg started reporting these errors. If I boot to a rescue CD and fsck, things go back to "normal," but then after a few more days I get corruption again. IIRC I skipped 4.19.1 but had the same problem with 4.19.2, and now again on 4.19.3. -- You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists