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 editContent deleted Content addedVisualWikitext
Revision as of 02:16, 22 March 2007 editSlowking Man (talk | contribs)Extended confirmed users10,329 editsm Reverted edits by 219.88.77.237 (talk) to last version by Rvalles← Previous edit Latest revision as of 11:18, 20 October 2024 edit undo88.97.16.53 (talk) NUL not NULLTags: Mobile edit Mobile web edit 
(375 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
{{short description|Computer file system, successor to ReiserFS}}
{{Infobox Filesystem |
{{Multiple issues|
name = Reiser4 |
{{Lead too short|date=February 2010}}
full_name = Reiser4|
{{More citations needed|date=January 2017}}
developer = ] |
introduction_os = ] |
OS = Linux |
introduction_date = 2004 |
partition_id = <tt>Apple_UNIX_SVR2</tt> (])<br><tt>0x83</tt> (])<br><tt>]</tt> (])|
directory_struct = ] ] |
file_struct = |
bad_blocks_struct = |
max_filename_size = 3976 bytes |
max_files_no = |
max_volume_size = |
max_file_size = 8 ] on x86 |
filename_character_set = All bytes except NUL and '/'|
dates_recorded = modification (mtime), metadata change (ctime), access (atime) |
date_range = 64-bit timestamps<ref>Documentation/filesystems/reiser4.txt from a reiser4-patched kernel source, "By default file in reiser4 have 64 bit timestamps."</ref> |
forks_streams = Extended attributes |
attributes = |
file_system_permissions = Unix permissions, ]s and arbitrary security attributes |
compression = Version 4.1 (beta) |
encryption = Version 4.1 (beta) |
}} }}
{{ infobox filesystem
'''Reiser4''' is a ] ], a new "from scratch" successor to the ] file system, developed by ] and sponsored by ] as well as ].
| name = Reiser4

