Tux3 File System Could Finally Make It Into the Mainline Linux Kernel

An anonymous reader writes "The Tux3 file-system that's been in development since 2008 as the public replacement to the patent-blocked Tux2 file-system is now under review for inclusion into the Linux kernel. Tux3 tries to act as a 'light, tight, modern file-system. We offer a fresh approach to some ancient problems,' according to its lead developer, Daniel Phillips. Tux3 strives for minimal resource consumption but lacks enterprise-grade reliability at this point. Tux3, at the end of the day, tries to be 'robust, fast, and simple' with the Linux FS reportedly being as fast as other well known file-systems. Details on the project are at Tux3.org."

Ambitious but not much has happened in 6 yrs

[haruchai]

and they expect to be competitive with ZFS?? They have a LOT of work to do.

parent delays

[KiloByte]

So tux2 was ready in 2000, and it took 14 years to rewrite it to avoid parents? Oh how much patents help innovation!

Re:Ambitious but not much has happened in 6 yrs

[Bengie]

It's a worthy goal to have. We need more competition in the FS sector. Many times competition is the inspiration for new features, even if some of these FS don't even make it off the ground. ZFS is great, but it's not perfect, and they only have so many resources to throw at new ideas to test. Monoculture is never a good thing.

Choice

[warrax_666]

Oh, please. A modern Linux distro actually needs to provide hotplug that actually works, a tear-free desktop experience, reliable service termination/startup/restarts, etc.

Stop living in the past.

Re:Ambitious but not much has happened in 6 yrs

[Bengie]

btrfs is interesting, but it's taking a long time to get anywhere and it has some big backers. I've also read some really well written blogs from sysadmins who have been Unix admins since the beginning of time, and they had some really good examples of some "Features" of btrfs that a sysadmin should never-ever use under any circumstance, and some features that are half-asses that are nearly a requirement for any good sysadmin, but cannot be done because of those other "bad" features.

One such example is btrfs allows a volume to be mounted under multiple parents. In order to handle this "awesome" feature, they had to give up the ability to atomically snapshot across volumes. In ZFS, if you mount a volume under another volume and snapshot the parent, the children will automatically be atomically included, not so with btrfs, that's an impossibility to add a feature that should never be used.