Reiser FS: The open source file system fallout

Yesterday, the Open Source community took an emotional hit when veteran Linux programmer Hans Reiser was convicted of first degree murder in the suspicious disappearing of his wife, Nina. While I won’t go into the details of the case, as this has been covered extensively in the press, I would like to talk a little bit about how this verdict will impact the technology in play for file system dominance in our favorite Open Source operating system, Linux.

While Namesys’ ReiserFS, of which Hans Reiser (right) was the primary programmer and lead designer was not the pre-dominant journaled file system used on Linux systems, it was praised for its stability and performance, and was and still is the default file system on the second most popular enterprise Linux distribution, SuSE Linux Enterprise Server (SLES). ReiserFS was also included in the “upstream” Linux kernel maintained by Linus Torvalds because it shares the same license, GPL version 2. ReiserFS is also popular on Debian-based systems as well.

SuSE and Debian use ReiserFS version 3, a stable and proven version of the code that has been sitting mostly fallow for some time, and is maintained with bug and security fixes on a best effort basis. Prior to the whirlwind and highly publicized trial, Hans Reiser and his small team were working on Reiser4, but much of this development ground to a halt due to his legal woes, and the project is more than likely to die an unfortunate death by virtue of its lead programmer having to serve a minimum 25 year life sentence in prison.

From the SuSE and Debian perspective, this is an obviously unacceptable state of affairs.

For now, the future of ReiserFS, and its parent company Namesys, remain in jeopardy. Reiser put the company up for sale in December 2006, and as of yet the company is unsold. Namesys employee Alexander Lyamin, writing in the Linux Kernel Mailing List in December 2006, said his company will continue its work absent of Reiser’s leadership, and attempt to appoint a “proxy” to run operations until a better solution could be found. At this time, Namesys’ website is current inaccessible.

The few prominent Linux distributions that were still shipping the stable version of ReiserFS by default have shifted to the more common Ext3 for various technical reasons. Reiser4, his next-generation filesystem, has been under active development for some time, but has not been streamlined into the Linux kernel because Linux developers claim that it fails to adhere to coding conventions and has several technical problems.

I don’t know if Hans Reiser, creator of the well-regarded, open-source ReiserFS (Reiser File System), is actually guilty of the murder of his estranged wife, Nina Reiser. We can’t actually even be sure that Nina Reiser was murdered. Her body was never found and Reiser’s attorney argued that she may have returned to her native Russia.

Never-the-less, as Wired reported, “with no body, no crime scene, no reliable eyewitness and virtually no physical evidence” Hans Reiser was found guilty of first-degree murder. In California, first-degree murder must be “willful, deliberate, and premeditated.”

Computer programmer Hans Reiser was arrogant while testifying in his murder trial and never showed any compassion for his estranged wife, one of many factors that led to his conviction on first-degree murder, a member of the jury said today.

If you look up the history of ReiserFS, you'll indirectly notice the politics goes a lot into those things.
Even if Hans never got convicted or if reiserfs development continues, Reiser4 will never get integrated into the mainline kernel.

So, Hans will have 25 years perhaps in prison with nothing to do but to perfect Reiser4 or v5. However, the problem is that Reiser file system is reaching a dead end. Only defragmentation technology can be picked up to be added in ReiserFS v5.

When an open source project loses one of its core people, it can be tough to pick up the pieces -- not just in terms of replacing that person's programming expertise or insight, but also to restore lost morale. On the plus side, the nature of an open source project does balance things out, if only in an opportunistic fashion.

Patches for the file system are still being submitted, as evinced by the traffic on the reiserfs-devel mailing list, and the folks at kernel.org have offered space to host the ReiserFS sources, giving it that much more of a lease on life. But without Reiser, I suspect ReiserFS itself is doomed -- or is at least due for a name change.

Does the survival and development of the Reiser FS really matter? With the stability of ext3, XFS, and JFS, and the promised scalability of the developing ext4 and Btrfs, neither Reiser3 or Reiser4 seem needed.

