Developer(s) | Namesys |
---|---|
Full name | ReiserFS |
Introduced | 2001Linux 2.4.1 | with
Partition IDs |
|
Structures | |
Directory contents | B+ tree |
File allocation | Bitmap[1] |
Limits | |
Max volume size | 16 TiB[2] |
Max file size | 1 EiB (8 TiB on 32 bit systems)[2] |
Max no. of files | 232−3 (~4 billion)[2] |
Max filename length | 4032 bytes, limited to 255 by Linux VFS |
Allowed filename characters | All bytes except NUL and '/' |
Features | |
Dates recorded | Modification (mtime), metadata change (ctime), access (atime) |
Date range | December 14, 1901 – January 18, 2038 (32-bit Unix time) |
Date resolution | 1 s |
Forks | Extended attributes |
File system permissions | Unix permissions, ACLs and arbitrary security attributes |
Transparent compression | No |
Transparent encryption | No |
Other | |
Supported operating systems | Linux, ReactOS |
ReiserFS is a general-purpose, journaling file system initially designed and implemented by a team at Namesys led by Hans Reiser and licensed under GPLv2. Introduced in version 2.4.1 of the Linux kernel, it was the first journaling file system to be included in the standard kernel. ReiserFS was the default file system in Novell's SUSE Linux Enterprise until Novell decided to move to ext3 for future releases on October 12, 2006.[3]
ReiserFS version 3.6, now occasionally referred to as Reiser3, introduced a new on-disk format allowing larger filesizes. Namesys considered ReiserFS stable and feature-complete and ceased development on it to concentrate on its successor, Reiser4, though it continued to release security updates and critical bug fixes. Namesys went out of business in 2008 after Reiser's conviction for murder. The product is now maintained as open source by volunteers.[4] The reiserfsprogs 3.6.27 were released on 25 July 2017.[5]
ReiserFS is currently supported on Linux without quota support. It has been discussed for removal from the Linux kernel since early 2022 due to a lack of maintenance upstream, and technical issues inherent to the filesystem, such as suffering from the year 2038 problem;[6][7][8] it was deprecated in Linux 5.18,[9] and marked as obsolete in Linux 6.6.[10] It is planned for removal in Linux 6.13. [11] [12] [13] [14]