Why Linux’s ext4 Filesystem Keeps Failing: A Deep Dive into Bugs and POSIX Pitfalls

Linus attacks ext4

If you follow the Linux kernel mailing list, you’ll notice Linus Torvalds recently vented his frustration at the ext4 file system, warning that recent changes could land ext4 on his "shit‑list" if problems arise.

POSIX, a strange standard

POSIX defines a minimal file‑system interface, leaving behavior after crashes largely unspecified, which means a Linux file system that loses all data after a crash can still be considered "POSIX‑compliant".

Filesystem black history

Research shows that over 40% of file‑system‑related patches in the Linux kernel are bug fixes, and roughly 40% of those bugs can cause data corruption. Studies using fuzzing tools like AFL and model‑checking tools like FiSC have uncovered numerous critical bugs in ext4, Btrfs, and other file systems.

Impact on application development

Many developers assume file‑system guarantees such as append‑atomicity, but ext4 and other file systems often violate these expectations, leading to data loss in applications like LevelDB.

Correct developer posture

Use mature databases instead of raw file I/O, prefer raw devices for storage systems, keep I/O models simple, design for failure at every step, employ fsync() before dependent operations, and add fault‑injection tests using tools like dm‑delay or dm‑flakey.

Conclusion

Linux file systems are far from flawless; ongoing research and testing continue to uncover bugs. Understanding their limitations and following robust development practices can mitigate data‑loss risks.