1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Talk Of "EXT5" File-System; Should EXT4 Be Frozen?

Linux Kernel

Published on 25 October 2012 03:23 PM EDT
Written by Michael Larabel in Linux Kernel
9 Comments

In the discussion that followed when it was found a nasty EXT4 file-system corruption bug hit recent Linux kernel stable releases, one user proposed that EXT4 be put in a feature-freeze mode and future work then be put towards an "EXT5" file-system, to which Ted Ts'o did respond.

In the Phoronix Forums discussion about the EXT4 corruption bug hitting the Linux 3.4/3.5/3.6 kernels, Ted Ts'o, the EXT4 file-system maintainer, ultimately jumped in on the discussion to respond to the numerous and polarized opinions of Phoronix readers.

One Phoronix reader suggested, "Maybe consider freezing all changes to Ext4 and make a new Ext5 for new ideas." Ted's response to this was:
We have considered this. Right now new features get added under experimental feature flags or mount options. One of the users who ran into problems were using experimental new features that are not enabled by default. We can't stop users from trying out new features that aren't enabled by default, just as we can't stop them from deciding to use ext5 instead of ext4 on production servers. Things like metadata checksums are not enabled by default specifically because they aren't ready yet. Brave users who try them out are invaluable, and I am grateful to people who help us do our testing, since that's the only way we can shake out the last bugs that aren't found in developer environments or via regression tests. But you make your choices, and take your chances when you turn on such experimental features.

And there are some real costs with forking the code base and creating a potential new "ext5". We already have had problems where bugs are fixed in ext4, and they aren't propagated to ext3. Just today I found a minor bug which was fixed in ext3, but not in ext2. And sometimes bugs are fixed in extN, but someone forgets to forward port the bug fix to extN+1. If we were to add an "ext5" it would make this problem much worse, since it would triple the potential ways that bug fixes might fail to get propagated to where they are needed.

Speaking of bug fixes, you can't freeze all changes, because we are still finding bugs. Heck, as part of deploying ext4 is deployed on thousands and thousands of thousands of machines in Google data centers, we found a bug that only showed up because we had deployed ext4 in great numbers. When we found the bug fix, I checked and found that the exact same bug existed in ext3, where it had not been found despite ten years of testing in enterprise linux releases, by companies such as IBM and Red Hat. (It had probably triggered a couple of times, but it was so rare that testers probably chalked it up to random hardware failure or cosmic rays; it was only because I was correlating failure reports --- and most were caused by hardware failures, not by software bugs --- across a very large number of machines that I could discern the pattern and find this particular bug.)

The problem is that sometimes bug fixes introduce other bugs. In this particular case, it was a bug fix which as backported to a stable kernel which apparently made this failure mode happen more often. If you really mean "freeze all changes", as opposed to just being full of snark, then that would also mean not taking any bug fixes. And if you want to stay on an older version of Linux, feel free..... that's what people who are using RHEL 5, or RHEL 4, or even in some cases RHAS 2.1 have chosen.
It's probably unlikely that we will see any EXT5 file-system for Linux anytime soon. Ted has also made some other file-system comments in this forum thread.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Intel Xeon E5-1680 v3 & E5-2687W v3 Compared To The Core i7 5960X On Linux
  2. Intel 120GB 530 Series SSD Linux Performance
  3. Btrfs/EXT4/XFS/F2FS RAID 0/1/5/6/10 Linux Benchmarks On Four SSDs
  4. AMD's Windows Catalyst Driver Remains Largely Faster Than Linux Drivers
Latest Linux Articles
  1. Apple OS X 10.10 vs. Ubuntu 14.10 Performance
  2. Mesa 10.5-devel Brings Some Intel Haswell HD Graphics Changes Over Mesa 10.3
  3. NVIDIA vs. Nouveau Drivers With Linux 3.18 + Mesa 10.4-devel
  4. Is The Open-Source NVIDIA Driver Fast Enough For Steam On Linux Gaming?
Latest Linux News
  1. Meizu's Ubuntu Phone Not Expected Until Early Next Year
  2. DragonFlyBSD 4.0 Drops i386 Support, Improves Graphics
  3. Expensive "Free/Libre Software Laptop" Uses A NVIDIA GPU
  4. QEMU 2.2-rc3 Released, Final Release Pushed Back By Couple Days
  5. 64-bit ARM FreeBSD Support Is Taking Shape
  6. GCW Zero Starts Seeing New Game Releases
  7. Intel's Cherry Trail Delayed To Next Year
  8. Bq Introduces More Android Devices, But Still No Ubuntu Phones
  9. Qt 5.4 Release Candidate Expected Later This Week
  10. ArrayFire Accelerated Compute Library Open-Sourced
Latest Forum Discussions
  1. Updated and Optimized Ubuntu Free Graphics Drivers
  2. Hurrican SDL Port
  3. Roadmap to Catalyst 14.10 ?
  4. how to configure module phoromatic ?
  5. PulseAudio 6.0 Is Coming & Other Linux Audio Plans For The Future
  6. Debian Developer Resigns From The Systemd Maintainership Team
  7. Cant get working Kaveri APU - A10-7850k
  8. Script for Fan Speed Control