Misplaced Pages

Reiser4: Difference between revisions

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 12:19, 6 January 2017 edit89.204.135.161 (talk) Features← Previous edit Revision as of 23:32, 7 January 2017 edit undo89.204.130.34 (talk) Update features listNext edit →
Line 34: Line 34:
Some of the goals of the Reiser4 file system are: Some of the goals of the Reiser4 file system are:


* Atomicity (filesystem operations either entirely occur, or they entirely don't, and they don't corrupt due to half occuring)
* Different transaction models: Journaling, Write-Anywhere (Copy-on-Write), Hybrid transaction model<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/Reiser4_transaction_models |title=Reiser4 transaction models |work=Reiser4 wiki }}</ref>Mirrors and failover<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/Reiser4_Mirrors_and_Failover |title=Reiser4 Mirrors and Failover |work=Reiser4 wiki }}</ref> * Different transaction models: Journaling, Write-Anywhere (Copy-on-Write), Hybrid transaction model<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/Reiser4_transaction_models |title=Reiser4 transaction models |work=Reiser4 wiki }}</ref>Mirrors and failover<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/Reiser4_Mirrors_and_Failover |title=Reiser4 Mirrors and Failover |work=Reiser4 wiki }}</ref>
* More efficient ] through wandering logs * More efficient ] through wandering logs

Revision as of 23:32, 7 January 2017

This article's lead section may be too short to adequately summarize the key points. Please consider expanding the lead to provide an accessible overview of all important aspects of the article. (February 2010)
Reiser4
Developer(s)Namesys
Full nameReiser4
Introduced2004 with Linux
Partition IDsApple_UNIX_SVR2 (Apple Partition Map)

0x83 (MBR)

Basic data partition (GPT)
Structures
Directory contentsDancing B*-tree
Limits
Max file size8 TiB on x86
Max filename length3976 bytes
Allowed filename
characters
All bytes except NULL and '/'
Features
Dates recordedmodification (mtime), metadata change (ctime), access (atime)
Date range64-bit timestamps
ForksNo
File system
permissions
Unix permissions
Transparent
compression
Yes
Transparent
encryption
No
Data deduplicationNo
Other
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. Reiser4 was named after its former lead developer Hans Reiser. As of 2016, the Reiser4 patch set is still being maintained, but according to Phoronix, it's unlikely to be merged into mainline Linux without corporate backing.

Features

Some of the goals of the Reiser4 file system are:

  • Atomicity (filesystem operations either entirely occur, or they entirely don't, and they don't corrupt due to half occuring)
  • Different transaction models: Journaling, Write-Anywhere (Copy-on-Write), Hybrid transaction modelMirrors and failover
  • 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
  • Transparent compression (LZO, ZLIB)
  • Plugin infrastructure
  • 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
  • Meta-data and inline-data checksums
  • Mirrors and failover
  • Precise discard support with delayed issuing of discard requests for SSD devices

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.

Performance

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. Other benchmarks from 2006 show results of Reiser4 being slower on many operations. Benchmarks conducted in 2013 with Linux Kernel version 3.10 show that Reiser4 is considerably faster in various tests compared to in-kernel filesystems EXT4, btrfs and XFS.

Integration with Linux

On August 14, 2014, Phoronix.com reported that Reiser4 has been ported into the Linux 3.15 kernel, although the latest stable kernel is 3.16. 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, but Hans Reiser suggested political reasons. Latest released reiser4 kernel patches and tools can be downloaded from reiser4 project page at sourceforge.net: http://reiser4.sourceforge.net/

History of Reiser4

See also: Hans Reiser

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; 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, making source code available from Shishkin's web site, later relocated to kernel.org. Since 2008, Namesys employees have received 100% of their sponsored funding from DARPA.

In 2010, Phoronix wrote that Edward Shishkin was exploring options to get Reiser4 merged into Linux kernel mainline. As of 2015, the file system is still being updated for new kernel releases, but has not been submitted for merging. According to Phoronix, it's unlikely to happen without corporate backing.

See also

References

  1. Documentation/filesystems/reiser4.txt from a reiser4-patched kernel source, "By default file in reiser4 have 64-bit timestamps."
  2. Michael Larabel (30 March 2016). "Reiser4 Now Available For Linux 4.5 Kernel". Phoronix.
  3. ^ Michael Larabel (23 February 2015). "KDBUS & Other Features You Won't Find In The Linux 4.0 Kernel". Phoronix.
  4. "Reiser4 transaction models". Reiser4 wiki.
  5. "Reiser4 Mirrors and Failover". Reiser4 wiki.
  6. "Reiser4 checksums". Reiser4 wiki.
  7. "Reiser4 Mirrors and Failover". Reiser4 wiki.
  8. "Precise Discard". Reiser4 wiki.
  9. "Reiser4 discard support". Reiser4 wiki.
  10. Reiser, Hans (2004-09-16). "Re: Benchmark: ext3 vs reiser4 and effects of fragmentation". Namesys, ReiserFS mailing list. Retrieved 2009-10-03.
  11. Hans Reiser (November 20, 2003). "Benchmarks Of ReiserFS Version 4". Namesys. Archived from the original on September 29, 2007. Retrieved 2014-01-18. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  12. Justin Piszcz (January 2006). "Benchmarking Filesystems Part II". Retrieved 2006-04-23.
  13. Michael Larabel (July 31, 2013). "Reiser4 File-System Shows Decent Performance On Linux 3.10". Phoronix. Retrieved 2013-07-31.
  14. "Reiser4 Now Available For Linux 3.15". Larabel, Michael. https://www.phoronix.com/scan.php?page=news_item&px=MTc2MzE
  15. "Linux: Why Reiser4 Is Not in the Kernel". Kerneltrap. September 19, 2005. Archived from the original on 2007-04-23.
  16. Reiser, Hans (21 July 2006). "The "'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion". Retrieved 2008-03-01.
  17. "Murder Suspect Selling Namesys". Wired News. 2006-12-21. Retrieved 2006-12-30.
  18. 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.
  19. "Namesys things". Chichkin_i.zelnet.ru. Retrieved 2010-02-08.
  20. New location of Namesys software Linux Kernel Mailing List post, 2008-08-04
  21. "Re: we got the DARPA grant to add views to Reiser4". Mail-archive.com. 2004-04-10. Retrieved 2010-02-08.
  22. "Bug 114785 – reiserfs won't mount with usrquota option". Red Hat Bugzilla.
  23. "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.
  24. "Reiser4 May Go For Mainline Inclusion In 2010". Phoronix.com. 2009-11-10. Retrieved 2010-02-08.

External links

File systems
Disk and
non-rotating
Optical disc
Flash memory and SSD
host-side wear leveling
Distributed parallel
NAS
Specialized
Pseudo
Encrypted
Types
Features
Access control
Interfaces
Lists
Layouts
Categories:
Reiser4: Difference between revisions Add topic