Reiser4

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Reiser4
Developer Namesys
Full name Reiser4
Introduced 2004 (Linux)
Partition identifier

Apple_UNIX_SVR2 (Apple Partition Map)
0x83 (MBR)

Basic data partition (GPT)
Structures
Directory contents Dancing B*-tree
Limits
Max. file size 8 TiB on x86
Max. filename length 3976 bytes
Allowed characters in filenames All bytes except NULL and '/'
Features
Dates recorded modification (mtime), metadata change (ctime), access (atime)
Date range 64-bit timestamps[1]
Forks No
File system permissions Unix permissions
Transparent compression Yes
Transparent encryption No
Data deduplication No
Supported operating systems Linux

Reiser4 is a computer file system, successor to the ReiserFS file system, developed from scratch by Namesys and sponsored by DARPA as well as Linspire. Named after its former lead developer Hans Reiser, Reiser4 has a questionable future and no immediate plans for merging into the Linux kernel.

Features[edit]

Some of the goals of the Reiser4 file system are:

  • Different transaction models: Journalling, Write-Anywhere (Copy-on-Write), Hybrid transaction model
  • More efficient journaling through wandering logs
  • More efficient support of small files, in terms of disk space and speed through block suballocation
  • Liquid items (or virtual keys) - a special format of records in the storage tree, which completely resolves the problem of internal fragmentation
  • EOTTL (extents on the twig level) - fully balanced storage tree, meaning that all paths to objects are of equal length
  • Faster handling of directories with large numbers of files
  • Intelligent transparent compression (LZO, ZLIB)
  • Flexible plugin infrastructure, which makes the file system resistant to the problem of creeping featurism
  • Dynamically optimized disk-layout through allocate-on-flush (also called delayed allocation in XFS)
  • Delayed actions (tree balancing, compression, block allocation, local defragmentation)
  • R and D (Rare and Dense) caches, synchronized at commit time
  • Transactions support for user-defined integrity
  • Offline filesystem check

Some of the more advanced Reiser4 features (such as user-defined transactions) are also not available because of a lack of a VFS API for them.

At present Reiser4 lacks a few standard file system features, such as an online repacker (similar to the defragmentation utilities provided with other file systems). The creators of Reiser4 say they will implement these later, or sooner if someone pays them to do so.[2]

Performance[edit]

Reiser4 uses B*-trees in conjunction with the dancing tree balancing approach, in which underpopulated nodes will not be merged until a flush to disk except under memory pressure or when a transaction completes. Such a system also allows Reiser4 to create files and directories without having to waste time and space through fixed blocks.

As of 2004, synthetic benchmarks performed by Namesys in 2003 show that Reiser4 is 10 to 15 times faster than its most serious competitor ext3 working on files smaller than 1 KiB. Namesys's benchmarks suggest it is typically twice the performance of ext3 for general-purpose filesystem usage patterns.[3] Other benchmarks from 2006 show results of Reiser4 being slower on many operations.[4] Benchmarks conducted in 2012 with Linux Kernel version 3.5 show that Reiser4 is considerably slower in various tests compared to in-kernel filesystems EXT4, btrfs and XFS.[5]

Integration with Linux[edit]

As of 2013, Reiser4 has not yet been merged into the mainline Linux kernel and consequently is still not supported on many Linux distributions; however, its predecessor ReiserFS v3 has been widely adopted. Reiser4 is also available from Andrew Morton's -mm kernel sources, and from Zen patch set. Linux kernel developers claim that Reiser4 does not follow Linux coding standards,[6] but Hans Reiser suggested political reasons.[7] Latest released reiser4 kernel patches and tools can be downloaded from reiser4 project page at sourceforge.net: http://reiser4.sourceforge.net/

History of Reiser4[edit]

