For those that haven't yet switched to Btrfs, ZFS On Linux, or running EXT4/XFS but holding out hope for Reiser4, this out-of-tree file-system code has been updated for Linux 4.9.
Reiser4 was released for Linux 4.9.0 last weekend but then a revised patch series came out three days ago to fix some problems with this port to 4.9. With the new Reiser4 patches built against Linux 4.9.1, all should be well if you want to use this experimental file-system on the newest Linux kernel.
While Linux 4.9 will be released in just a few weeks, the remaining Reiser4 file-system developers have just updated their code to support the Linux 4.8 stable kernel.
Reiser4 for Linux 4.8.0 is now available for those wanting to run this out-of-tree file-system on the current stable kernel. The Reiser4 kernel is now compatible with 4.8 and there is also a kernel oops fix when mounting forward-incompatible volumes, unneeded assertions were removed, some VFS changes were made, and there is now rename2 support.
Edward Shishkin, one of the last remaining Reiser4 developers and the one who has been leading this out-of-tree file-system the past few years, has implemented logical volumes support with support for mirrors (in effect, RAID 0) and failover support at the file-system level.
Shishkin quietly announced on Sunday, "Reiser4 will support logical (compound) volumes. For now we have implemented the simplest ones - mirrors. As a supplement to existing checksums it will provide a failover - an important feature, which will reduce number of cases when your volume needs to be repaired by fsck."
The Reiser4 file-system now has support for the latest stable Linux kernel series, Linux 4.7.
Released this morning by Edward Shishkin was the updated Reiser4 file-system driver patch that provides compatibility for Linux 4.7.0. The only other change besides porting over to Linux 4.7 is a small returned optimization.
There's been no talk in a few years about attempting to mainline the Reiser4 file-system in the Linux kernel. Thus for now if you want to try out this once-promising file-system, swing by SourceForge to patch your kernel.
In short: Novelist Stephen Elliott (James Franco) find himself drawn to the high-profile Hans Reiser (Christian Slater) murder trial - a case that brings him closer to his own troubled past with father (Ed Harris). Amber Heard, Wilmer Valderrama and Cynthia Nixon also star. (Watch the trailer)
While Romanowsky gamely tries to negotiate the same structural tricks as the book, which employed the Reiser case as a base camp from which the author could depart and return, in the film it feels more like a subplot despite the cinematic tricks -- the cross-cutting and slo-mo flashbacks -- that the director uses to try to connect the stories. At times it feels flat, other times risible, and only occasionally do the stories resonate in any kind of harmony.
Short version — I will continue to use “ext4” in future installs.
Note that this a personal view, not a recommendation. My own choice depends on how I use computers and my practices for backup, recovery, etc. Your practices are likely different. Much of this post will be about my considerations in deciding against “btrfs” for my own use.
The Reiser4 file-system has been updated with support for the Linux 4.5 kernel.
Edward Shishkin, the main Reiser4 developer left working on this out-of-tree file-system, today spun the Reiser4 patches for the Linux 4.5 kernel that also includes a few fixes/changes for satisfying the kernel and compiler. Aside from that, there's nothing new to report today with regard to new Reiser4 file-system features nor any new attempt to try to mainline this file-system code.
While Reiser4 doesn't still have any mainline Linux kernel ambitions until receiving any corporate backing, the notoriously known Linux file-system has been updated for Linux 3.16 compatibility and SSD discard support.
Over the weekend the Reiser4 file-system patches were updated for Linux 3.16.1/3.16.2 kernel support and additionally for presenting SSD discard support for the long-in-development Linux FS. This latest Reiser4 file-system work was done by Ivan Shapovalov and Edward Shishkin.
A recent announcement was made stating that the Reiser4 file system, successor to the ReiserFS, was ported to the 3.15 Linux kernel. Following the 2006 conviction and incarceration of the mastermind that original conceived this project (Hans Reiser), a few dedicated developers continued supporting this file system despite the odds stacked against them. In the last decade, the Linux kernel has seen newer file systems, most of which are integrated into the mainline kernel tree (i.e. btrfs, ext4, etc.). Reiser4 was rejected for inclusion some time back, and most of its developers moved on (one or more of which are currently working on btrfs).
While the Linux 3.16 kernel is now stable, a few days ago the Reiser4 file-system was finally ported to Linux 3.15.
Edward Shishkin released Reiser4 for the Linux 3.15.1 kernel last weekend. Besides being ported to the kernel interface changes for Linux 3.15, there's also two bug-fixes for the out-of-tree file-system. Most of the Reiser4 activity these days continues to just be porting to new kernel versions and bug-fixing. Edward is down to being one of the only main developers left and there's expected to be no effort to mainline the controversial file-system without the support of a major Linux ISV/IHV.
Ivan Shapovalov is back on track with his Reiser4 file-system contributions.
Shapovalov has been working on Reiser4 support for TRIM/Discard on SSDs. It's been some weeks since the last revision but the fourth version of the patches are now out there for this common file-system feature of being able to discard blocks by informing the solid-state drive about blocks that are no longer in use by the file-system. Most mainline Linux file-systems already support SSD discard, which is generally exposed via the discard mount option -- which is also the case for Reiser4.