*** Welcome to piglix ***

ReiserFS

ReiserFS
Developer(s) Namesys
Full name ReiserFS
Introduced 2001 with Linux 2.4.1
Partition identifier Apple_UNIX_SVR2 (Apple Partition Map)
0x83 (MBR)
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (GPT)
Structures
Directory contents B+ tree
File allocation Bitmap
Limits
Max. volume size 16 TiB
Max. file size 1 EiB (8 TiB on 32 bit systems)
Max. number of files 232−3 (~4 billion)
Max. filename length 4032 bytes, limited to 255 by Linux VFS
Allowed characters in filenames All bytes except NUL and '/'
Features
Dates recorded modification (mtime), metadata change (ctime), access (atime)
Date range December 14, 1901 – January 18, 2038
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, journaled computer file system formerly designed and implemented by a team at Namesys led by Hans Reiser. ReiserFS is currently supported on Linux (without quota support). 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 is the default file system on the Elive, Xandros, Linspire, and YOPER Linux distributions. ReiserFS was the default file system in Novell's SUSE Linux Enterprise until Novell decided to move to ext3 on October 12, 2006 for future releases.

Namesys considered ReiserFS (now occasionally referred to as Reiser3) stable and feature-complete and, with the exception of security updates and critical bug fixes, ceased development on it to concentrate on its successor, Reiser4. Namesys went out of business in 2008 after Hans Reiser was charged with the murder of his wife (and later convicted and sent to prison). Nevertheless, volunteers continue to work on the open source project.

At the time of its introduction, ReiserFS offered features that had not been available in existing Linux file systems:

Compared with ext2 and ext3 in version 2.4 of the Linux kernel, when dealing with files under 4 KiB and with tail packing enabled, ReiserFS may be faster. This was said to be of great benefit in Usenet news spools, HTTP caches, mail delivery systems, and other applications where performance with small files is critical. However, in practice news spools use a feature called cycbuf, which holds articles in one large file; fast HTTP caches and several revision control systems use a similar approach, nullifying these performance advantages. For email servers, ReiserFS was problematic due to semantic problems explained below. Also, ReiserFS had a problem with very fast filesystem aging when compared to other filesystems — in several usage scenarios filesystem performance decreased dramatically with time.


...
Wikipedia

...