Hans Reiser was convicted of murder on April 28, 2008, leaving the future of Reiser4 uncertain. After his arrest, employees of Namesys assured they would continue to work and that the events would not slow down the software development in the immediate future. In order to afford increasing legal fees, Hans Reiser announced on December 21, 2006 that he was going to sell Namesys;[8] as of March 26, 2008, it had not been sold, although the website was unavailable. In January 2008, Edward Shishkin, an employee of and programmer for Namesys, was quoted in a CNET interview saying that "Commercial activity of Namesys has stopped." Shishkin and others continued the development of Reiser4,[9] making source code available from Shishkin's web site,[10] later relocated to kernel.org.[11] Since 2008, Namesys employees have received 100% of their sponsored funding from DARPA which is why Shishkin said 'commercial funding has stopped'.[12][13][14]

Future of Reiser4[edit]

Reiser4 development still continues,[15] delivering patches via kernel.org.[16]

In a mailing list post from July 2009, Edward Shishkin wrote that in the coming autumn, they would start exploring the opportunity of getting Reiser4 into the main Linux kernel.[17] In a November 2009 interview[18] with Phoronix he said he was going to publish a plug-in design document for independent expert review. He aimed for January 2011,[19] but as of 2013, and with the 3.0 branch of kernel in full development, Reiser4 has not yet been integrated into the mainline kernel.

See also[edit]

References[edit]

  1. ^ Documentation/filesystems/reiser4.txt from a reiser4-patched kernel source, "By default file in reiser4 have 64-bit timestamps."
  2. ^ Reiser, Hans (2004-09-16). "Re: Benchmark: ext3 vs reiser4 and effects of fragmentation.". Namesys, ReiserFS mailing list. Retrieved 2009-10-03. 
  3. ^ Hans Reiser (November 20, 2003). "Benchmarks Of ReiserFS Version 4". Namesys. Retrieved 2014-01-18. 
  4. ^ Justin Piszcz (January 2006). "Benchmarking Filesystems Part II". Retrieved 2006-04-23. 
  5. ^ Michael Larabel (October 15, 2012). "Reiser4 Benchmarked On Linux 3.5 Against EXT4, Btrfs, XFS, ReiserFS". Phoronix. Retrieved 2012-10-15. 
  6. ^ "Linux: Why Reiser4 Is Not in the Kernel". Kerneltrap. September 19, 2005. Archived from the original on 2007-04-23. 
  7. ^ Reiser, Hans (21 July 2006). "The "'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion". Retrieved 2008-03-01. 
  8. ^ "Murder Suspect Selling Namesys". Wired News. 2006-12-21. Retrieved 2006-12-30. 
  9. ^ Namesys vanishes, but ReiserFS project lives on. http://www.news.com/8301-13580_3-9851703-39.html CNet (January 16, 2008). Retrieved on 2008-01-26.
  10. ^ "Namesys things". Chichkin_i.zelnet.ru. Retrieved 2010-02-08. 
  11. ^ New location of Namesys software Linux Kernel Mailing List post, 2008-08-04
  12. ^ "Re: we got the DARPA grant to add views to Reiser4". Mail-archive.com. 2004-04-10. Retrieved 2010-02-08. 
  13. ^ https://bugzilla.redhat.com/show_bug.cgi?id=114785
  14. ^ "Reports - ext3 or ReiserFS? Hans Reiser Says Red Hat's Move Is Understandable - Red Hat's Decision is Conservative, Not Radical". LinuxPlanet. Retrieved 2010-02-08. 
  15. ^ ReiserFS Development Mailing List. Retrieved on 2009-04-11.
  16. ^ "Edward Shishkin's Kernel Space". Kernel.org. Retrieved 2010-02-08. 
  17. ^ "Edward Shishkin on Reiser4's status". Spinics.net. 2009-07-31. Retrieved 2010-02-08. 
  18. ^ "Reiser4 May Go For Mainline Inclusion In 2010". Phoronix.com. 2009-11-10. Retrieved 2010-02-08. 
  19. ^ Shishkin, Edward (17 Oct 2010). "Re: Mainline inclusion". Retrieved 2010-10-17. 

External links[edit]