Language Selection

English French German Italian Portuguese Spanish

Reiser FS: The open source file system fallout

Filed under
Reiser

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.

More Here




Also:

  • 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.

    "Misunderstood" programmer receives 25-to-life

  • 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.

    Hans Reiser is fscked: jury delivers guilty verdict

  • 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.”

    I don’t see it.

    Was Reiser really found Guilty of being a Hacker?

  • 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.

    Reiser juror: "Never showed sympathy" for Nina

ReiserFS

Isn't one of the PRIMARY arguments for OPEN SOURCE suposed to be that it's "Open"?

Since ALL of the source is available, why does the fact that one programmer will no longer be working on it, doom the project?

So much for the great benefit of having ALL the source to prevent being burned by orphaned/abandoned/obsolete projects.

Re: ReiserFS

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.

Re: Understanding ReiserFS is easy ? Sql, logs compressed files

atang1 wrote:
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.

I doubt they will give him a Linux desktop in jail lol.

A ReiserFS Without Hans Reiser

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.

More Here

And: Reiser to be sentenced in July

ReiserFS project death

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.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more