XFS ftw
Announcement
Collapse
No announcement yet.
Some Users Have Been Hitting EXT4 File-System Corruption On Linux 4.19
Collapse
X
-
I've experienced corruption on a few hundred files, when switching from multi-queue block deadline to mq-blk none. Might not be related to mq-blk, but it happened in the past 3 weeks. I have full backups, so it's not that bad. What's terrible is that most errors I only found because I keep checksum log audits. If someone doesn't, and got some corruption, they might never know it.
I've since re-migrated to btrfs, but hey, with my luck, that will get corrupted also. I actually switched from btrfs to ext4 because I was tired of unfixable problems btrfs would throw up every few months when running a scrub. Can't wait for bcachefs.
- Likes 1
Comment
-
I also experienced data corruption on the 4.19 kernel. At first I thought it was due to a faulty M.2 SSD, which I tried for a full day to flash to the latest firmware. Then giving up reinstalling Ubuntu on the second SSD in my laptop, without using the smaller M.2 SSD. After installation I updating to the latest kernel using ukuu I got the same io errors, having the root partition remounting as read-only during use. Switching back to 4.18 and everything is fine again. After these errors happened again on the second SSD I gathered it must be something other than a faulty SSD. Searched for kernel related corruption issues and found the lkml.org thread and later this one.
Comment
-
Originally posted by AndyChow View PostI've experienced corruption on a few hundred files, when switching from multi-queue block deadline to mq-blk none. Might not be related to mq-blk, but it happened in the past 3 weeks. I have full backups, so it's not that bad. What's terrible is that most errors I only found because I keep checksum log audits. If someone doesn't, and got some corruption, they might never know it.
I've since re-migrated to btrfs, but hey, with my luck, that will get corrupted also. I actually switched from btrfs to ext4 because I was tired of unfixable problems btrfs would throw up every few months when running a scrub. Can't wait for bcachefs.
A purely COW filesystem does not use a journal so may be more resiliant to the problem since none of the existing disk structures are modified at all, it can read the existing disk structures and write modified versions to new locations. This allows the old unmodified structures to be used for recovery. Not sure if btrfs actually can do this.Last edited by jpg44; 28 November 2018, 03:45 PM.
Comment
-
Originally posted by bitman View PostI tend to believe corruption really does come from outside of ext4 driver. 4.19 is a total wreck of a release. People report all kinds of problems. I myself was getting random freezes every few hours. I do not recall such a disastrous release.
Comment
-
Originally posted by Weasel View PostRolling Release must be so awesome to force this kind of breakage on you right?
I have a couple systems still using 4.14 LTS. On Manjaro, the kernel major/minor version isn't updated unless you specifically install the new version. Only point releases are automatically updated (i.e. 4.14.1 to 4.14.2).
Comment
-
Originally posted by ALRBP View PostAnd I was thinking that maybe switching back to EXT4 (+HW RAID/MDADM) was safer than keeping Btrfs (no RAID5/6)…
- Likes 1
Comment
Comment