| full_name = Reiser4
], Reiser4 has not yet been merged into the mainline ] and consequently is still not supported on many ]s; however, its predecessor ReiserFS v3 has been much more widely adopted. Reiser4 is also available from ]'s -mm kernel sources. Linux kernel developers claim that Reiser4 breaks Linux coding standards,<ref>{{cite web | url=http://kerneltrap.org/node/6844 | title=Linux: Why Reiser4 Is Not in the Kernel | year=September 19, 2005 | publisher=Kerneltrap }}</ref> but ] suggests political reasons.
| developer = Edward Shishkin and others<ref>{{Cite web |url=https://reiser4.wiki.kernel.org/index.php/Credits |title=Credits - Reiser4 FS Wiki |website=reiser4.wiki.kernel.org |access-date=2019-08-05}}</ref>
| introduction_os = ]
| OS = Linux
| introduction_date = {{Start date and age|2004}}
| partition_id =
<code>Apple_UNIX_SVR2</code> (])<br />
<code>0x83</code> (])<br />
<code>]</code> (])
| directory_struct = ] ]
| file_struct =
| bad_blocks_struct =
| max_filename_size = 3976 bytes
| max_files_no =
| max_volume_size =
| max_file_size = 8 ] on x86
| filename_character_set = All bytes except NUL and '/'
| dates_recorded = modification (mtime), metadata change (ctime), access (atime)
| date_range = 64-bit timestamps<ref>Documentation/filesystems/reiser4.txt from a reiser4-patched kernel source, "By default file in reiser4 have 64-bit timestamps."</ref>
| forks_streams = No
| attributes =
| file_system_permissions = Unix permissions
| compression = Yes
| encryption = No
| single_instance_storage = No
| website =
| repo =
}}
'''Reiser4''' is a ] ], successor to the ] file system, developed from scratch by ] and sponsored by ] as well as ]. Reiser4 was named after its former lead developer ]. {{As of|2021}}, the Reiser4 patch set is still being maintained,<ref name="phLinux5patch">{{Cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=Reiser4-Linux-5.0-Patch |title=Reiser4 Brought To The Linux 5.0 Kernel - Phoronix |last=Larabel |first=Michael |author-link=Michael Larabel |date=2019-04-13 |website=] |access-date=2019-08-04}}</ref><ref name=reiser4sourceforge/> but according to ], it is unlikely to be merged into mainline Linux without corporate backing.<ref>{{Cite web|url=https://phoronix.com/scan.php?page=news_item&px=Linux-4.10-Ten-Missing-Features|title = Ten Features You Will Not Find in the Mainline Linux 4.10 Kernel - Phoronix}}</ref>


== Features == == Features ==
Some of the goals of the Reiser4 file system are: Some of the goals of the Reiser4 file system are:


* ] (filesystem operations either complete, or they do not, and they do not corrupt due to partially occurring)
* Different transaction models: journaling, write-anywhere (]), 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>
* More efficient ] through wandering logs * More efficient ] through wandering logs
* More efficient support of small files, in terms of disk space and speed through ] * More efficient support of small files, in terms of disk space and speed through ]
* Liquid items (or virtual keys) – a special format of records in the storage tree, which completely resolves the problem of ]
* EOTTL (extents on the twig level) – fully balanced storage tree, meaning that all paths to objects are of equal length
* Faster handling of ] with large numbers of files * Faster handling of ] with large numbers of files
* Transparent compression: ] (LZO), ]
* Flexible plugin infrastructure (through which special ] types, ] and ] will be supported)
* Plugin infrastructure
* Dynamically optimized disk-layout through ] (also called delayed allocation in ]) * Dynamically optimized disk-layout through ] (also called delayed allocation in ])
* Delayed actions (tree balancing, compression, block allocation, local defragmentation)
* ] support
* R and D (Rare and Dense) caches, synchronized at commit time
* ] support for user-defined integrity
* ] and inline-data ]<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/Reiser4_checksums |title=Reiser4 checksums |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>
* Precise ] support<ref>{{cite web |url=http://reiser4.wiki.kernel.org/index.php/PreciseDiscard |title=Precise Discard |work=Reiser4 wiki }}</ref> with delayed issuing of discard requests for SSD devices<ref>{{cite web |url=https://reiser4.wiki.kernel.org/index.php/Reiser4_discard_support |title=Reiser4 discard support |work=Reiser4 wiki }}</ref>


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


At present Reiser4 lacks a few standard file system features, such as an online repacker (similar to the ] utilities provided with other file systems). The creators of Reiser4 say they will implement these later; sooner if someone pays them to do so.<ref name=reiser4-repacker>{{cite web| first=Hans| last=Reiser| publisher=Namesys, ReiserFS mailing list |title=Re: Benchmark : ext3 vs reiser4 and effects of fragmentation.| date=2004-09-16 |url=http://www.xy1.org/reiserfs-list@namesys.com/msg04018.html |accessdate=2006-10-13}}</ref> At present Reiser4 lacks a few standard file system features, such as an online repacker (similar to the ] 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.<ref name=reiser4-repacker>{{cite web| first=Hans| last=Reiser| publisher=Namesys, ReiserFS mailing list |title=Re: Benchmark: ext3 vs reiser4 and effects of fragmentation.| date=2004-09-16 |url=http://marc.info/?l=reiserfs-devel&m=109535506122706&w=2 |access-date=2009-10-03}}</ref>


== Performance == == Performance ==
Reiser4 uses ]s in conjunction with the ] balancing approach, in which underpopulated nodes will not get 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. Reiser4 uses ]s in conjunction with the ] 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.


], synthetic benchmarks performed by Namesys show that Reiser4 is 10 to 15 times faster than its most serious competitor ] working on files smaller than 1 ]. Namesys's benchmarks suggest it is typically twice the performance of ext3 for general-purpose filesystem usage patterns.<ref>{{cite web | url=http://www.namesys.com/benchmarks.html | title=Benchmarks Of ReiserFS Version 4 | author=Hans Reiser | year=], ] | publisher=Namesys | accessdate=2006-11-28}}</ref> {{As of|2004}}, synthetic benchmarks performed by Namesys in 2003 show that Reiser4 is 10 to 15 times faster than its most serious competitor ] working on files smaller than 1 ]. Namesys's benchmarks suggest it is typically twice the performance of ext3 for general-purpose filesystem usage patterns.<ref>{{cite web|url=http://www.namesys.com/ |title=Benchmarks Of ReiserFS Version 4 |author=Hans Reiser |date=November 20, 2003 |publisher=Namesys |access-date=2014-01-18 |url-status=dead |archive-url=https://web.archive.org/web/20070929195459/http://www.namesys.com/ |archive-date=September 29, 2007 }}</ref> Other benchmarks from 2006 show results of Reiser4 being slower on many operations.<ref>{{cite web|url = http://linuxgazette.net/122/TWDT.html#piszcz|title = Benchmarking Filesystems Part II|author = Justin Piszcz|date=January 2006|access-date = 2006-04-23 }}</ref> Benchmarks conducted in 2013 with Linux Kernel version 3.10 show that Reiser4 is considerably faster in various tests compared to in-kernel filesystems ], ] and ].<ref>{{cite web | url= https://www.phoronix.com/scan.php?page=article&item=linux_310_reiser4 | title=Reiser4 File-System Shows Decent Performance On Linux 3.10| author=Michael Larabel | date=July 31, 2013 | publisher=Phoronix | access-date=2013-07-31}}</ref>

==Integration with Linux==
Reiser4 has patches for Linux 2.6, 3.x, 4.x and 5.x.,<ref>{{Cite web |url=https://sourceforge.net/projects/reiser4/files/ |title=Reiser4 file system for Linux OS - Browse Files at SourceForge.net |website=sourceforge.net |access-date=2019-08-04}}</ref><ref name="phLinux5patch" /> but {{as of|lc=y|2019}}, Reiser4 has not been merged into the mainline ]<ref name="phLinux5patch" /> and consequently is still not supported on many ]s; however, its predecessor ReiserFS v3 has been widely adopted. Reiser4 is also available from ]'s ] kernel sources, and from the Zen patch set. The Linux kernel developers claim that Reiser4 does not follow the Linux "coding style" by the decision to use its own plugin system,<ref>{{cite web | url=http://kerneltrap.org/node/6844 | archive-url=https://web.archive.org/web/20070423030227/http://kerneltrap.org/node/6844 | archive-date=2007-04-23 | title=Linux: Why Reiser4 Is Not in the Kernel | date=September 19, 2005 | publisher=Kerneltrap }}</ref> but ] suggested the decision was made for political reasons.<ref>{{cite web | url=https://lkml.org/lkml/2006/7/21/109 | title=The "'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion | first=Hans | last=Reiser | author-link=Hans Reiser | date=21 July 2006 | access-date=2008-03-01}}</ref>
The latest released Reiser4 kernel patches and tools can be downloaded from Reiser4 project page at sourceforge.net.<ref name=reiser4sourceforge></ref>

== History of Reiser4 ==
{{See also|Hans Reiser}}
Hans Reiser was convicted of ] on April 28, 2008, leaving the future of Reiser4 uncertain. After his arrest, employees of Namesys were 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;<ref>{{cite web
|url=https://www.wired.com/news/technology/0,72342-0.html?tw=wn_technology_1
|title=Murder Suspect Selling Namesys
|publisher=]
|date=2006-12-21
|access-date=2006-12-30
}}</ref> 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, "Commercial activity of Namesys has stopped." Shishkin and others continued the development of Reiser4,<ref>Namesys vanishes, but ReiserFS project lives on. http://www.news.com/8301-13580_3-9851703-39.html {{Webarchive|url=https://web.archive.org/web/20080905032318/http://www.news.com/8301-13580_3-9851703-39.html |date=2008-09-05 }} CNet (January 16, 2008). Retrieved on 2008-01-26.</ref> making source code available from Shishkin's web site,<ref>{{cite web |url=http://chichkin_i.zelnet.ru/namesys/ |title=Namesys things |publisher=Chichkin_i.zelnet.ru |access-date=2010-02-08 |url-status=dead |archive-url=https://web.archive.org/web/20100324124748/http://chichkin_i.zelnet.ru/namesys/ |archive-date=2010-03-24 }}</ref> later relocated to ].<ref>New location of Namesys software </ref> Since 2008, Namesys employees have received 100% of their sponsored funding from ].<ref>{{cite web|url=http://www.mail-archive.com/reiserfs-list%40namesys.com/msg11961.html |title=Re: we got the DARPA grant to add views to Reiser4 |publisher=Mail-archive.com |date=2004-04-10 |access-date=2010-02-08}}</ref><ref>{{cite web |url=https://bugzilla.redhat.com/show_bug.cgi?id=114785 |title=Bug 114785 – reiserfs won't mount with usrquota option |work=Red Hat Bugzilla }}</ref><ref>{{cite web|url=http://www.linuxplanet.com/linuxplanet/reports/3726/1/ |title=Reports - ext3 or ReiserFS? Hans Reiser Says Red Hat's Move Is Understandable - Red Hat's Decision is Conservative, Not Radical |publisher=LinuxPlanet |access-date=2010-02-08}}</ref>

In 2010, ] wrote that Edward Shishkin was exploring options to get Reiser4 merged into Linux kernel mainline.<ref>{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=NzY4OQ |title=Reiser4 May Go For Mainline Inclusion In 2010 |publisher=] |date=2009-11-10 |access-date= 2010-02-08}}</ref> {{As of|2019}}, the file system is still being updated for new kernel releases, but has not been submitted for merging.<ref name="phLinux5patch" /> In 2015, ] mentioned it is unlikely to happen without corporate backing,<ref name=not-in-linux-4.0>{{cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.0-Missing-Features |author=Michael Larabel |date=23 February 2015 |title=KDBUS & Other Features You Won't Find In The Linux 4.0 Kernel |work=] }}</ref> and then he suggested in April 2019 that the main obstacle could be the renaming of Reiser4 to avoid reference to the initial author who was convicted of murder.<ref name="phLinux5patch" />

Shishkin announced a ] filesystem on December 31, 2019.<ref>{{cite web|url=https://lwn.net/ml/linux-kernel/ee55ce28-2434-d3c6-0d2d-2ed1ea8f35d7%40gmail.com/|title= Reiser5 (Format Release 5.X.Y)|date=2019-12-31|publisher=Linux Weekly News}}</ref>


== See also == == See also ==
* ]
* ] * ]
* ] * ]