I'm certainly no expert on file systems, but I found a filesystem partitioning combo years ago that has been extremely reliable for me, which does not include a Reiser FS partition.

Reiser4 might have become a great Linux filesystem, but so might others.

Latest News

Security: Deloitte, Ransomware, Equifax, Denmark, and macOS 0-Day

Hackers [sic] are said to have accessed confidential emails and plans of Deloitte's blue-chip clients, along with usernames, passwords, IP addresses, architectural diagrams for businesses and health information.

Equifax's massive data breach has claimed another victim - Richard Smith, the company's CEO and Chairman of the Board. Equifax announced that Smith is retiring from his role at the company, effective Sept. 26.
"The cybersecurity incident has affected millions of consumers, and I have been completely dedicated to making this right," Smith stated. "At this critical juncture, I believe it is in the best interests of the company to have new leadership to move the company forward."
Equifax announced on Sept. 7 that it was the victim of a data breach the exposed personally identifiable information on 143 million Americans. The company initially reported that it first became aware of the breach on July 29, though subsequent reports have alleged that the company was breached as early as March.

Denmark’s Ministry of Finance is to finalise Denmark’s national strategy for cyber and information security. The ministry recently took over coordination of the plans, which previously were being prepared by the Ministry of Defence. The strategy is to be presented early next year, reports Denmark’s Agency for Digitisation (Digitaliseringsstyrelsen - DIGST).

There's a vulnerability in High Sierra and earlier versions of macOS that allows rogue applications to steal plaintext passwords stored in the Mac keychain, a security researcher said Monday. That's the same day the widely anticipated update was released.
The Mac keychain is a digital vault of sorts that stores passwords and cryptographic keys. Apple engineers have designed it so that installed applications can't access its contents without the user entering a master password. A weakness in the keychain, however, allows rogue apps to steal every plaintext password it stores with no password required. Patrick Wardle, a former National Security Agency hacker who now works for security firm Synack, posted a video demonstration here.

Facebook Licence-Patents Debacle

Thirty-five days after publicly stating, in response to objections from the Apache Software Foundation among others, that the company would not be re-licensing its React library, Facebook on Friday announced that it was re-licensing its React library. It was a surprising but welcome reversal for many in the industry, including Automattic’s Matt Mullenweg.
Ten days ago, Mullenweg published a piece that was at once understanding and blunt announcing that React would be excised from WordPress related projects. The problem was not Automattic – their general counsel saw little problem with the license – but given the breadth of WordPress’ distribution, the decision was made to remove the software because of the uncertainties surrounding its license. As bad as it was being banished from Apache Software Foundation projects, this was worse. Depending on whose numbers you use, WordPress can account for something close to one in four websites.
Given such extensive and escalating costs, the burden of proving the offsetting benefits to a patent clause required by virtually no one else in the industry presumably became too great, at which point the only rational decision would be to re-license the asset – difficult as such backtracking may have been.

Firefox Quantum

Earlier this year we wrote about Project Quantum, Mozilla's work to modernize Firefox and rebuild it to handle the needs of the modern Web.
Today, that work takes a big step toward the mainstream with the release of the new Firefox 57 developer edition. The old Firefox developer edition was based on the alpha-quality Aurora channel, which was two versions ahead of the stable version. In April, Mozilla scrapped the Aurora channel, and the developer edition moved to being based on the beta channel. The developer edition is used by a few hundred thousand users each month and is for the most part identical to the beta, except it has a different theme by default—a dark theme instead of the normal light one—and changes a few default settings in ways that developers tend to prefer.

Engines are important, both in cars and in browsers. That’s why we’re so revved up this morning – we’re releasing the Beta of a whole new Firefox, one that’s powered by a completely reinvented, modernized engine. Since the version number – 57 – can’t really convey the magnitude of the changes we’ve made, and how much faster this new Firefox is, we’re calling this upcoming release Firefox Quantum.