== External links == == References ==
{{Reflist}}
*

*
==External links==
* on ]
*
* from Namesys.com
* * as ]' website is down
*
* ]'s lecture at ]
* on ]
* at kernelnewbies.org and
*
* on Linux.com
* from ]
* from ]
* ]'s lecture at ]
* at kernelnewbies.org and
* by Bruce Byfield on Linux.com
* - lecture given by Hans Reiser at ] ().
*
* – a Debian installer including Reiser4


{{File systems}}
== Notes and references ==
<references/>


]
]
] ]
]
]


] ]
]
]
]
]
]
]
]
]

Latest revision as of 11:18, 20 October 2024

Computer file system, successor to ReiserFS
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
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)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Reiser4" – news · newspapers · books · scholar · JSTOR (January 2017) (Learn how and when to remove this message)
(Learn how and when to remove this message)
Reiser4
Developer(s)Edward Shishkin and others
Full nameReiser4
Introduced2004; 21 years ago (2004) 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 NUL 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
Websitereiser4.wiki.kernel.org
Repositorygithub.com/edward6/reiser4

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 2021, the Reiser4 patch set is still being maintained, but according to Phoronix, it is 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 complete, or they do not, and they do not corrupt due to partially occurring)
  • Different transaction models: journaling, 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
  • Transparent compression: Lempel-Ziv-Oberhumer (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
  • Metadata 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

Reiser4 has patches for Linux 2.6, 3.x, 4.x and 5.x., but as of 2019, Reiser4 has not 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 the Zen patch set. The Linux kernel developers claim that Reiser4 does not follow the Linux "coding style" by the decision to use its own plugin system, but Hans Reiser suggested the decision was made for political reasons. The latest released Reiser4 kernel patches and tools can be downloaded from Reiser4 project page at 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 were 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, "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 2019, the file system is still being updated for new kernel releases, but has not been submitted for merging. In 2015, Michael Larabel mentioned it is unlikely to happen without corporate backing, and then he suggested in April 2019 that the main obstacle could be the renaming of Reiser4 to avoid reference to the initial author who was convicted of murder.

Shishkin announced a Reiser5 filesystem on December 31, 2019.

See also

References

  1. "Credits - Reiser4 FS Wiki". reiser4.wiki.kernel.org. Retrieved 2019-08-05.
  2. Documentation/filesystems/reiser4.txt from a reiser4-patched kernel source, "By default file in reiser4 have 64-bit timestamps."
  3. ^ Larabel, Michael (2019-04-13). "Reiser4 Brought To The Linux 5.0 Kernel - Phoronix". Phoronix. Retrieved 2019-08-04.
  4. ^ http://reiser4.sourceforge.net/
  5. "Ten Features You Will Not Find in the Mainline Linux 4.10 Kernel - Phoronix".
  6. "Reiser4 transaction models". Reiser4 wiki.
  7. "Reiser4 checksums". Reiser4 wiki.
  8. "Reiser4 Mirrors and Failover". Reiser4 wiki.
  9. "Precise Discard". Reiser4 wiki.
  10. "Reiser4 discard support". Reiser4 wiki.
  11. Reiser, Hans (2004-09-16). "Re: Benchmark: ext3 vs reiser4 and effects of fragmentation". Namesys, ReiserFS mailing list. Retrieved 2009-10-03.
  12. Hans Reiser (November 20, 2003). "Benchmarks Of ReiserFS Version 4". Namesys. Archived from the original on September 29, 2007. Retrieved 2014-01-18.
  13. Justin Piszcz (January 2006). "Benchmarking Filesystems Part II". Retrieved 2006-04-23.
  14. Michael Larabel (July 31, 2013). "Reiser4 File-System Shows Decent Performance On Linux 3.10". Phoronix. Retrieved 2013-07-31.
  15. "Reiser4 file system for Linux OS - Browse Files at SourceForge.net". sourceforge.net. Retrieved 2019-08-04.
  16. "Linux: Why Reiser4 Is Not in the Kernel". Kerneltrap. September 19, 2005. Archived from the original on 2007-04-23.
  17. Reiser, Hans (21 July 2006). "The "'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion". Retrieved 2008-03-01.
  18. "Murder Suspect Selling Namesys". Wired News. 2006-12-21. Retrieved 2006-12-30.
  19. Namesys vanishes, but ReiserFS project lives on. http://www.news.com/8301-13580_3-9851703-39.html Archived 2008-09-05 at the Wayback Machine CNet (January 16, 2008). Retrieved on 2008-01-26.
  20. "Namesys things". Chichkin_i.zelnet.ru. Archived from the original on 2010-03-24. Retrieved 2010-02-08.
  21. New location of Namesys software Linux Kernel Mailing List post, 2008-08-04
  22. "Re: we got the DARPA grant to add views to Reiser4". Mail-archive.com. 2004-04-10. Retrieved 2010-02-08.
  23. "Bug 114785 – reiserfs won't mount with usrquota option". Red Hat Bugzilla.
  24. "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.
  25. "Reiser4 May Go For Mainline Inclusion In 2010". Phoronix. 2009-11-10. Retrieved 2010-02-08.
  26. Michael Larabel (23 February 2015). "KDBUS & Other Features You Won't Find In The Linux 4.0 Kernel". Phoronix.
  27. "[ANNOUNCE] Reiser5 (Format Release 5.X.Y)". Linux Weekly News. 2019-12-31.

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