View source for Software:Comparison of file systems

{{short description|None}}
{{Incomplete list|date=July 2015}}
<!-- ideally every table cell needs a verifiable cite -->
<!-- PLEASE ADD INFO TO THE EMPTY COLUMNS. PLEASE DO NOT DELETE THE COLUMNS BECAUSE THEY'RE EMPTY -->

The following tables compare general and technical information for a number of file systems.

== General information ==
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed;"
! scope="col" | File system
! scope="col" | Creator
! scope="col" | Year of introduction
! scope="col" | Original [[Operating system|operating system]]
|-
|{{rh}} | [[Engineering:DECtape|DECtape]]
| [[Company:Digital Equipment Corporation|DEC]]
| 1964
| PDP-6 Monitor
|-
|{{rh}} | [[Software:MVS#MVS filesystem|OS/3x0 FS]]
| [[Company:IBM|IBM]]
| 1964
| OS/360
|-
|{{rh}} | Level-D
| [[Company:Digital Equipment Corporation|DEC]]
| 1968
| [[Software:TOPS-10|TOPS-10]]
|-
|{{rh}} | George 3
| [[Company:International Computers and Tabulators|ICT]] (later [[Company:International Computers Limited|ICL]])
| 1968
| [[Software:GEORGE (operating system)|George 3]]
|-
|{{rh}} | Version 6 Unix file system (V6FS)
| [[Organization:Bell Labs|Bell Labs]]
| 1972
| [[Software:Version 6 Unix|Version 6 Unix]]
|-
|{{rh}} | [[Software:RT-11|RT-11]] file system
| [[Company:Digital Equipment Corporation|DEC]]
| 1973
| [[Software:RT-11|RT-11]]
|-
|{{rh}} | Disk Operating System (GEC DOS)
| GEC
| 1973
| Core Operating System
|-
|{{rh}} | CP/M file system
| [[Company:Digital Research|Digital Research]] ([[Biography:Gary Kildall|Gary Kildall]])
| 1974
|-
|{{rh}} | ODS-1
| [[Company:Digital Equipment Corporation|DEC]]
| 1975
| [[Software:RSX-11|RSX-11]]
|-
|{{rh}} | GEC DOS filing system extended
| GEC
| 1977
| [[Software:OS4000|OS4000]]
|-
|{{rh}} | FAT (8-bit)<!-- the 8-bit variant was just named "FAT" -->
| [[Company:Microsoft|Microsoft]] (Marc McDonald) for NCR
| 1977
| Microsoft Standalone Disk BASIC-80 (later Microsoft Standalone Disk BASIC-86)<!-- but not the normal "non-Standalone" Disk BASIC-80 and -86! -->
|-
|{{rh}} | [[Software:Apple DOS|DOS 3.x]]<!-- This is the name of a file system *and* an operating system -->
| [[Company:Apple Inc.|Apple]]
| 1978
| [[Software:Apple DOS|Apple DOS]]
|-
|{{rh}} | UCSD p-System
| UCSD
| 1978
| UCSD p-System
|-
|{{rh}} | CBM DOS
| [[Company:Commodore International|Commodore]]
| 1978
| [[Commodore BASIC]]
|-
|{{rh}} | [[Software:Atari DOS|Atari DOS]]
| [[Company:Atari|Atari]]
| 1979
| Atari 8-bit
|-
|{{rh}} | Version 7 Unix file system (V7FS)
| [[Organization:Bell Labs|Bell Labs]]
| 1979
| [[Software:Version 7 Unix|Version 7 Unix]]
|-
|{{rh}} | ODS-2
| [[Company:Digital Equipment Corporation|DEC]]
| 1979
| [[Software:OpenVMS|OpenVMS]]
|-
|{{rh}} | [[FAT12]]
| [[Company:Seattle Computer Products|Seattle Computer Products]] (Tim Paterson)
| <!-- August -->1980
| QDOS/[[Software:86-DOS|86-DOS]] (later IBM PC DOS 1.0)
|-
|{{rh}} | ProDOS <!-- This is the name of a file system *and* an operating system -->
| [[Company:Apple Inc.|Apple]]
| 1980
| [[Software:Apple SOS|Apple SOS]] (later ProDOS 8)
|-
|{{rh}} | [[Disc Filing System|DFS]]
| Acorn Computers Ltd
| 1982
| [[Engineering:BBC Micro|Acorn BBC Micro]] [[Software:Acorn MOS|MOS]]
|-
|{{rh}} | [[Advanced Disc Filing System|ADFS]]
| Acorn Computers Ltd
| 1983
| [[Engineering:Acorn Electron|Acorn Electron]] (later [[Software:RISC OS|Arthur/RISC OS]])
|-
|{{rh}} | FFS
| [[Biography:Marshall Kirk McKusick|Kirk McKusick]]
| 1983
| 4.2BSD
|-
|{{rh}} | [[FAT16]]
| [[Company:IBM|IBM]], [[Company:Microsoft|Microsoft]]
| <!-- August -->1984
| PC DOS 3.0, MS-DOS 3.0
|-
|{{rh}} | [[Macintosh File System|MFS]]
| [[Company:Apple Inc.|Apple]]
| 1984
| [[Software:System 1|System 1]]
|-
|{{rh}} | Elektronika BK tape format
| NPO "Scientific centre" (now [[Company:Sitronics|Sitronics]])
| 1985
| Vilnius Basic, BK monitor program
|-
|{{rh}} | [[Hierarchical File System (Apple)|HFS]]
| [[Company:Apple Inc.|Apple]]
| <!-- September -->1985
| System 2.1
|-
|{{rh}} | [[Amiga Old File System|Amiga OFS]]{{ref|54}}
| Metacomco for [[Company:Commodore International|Commodore]]
| 1985
| Amiga OS
|-
|{{rh}} | [[Software:GEMDOS|GEMDOS]]
| [[Company:Digital Research|Digital Research]]
| 1985
| [[Software:Atari TOS|Atari TOS]]
|-
|{{rh}} | [[NetWare File System|NWFS]]
| [[Company:Novell|Novell]]
| 1985
| NetWare 286
|-
|{{rh}} | [[High Sierra Format|High Sierra]]
| Ecma International
| 1986
| [[Software:MSCDEX|MSCDEX]] for MS-DOS 3.1/3.2<ref>{{cite journal |title=Extensions to MS-DOS Run CD-ROM |author-first=Scott |author-last=Mace |journal=InfoWorld |volume=8 |issue=38 |date=1986-09-22 |pages=1, 8 |url=https://books.google.com/books?id=ZS8EAAAAMBAJ&pg=PA1 |access-date=2016-11-09}}</ref>
|-
|{{rh}} | [[FAT16B]]
| [[Company:Compaq|Compaq]]
| 1987 <!-- November -->
| Compaq MS-DOS 3.31
|-
|{{rh}} | Minix V1 FS
| [[Biography:Andrew S. Tanenbaum|Andrew S. Tanenbaum]]
| 1987
| MINIX 1.0
|-
|{{rh}} | [[Amiga Fast File System|Amiga FFS]]
| [[Company:Commodore International|Commodore]]
| 1988
| Amiga OS 1.3
|-
|{{rh}} | [[ISO 9660:1988|1988]]
| Ecma International, ISO
| 1988
| [[Software:MS-DOS|MS-DOS]], "classic" Mac OS, and [[Software:AmigaOS|AmigaOS]]
|-
|{{rh}} | [[High Performance File System|HPFS]]
| [[Company:IBM|IBM]] & [[Company:Microsoft|Microsoft]]
| 1989 <!-- November -->
| OS/2 1.2
|-
|{{rh}} | [[Rock Ridge]]
| IEEE
| {{Circa|1990|sortable=yes}}
| [[Software:Unix|Unix]]
|-
|{{rh}} | JFS1
| [[Company:IBM|IBM]]
| 1990
| [[Software:IBM AIX|AIX]]{{efn |name=note-11 |IBM introduced JFS with the initial release of [[Software:IBM AIX|AIX]] Version 3.1 in 1990. This file system now called JFS1. The new JFS, on which the Linux port was based, was first shipped in OS/2 Warp Server for e-Business in 1999. The same sourcebase was also used for release JFS2 on AIX 5L.}}
|-
|{{rh}} | [[Veritas File System|VxFS]]
| VERITAS
| 1991
| SVR4.0
|-
|{{rh}} | [[Extended file system|ext]]
| Rémy Card
| 1992
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[AdvFS]]
| [[Company:Digital Equipment Corporation|DEC]]
| 1993<ref>{{cite web |last1=Warren |first1=David |date=20 October 1993 |title=Polycenter File System - - HELP |url=http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html |archive-url=https://web.archive.org/web/20120309144054/http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html |archive-date=9 March 2012 |url-status=dead}}</ref>
| Digital Unix
|-
|{{rh}} | [[NTFS]]
| [[Company:Microsoft|Microsoft]] (Gary Kimura, Tom Miller)
| 1993
| [[Software:Windows NT 3.1|Windows NT 3.1]]
|-
|{{rh}} | [[Log-structured File System (BSD)|LFS]]
| [[Biography:Margo Seltzer|Margo Seltzer]]
| 1993
| Berkeley Sprite
|-
|{{rh}} | [[Ext2|ext2]]
| Rémy Card
| 1993
| [[Software:Linux|Linux]], Hurd
|-
|{{rh}} | [[Xiafs]]
| Q. Frank Xia
| 1993
| [[Software:Linux|Linux]]
|-
|{{rh}} | UFS1
| [[Biography:Marshall Kirk McKusick|Kirk McKusick]]
| 1994
| 4.4BSD
|-
|{{rh}} | [[XFS]]
| [[Company:Silicon Graphics|SGI]]
| 1994
| [[Software:IRIX|IRIX]]
|-
|{{rh}} | [[Hierarchical File System (IBM MVS)|HFS]]
| [[Company:IBM|IBM]]
| 1994
| MVS/ESA (now z/OS)
|-
|{{rh}} | [[FAT16X]]
| [[Company:Microsoft|Microsoft]]
| 1995
| MS-DOS 7.0 / [[Software:Windows 95|Windows 95]]
|-
|{{rh}} | [[Joliet (file system)|Joliet ("CDFS")]]
| [[Company:Microsoft|Microsoft]]
| 1995
| [[Software:Microsoft Windows|Microsoft Windows]], [[Software:Linux|Linux]], "classic" Mac OS, and [[Software:FreeBSD|FreeBSD]]
|-
|{{rh}} | [[Universal Disk Format|UDF]]
| [[Organization:International Organization for Standardization|ISO]]/ECMA/[[Organization:Optical Storage Technology Association|OSTA]]
| 1995
| {{n/a}}
|-
|{{rh}} | [[FAT32]], [[FAT32X]]
| [[Company:Microsoft|Microsoft]]
| 1996
| MS-DOS 7.10 / Windows 95 OSR2{{efn |name=note-10 |[[Company:Microsoft|Microsoft]] first introduced FAT32 in MS-DOS 7.1 / Windows 95 OSR2 (OEM Service Release 2) and then later in [[Software:Windows 98|Windows 98]]. NT-based Windows did not have ''any'' support for FAT32 up to Windows NT4; Windows 2000 was the first NT-based Windows OS that received the ability to work with it.}}
|-
|{{rh}} | [[QFS]]
| [[Company:Sun Microsystems|Sun Microsystems]]
| 1996
| [[Software:Solaris (operating system)|Solaris]]
|-
|{{rh}} | [[GPFS]]
| [[Company:IBM|IBM]]
| 1996
| [[Software:IBM AIX|AIX]], [[Software:Linux|Linux]]
|-
|{{rh}} | [[Be File System]]
| [[Company:Be Inc.|Be Inc.]] (D. Giampaolo, Cyril Meurillon)
| 1996
| [[Software:BeOS|BeOS]]
|-
|{{rh}} | Minix V2 FS
| [[Biography:Andrew S. Tanenbaum|Andrew S. Tanenbaum]]
| 1997
| MINIX 2.0
|-
|{{rh}} | [[HFS Plus]]
| [[Company:Apple Inc.|Apple]]
| 1998
| Mac OS 8.1
|-
|{{rh}} | [[Novell Storage Services|NSS]]
| [[Company:Novell|Novell]]
| 1998
| NetWare 5
|-
|{{rh}} | PolyServe File System (PSFS)
| PolyServe
| 1998
| [[Software:Windows|Windows]], [[Software:Linux|Linux]]
|-
|{{rh}} | ODS-5
| [[Company:Digital Equipment Corporation|DEC]]
| 1998
| [[Software:OpenVMS|OpenVMS]] V7.2
|-
|{{rh}} | [[Write Anywhere File Layout|WAFL]]
| [[Company:NetApp|NetApp]]
| 1998
| [[NetApp filer|Data ONTAP]]
|-
|{{rh}} | [[Ext3|ext3]]
| Stephen Tweedie
| 1999
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[ISO 9660:1999|1999]]
| Ecma International, ISO
| 1999
| [[Software:Microsoft Windows|Microsoft Windows]], [[Software:Linux|Linux]], "classic" Mac OS, [[Software:FreeBSD|FreeBSD]], and [[Software:AmigaOS|AmigaOS]]
|-
|{{rh}} | JFS
| [[Company:IBM|IBM]]
| 1999
| OS/2 Warp Server for e-business
|-
|{{rh}} | GFS
| Sistina ([[Company:Red Hat|Red Hat]])
| 2000
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[ReiserFS]]
| [[Company:Namesys|Namesys]]
| 2001
| [[Software:Linux|Linux]]
|-
|{{rh}} | zFS
| [[Company:IBM|IBM]]
| 2001
| z/OS (backported to OS/390)
|-
|{{rh}} | FATX
| [[Company:Microsoft|Microsoft]]
| 2002
| [[Engineering:Xbox|Xbox]]
|-
|{{rh}} | UFS2
| [[Biography:Marshall Kirk McKusick|Kirk McKusick]]
| 2002
| FreeBSD 5.0
|-
|{{rh}} | OCFS
| [[Company:Oracle Corporation|Oracle Corporation]]
| 2002
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[SquashFS]]
| Phillip Lougher, Robert Lougher
| 2002
| [[Software:Linux|Linux]]
|-
|{{rh}} | VMFS2
| [[Company:VMware|VMware]]
| 2002
| VMware ESX Server 2.0
|-
|{{rh}} | [[Software:Lustre (file system)|Lustre]]
| Cluster File Systems<ref>{{cite press release |title=Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System |location=Santa Clara, Calif. |date=12 September 2007 |publisher=Sun Microsystems, Inc. |url=http://www.sun.com/aboutsun/pr/2007-09/sunflash.20070912.2.xml |archive-url=https://web.archive.org/web/20071002091821/http://www.sun.com/aboutsun/pr/2007-09/sunflash.20070912.2.xml |archive-date=2 October 2007}}</ref>
| 2002
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Fossil (file system)|Fossil]]
| [[Organization:Bell Labs|Bell Labs]]
| 2003
| [[Software:Plan 9 from Bell Labs|Plan 9]] version 4
|-
|{{rh}} | [[Software:Google File System|Google File System]]
| [[Company:Google|Google]]
| 2003
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[ZFS]]
| [[Company:Sun Microsystems|Sun Microsystems]]
| 2004
| [[Software:Solaris (operating system)|Solaris]]
|-
|{{rh}} | [[Reiser4]]
| [[Company:Namesys|Namesys]]
| 2004
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Non-Volatile File System]]
| [[Company:Palm, Inc.|Palm, Inc.]]
| 2004
| Palm OS Garnet
|-
|{{rh}} | [[Software:BeeGFS|BeeGFS]]
|Fraunhofer/ [http://thinkparq.com/ ThinkParQ]
|2005
|[[Software:Linux|Linux]]
|-
|{{rh}} | [[GlusterFS]]
| Gluster Inc.
| 2005
| [[Software:Linux|Linux]]
|-
|{{rh}} | Minix V3 FS
| [[Biography:Andrew S. Tanenbaum|Andrew S. Tanenbaum]]
| 2005
| [[Software:MINIX 3|MINIX 3]]
|-
|{{rh}} | [[OCFS2]]
| [[Company:Oracle Corporation|Oracle Corporation]]
| 2005
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[NILFS]]
| [[Company:Nippon Telegraph and Telephone|NTT]]
| 2005
| [[Software:Linux|Linux]]
|-
|{{rh}} | VMFS3
| [[Company:VMware|VMware]]
| 2005
| VMware ESX Server 3.0
|-
|{{rh}} | GFS2
| [[Company:Red Hat|Red Hat]]
| 2006
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Ext4|ext4]]
| various <!-- but akpm is not one of them -->
| 2006
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[ExFAT|exFAT]]
| [[Company:Microsoft|Microsoft]]
| 2006
| Windows CE 6.0
|-
|{{rh}} | [[Btrfs]]
| Chris Mason
| 2007
| [[Software:Linux|Linux]]
|-
|{{rh}} | JXFS
| [[Company:Hyperion Entertainment|Hyperion Entertainment]]
| 2008
| AmigaOS 4.1
|-
|{{rh}} | [[HAMMER (file system)|HAMMER]]
| Matthew Dillon
| 2008
| [[Software:DragonFly BSD#2.0|DragonFly BSD 2.0]]
|-
|{{rh}} | LSFS
| [[Company:StarWind Software|StarWind Software]]
| 2009
| [[Software:Linux|Linux]], [[Software:FreeBSD|FreeBSD]], [[Software:Windows|Windows]]
|-
|{{rh}} | UniFS
| [[Company:Nasuni|Nasuni]]
| 2009
| Cloud
|-
|{{rh}} | CASL
| [[Company:Nimble Storage|Nimble Storage]]
| 2010
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Software:OrangeFS|OrangeFS]]
|Omnibond and others
|2011
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[VMware VMFS|VMFS5]]
| [[Company:VMware|VMware]]
| 2011
| vSphere 5.0+
|-
|{{rh}} | [[CHFS]]
| University of Szeged
| 2011
| [[Software:NetBSD|NetBSD]] 6.0+
|-
|{{rh}} | ReFS
| [[Company:Microsoft|Microsoft]]
| 2012
| [[Software:Windows Server 2012|Windows Server 2012]]
|-
|{{rh}} | [[F2FS]]
| [[Company:Samsung Electronics|Samsung Electronics]]
| 2012
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Bcachefs|bcachefs]]
| Kent Overstreet
| 2015
| [[Software:Linux|Linux]]
|-
|{{rh}} | APFS
| [[Company:Apple Inc.|Apple]]
| 2016
| [[Software:MacOS High Sierra|macOS High Sierra]], iOS 10.3
|-
|{{rh}} | [[Software:NOVA (filesystem)|NOVA]]
| [[Organization:University of California, San Diego|UC, San Diego]]
| 2017
| [[Software:Linux|Linux]]
|-
|{{rh}} | [[Software:Ceph|BlueStore/Cephfs]]
| [[Company:Red Hat|Red Hat]], [[Organization:University of California, Santa Cruz|University of California, Santa Cruz]]
|2017
|[[Software:Linux|Linux]]
|-
|{{rh}} | [[HAMMER2]]
| 2017
| [[Software:DragonFly BSD#5.0|DragonFly BSD 5.0]]
|-
|{{rh}} | [[EROFS]]
|[[Company:Huawei|Huawei]]<ref>{{Cite news|url=https://www.xda-developers.com/huawei-erofs-linux-file-system-android/|title=Huawei announces the EROFS Linux file system intended for Android devices|date=June 1, 2018|work=XDA Developer}}</ref>
|2018
|[[Software:Android (operating system)|Android]]
|}

<div style="overflow-x:auto"></div>

== Metadata ==
<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed; margin: 0;"
! File system
! Stores file owner
! [[POSIX]] file permissions
! Creation timestamps
! Last access/ read timestamps
! Last metadata change timestamps
! Last archive timestamps
! [[Access control list]]s
! Security/ [[Mandatory access control|MAC]] labels
! Extended attributes/ Alternate data streams/ forks
! Metadata [[Checksum|checksum]]/ [[Error correction code|ECC]]
! File system
|-
|{{rh}} | [[Bcachefs]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| [[Bcachefs]]
|-
|{{rh}} | [[Software:BeeGFS|BeeGFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| [[Software:BeeGFS|BeeGFS]]
|-
|{{rh}} | CP/M file system
| {{no}}
| {{no}}
| {{yes}}{{efn |Implemented in later versions as an extension}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| CP/M file system
|-
|{{rh}} | [[Engineering:DECtape|DECtape]]<ref>{{cite web
 | url = http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf
 | title = RT–11 Volume and File Formats Manual
 | publisher = Digital Equipment Corporation
 | date = August 1991
 | pages = 1–26 .. 1–32
}}</ref>
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Engineering:DECtape|DECtape]]
|-
|{{rh}} | Elektronika BK tape format
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| Elektronika BK
|-
|{{rh}} | Level-D
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}} <small>(date only)</small>
| {{yes}}
| {{yes}}
| {{yes}} <small>(FILDAE)</small>
| {{no}}
| {{no}}
| {{no}}
| Level-D
|-
|{{rh}} | [[Software:RT-11|RT-11]]<ref>{{cite web
 | url = http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf
 | title = RT–11 Volume and File Formats Manual
 | publisher = Digital Equipment Corporation
 | date = August 1991
 | pages = 1–4 .. 1–12
}}</ref>
| {{no}}
| {{no}}
| {{yes}} <small>(date only)</small>
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| [[Software:RT-11|RT-11]]
|-
|{{rh}} | Version 6 Unix file system (V6FS)<ref name="Unixv6">{{cite web
   | url=http://www.utdallas.edu/~venky/os/Proj/disk.pdf
   | title=Format of the Unix 6 file system
   | access-date=2016-02-21
   | archive-url=https://web.archive.org/web/20160921012843/http://www.utdallas.edu/~venky/os/Proj/disk.pdf
   | archive-date=2016-09-21
   | url-status=dead
   }}</ref>
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| Version 6 Unix file system (V6FS)
|-
|{{rh}} | Version 7 Unix file system (V7FS)<ref name="Unixv7">See dinode structure on page 355 (''FILESYS(5)'') of {{cite web
   | url=http://web.cuzuco.com/~cuzuco/v7/v7vol1.pdf
   | title= Unix Programmers Manual
   | publisher=Bell Telephone Laboratories
   | location=Murray Hill, New Jersey
   | edition=Seventh
   | date=January 1979
   | access-date=2016-02-21
   }}</ref>
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| Version 7 Unix file system (V7FS)
|-
|{{rh}} | [[ExFAT|exFAT]]
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[ExFAT|exFAT]]
|-
|{{rh}} | [[FAT12]]/[[FAT16]]/[[FAT32]]
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}{{efn |name=fat-ctime |Some FAT implementations, such as in Linux, show file modification timestamp (mtime) in the metadata change timestamp (ctime) field. This timestamp is however, not updated on file metadata change.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}{{efn |name=note-22 |Particular [[Installable File System]] drivers and [[Operating system|operating system]]s may not support extended attributes on FAT12 and FAT16. The OS/2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes (using a "EA&nbsp;DATA.&nbsp;SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.}}
| {{no}}
| [[FAT12]]/[[FAT16]]/[[FAT32]]
|-
|{{rh}} | [[High Performance File System|HPFS]]
| {{yes}}{{efn |name=note-14 |The ''f-node'' contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}}
| {{no}}
| [[High Performance File System|HPFS]]
|-
|{{rh}} | [[NTFS]]
| {{yes}}
| {{yes}}{{efn |name=note-5 |NTFS [[Access control list|access control list]]s can express any access policy possible using simple POSIX file permissions (and far more), but use of a POSIX-like interface is not supported without an add-on such as Services for UNIX or [[Software:Cygwin|Cygwin]].}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}{{efn |As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.<ref>{{cite web|url=https://docs.microsoft.com/en-us/windows/win32/secauthz/mandatory-integrity-control|title=Mandatory Integrity Control|website=[[Software:Microsoft Docs|Microsoft Docs]]|access-date=2022-08-14}}</ref>}}
| {{yes}}
| {{no}}
| [[NTFS]]
|-
|{{rh}} | ReFS
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS}}
| {{yes}}
| ReFS
|-
|{{rh}} | [[Hierarchical File System (Apple)|HFS]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| [[Hierarchical File System (Apple)|HFS]]
|-
|{{rh}} | [[HFS Plus]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{no}}
| [[HFS Plus]]
|-
|{{rh}} | FFS
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| FFS
|-
|{{rh}} | UFS1
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-33 |Access-control lists and MAC labels are layered on top of extended attributes.}}
| {{yes}}{{efn |name=note-33}}
| {{no}}{{efn |name=note-32 |Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).}}
| {{no}}
| UFS1
|-
|{{rh}} | UFS2
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-33}}
| {{yes}}{{efn |name=note-33}}
| {{yes}}
| {{partial}}
| UFS2
|-
|{{rh}} | [[HAMMER (file system)|HAMMER]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| [[HAMMER (file system)|HAMMER]]
|-
|{{rh}} | [[Log-structured File System (BSD)|LFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Log-structured File System (BSD)|LFS]]
|-
|{{rh}} | [[Extended file system|ext]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Extended file system|ext]]
|-
|{{rh}} | [[Xiafs]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Xiafs]]
|-
|{{rh}} | [[Ext2|ext2]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23 |Some [[Installable File System]] drivers and [[Operating system|operating system]]s may not support extended attributes, access control lists or security labels on these filesystems. Linux kernels prior to 2.6.x may either be missing support for these altogether or require a [[Patch (computing)|patch]].}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{no}}
| [[Ext2|ext2]]
|-
|{{rh}} | [[Ext3|ext3]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{no}}
| [[Ext3|ext3]]
|-
|{{rh}} | [[Ext4|ext4]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{partial}}{{efn | Metadata is mostly checksummed,<ref>{{cite web | title=Ext4 Disk Layout | url=https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Checksums}}</ref> however Direct/indirect/triple-indirect block maps are not protected by checksums<ref>{{cite web | title=Ext4 Metadata Checksums | url=https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums#Metadata_Not_Being_Upgraded}}</ref> }}
| [[Ext4|ext4]]
|-
|{{rh}} | [[Software:NOVA (filesystem)|NOVA]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| [[Software:NOVA (filesystem)|NOVA]]
|-
|{{rh}} | [[Software:Lustre (file system)|Lustre]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| [[Software:Lustre (file system)|Lustre]]
|-
|{{rh}} | [[F2FS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{no}}
| [[F2FS]]
|-
|{{rh}} | [[GPFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| [[GPFS]]
|-
|{{rh}} | GFS
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{no}}
| GFS
|-
|{{rh}} | [[NILFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| [[NILFS]]
|-
|{{rh}} | [[ReiserFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{no}}
| [[ReiserFS]]
|-
|{{rh}} | [[Reiser4]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Reiser4]]
|-
|{{rh}} | OCFS
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| OCFS
|-
|{{rh}} | [[OCFS2]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[OCFS2]]
|-
|{{rh}} | [[XFS]]
| {{yes}}
| {{yes}}
| {{partial}}{{efn |name=note-35 |Creation time stored since June 2015, xfsprogs version 3.2.3}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}{{efn |name=note-23}}
| {{yes}}
| {{yes}}
| [[XFS]]
|-
|{{rh}} | JFS
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| JFS
|-
|{{rh}} | [[QFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| [[QFS]]
|-
|{{rh}} | [[Be File System|BFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| [[Be File System|BFS]]
|-
|{{rh}} | [[AdvFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| [[AdvFS]]
|-
|{{rh}} | [[Novell Storage Services|NSS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-31 |The local time, time zone/[[UTC]] offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.}}
| {{yes}}{{efn |name=note-31}}
| {{yes}}
| {{yes}}{{efn |name=note-31}}
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |name=note-19 |Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.}}{{efn |name=note-29 |Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.}}
| {{no}}
 | [[Novell Storage Services|NSS]]
|-
|{{rh}} | [[NetWare File System|NWFS]]
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |name=note-31}}
| {{yes}}{{efn |name=note-31}}
| {{yes}}
| {{yes}}{{efn |name=note-31}}
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |name=note-19}}{{efn |name=note-29}}
| {{no}}
| [[NetWare File System|NWFS]]
|-
|{{rh}} | ODS-5
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |name=note-17 |Record Management Services (RMS) attributes include record type and size, among many others.}}
| {{no}}
| ODS-5
|-
|{{rh}} | APFS
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| APFS
|-
|{{rh}} | [[Veritas File System|VxFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{yes}}{{efn |name=note-23}}
| {{no}}
| [[Veritas File System|VxFS]]
|-
|{{rh}} | [[Universal Disk Format|UDF]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| [[Universal Disk Format|UDF]]
|-
|{{rh}} | [[Fossil (file system)|Fossil]]
| {{yes}}
| {{yes}}{{efn |name=note-61 |File permission in [[9P (protocol)|9P]] are a variation of the traditional Unix permissions with some minor changes, e.g. the suid bit is replaced by a new 'exclusive access' bit.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Fossil (file system)|Fossil]]
|-
|{{rh}} | [[ZFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-69 |Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.}}
| {{yes}}{{efn |name=note-60 |Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.}}
| {{yes}}
| [[ZFS]]
|-
|{{rh}} | [[Btrfs]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| [[Btrfs]]
|-
|{{rh}} | [[MINIX file system|Minix V1]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[MINIX file system|Minix V1]]
|-
|{{rh}} | [[MINIX file system|Minix V2]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[MINIX file system|Minix V2]]
|-
|{{rh}} | [[MINIX file system|Minix V3]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[MINIX file system|Minix V3]]
|-
|{{rh}} | VMFS2
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| VMFS2
|-
|{{rh}} | VMFS3
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| VMFS3
|-
|{{rh}} | [[ISO 9660:1988|1988]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[ISO 9660:1988|1988]]
|-
|{{rh}} | [[Rock Ridge]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn|Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.}}
| {{yes}}
| {{no}}
| {{no}}{{efn|[[Software:Libburnia|libburnia]] can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.}}
| {{no}}{{efn|name=note-78|[[Software:Libburnia|libburnia]] can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.}}
| {{no}}{{efn|name=note-78}}
| {{no}}
| [[Rock Ridge]]
|-
|{{rh}} | [[Joliet (file system)|Joliet ("CDFS")]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[Joliet (file system)|Joliet ("CDFS")]]
|-
|{{rh}} | [[ISO 9660:1999|1999]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[ISO 9660:1999|1999]]
|-
|{{rh}} | [[High Sierra Format|High Sierra]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| [[High Sierra Format|High Sierra]]
|-
|{{rh}} | [[SquashFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| [[SquashFS]]
|-
|{{rh}} | [[Software:Ceph|BlueStore/Cephfs]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| [[Software:Ceph|BlueStore/Cephfs]]
|-class="sortbottom"
! File system
! Stores file owner
! [[POSIX]] file permissions
! Creation timestamps
! Last access/read timestamps
! Last metadata change timestamps
! Last archive timestamps
! [[Access control list]]s
! Security/ [[Mandatory access control|MAC]] labels
! Extended attributes/ Alternate data streams/ forks
! Metadata [[Checksum|checksum]]/ [[Error correction code|ECC]]
! File system
|}</div>

== Features ==
===File capabilities===
<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed; margin: 0;"
! File system
! [[Hard link]]s
! [[Symbolic link]]s
! [[Journaling file system|Block journaling]]
! [[Journaling file system|Metadata-only journaling]]
! Case-sensitive
! Case-preserving
! File Change Log
! [[Execute in place|XIP]]
!Resident files (inline data)
|-
! [[Engineering:DECtape|DECtape]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
![[Software:BeeGFS|BeeGFS]]
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! Level-D
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Software:RT-11|RT-11]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! APFS
| {{yes}}
| {{yes}}
| {{dunno}}<!-- APFS utilizes copy-on-write, but details about the exact approach beyond that are very vague -->
| {{dunno}}<!-- APFS utilizes copy-on-write, but details about the exact approach beyond that are very vague -->
| {{maybe|Optional}}<!-- There are two variants of APFS, one that is case-sensitive, and one that is not. The non-case-sensitive variant is the default one for APFS in macOS 10.13+, while the case-sensitive variant is the default one for iOS 10.3+. -->
| {{yes}}
| {{dunno}}<!-- APFS utilizes copy-on-write, but details about the exact approach beyond that are very vague -->
| {{dunno}}
| {{dunno}}
|-
! Version 6 Unix file system (V6FS)
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! Version 7 Unix file system (V7FS)
| {{yes}}
| {{no}}{{efn |name=note-59 |System V Release 4, and some other [[Software:Unix|Unix]] systems, retrofitted symbolic links to their versions of the [[Software:Version 7 Unix|Version 7 Unix]] file system, although the original version didn't support them.}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[ExFAT|exFAT]]
| {{no}}
| {{no}}
| {{no}}
| {{partial}} (with [[Transaction-Safe FAT File System|TexFAT]] only)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[FAT12]]
| {{no}}
| {{no}}
| {{no}}
| {{partial}} (with TFAT12 only)
| {{no}}
| {{partial}} (with [[VFAT]] LFNs only)
| {{no}}
| {{no}}
| {{no}}
|-
! [[FAT16]]&nbsp;/ [[FAT16B]]&nbsp;/ [[FAT16X]]
| {{no}}
| {{no}}
| {{no}}
| {{partial}} (with TFAT16 only)
| {{no}}
| {{partial}} (with [[VFAT]] LFNs only)
| {{no}}
| {{no}}
| {{no}}
|-
! [[FAT32]]&nbsp;/ [[FAT32X]]
| {{no}}
| {{no}}
| {{no}}?
| {{partial}} (with TFAT32 only)
| {{no}}
| {{partial}} (with [[VFAT]] LFNs only)
| {{no}}
| {{no}}
| {{no}}
|-
! GFS
| {{yes}}
| {{yes}}{{efn |Context based symlinks were supported in GFS, GFS2 only supports standard symlinks since the bind mount feature of the Linux VFS has made context based symlinks obsolete}}
| {{yes}}
| {{yes}}{{efn |Optional journaling of data}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[High Performance File System|HPFS]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[NTFS]]
| {{yes}}
| {{no}}{{efn |name=note-37 |NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.}}
| {{yes}}{{efn |name=note-37}} (2000)
| {{yes}}{{efn |name=note-36 |While NTFS itself supports case sensitivity, the Win32 environment subsystem cannot create files whose names differ only by case for compatibility reasons. When a file is opened for writing, if there is any existing file whose name is a case-insensitive match for the new file, the existing file is truncated and opened for writing instead of a new file with a different name being created. Other subsystems like e. g. Services for Unix, that operate directly above the kernel and not on top of Win32 can have case-sensitivity.}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes|[[NTFS#Resident vs. non-resident attributes|Yes]]}} (approximately 700 bytes)
|-
! [[HFS Plus]]
| {{yes}}<ref>{{cite web|last1=Siracusa|first1=John|title=Mac OS X 10.7 Lion: the Ars Technica review|url=https://arstechnica.com/gadgets/2011/07/mac-os-x-10-7/12/#hfs-problems|website=Ars Technica|access-date=14 December 2017|quote=To keep track of hard links, HFS+ creates a separate file for each hard link inside a hidden directory at the root level of the volume.|date=2011-07-20}}</ref>
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-48 |Metadata-only journaling was introduced in the Mac OS X 10.2.2 HFS Plus driver; journaling is enabled by default on Mac OS X 10.3 and later.}}
| {{maybe|Optional}}{{efn |Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS X 10.3 on the command ''newfs_hfs -s'' will create a case-sensitive new file system.<ref>{{man|8|newfs_hfs|Darwin}}</ref> HFS Plus version 5 optionally supports case-sensitivity. However, since case-sensitivity is fundamentally different from case-insensitivity, a new signature was required so existing HFS Plus utilities would not see case-sensitivity as a file system error that needed to be corrected. Since the new signature is 'HX', it is often believed this is a new filesystem instead of a simply an upgraded version of HFS Plus.<ref>{{cite web |publisher=Apple |url=https://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Articles/Comparisons.html |title=File System Comparisons |archive-url=https://web.archive.org/web/20081006205615/https://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Articles/Comparisons.html |archive-date=2008-10-06 |url-status=dead}} (hasn't been updated to discuss HFSX)</ref><ref>{{cite web |publisher=Apple |url=https://developer.apple.com/library/archive/technotes/tn/tn1150.html |title=Technical Note TN1150: HFS Plus Volume Format}} (Very technical overview of HFS Plus and HFSX.)</ref>}}
| {{yes}}
| {{yes}}{{efn |Mac OS X Tiger (10.4) and late versions of Panther (10.3) provide file change logging (it's a feature of the file system software, not of the volume format, actually).<ref>{{Cite web |url=http://www.kernelthread.com/software/fslogger/ |title=fslogger |access-date=2006-08-03 |archive-url=https://web.archive.org/web/20080918004451/http://www.kernelthread.com/software/fslogger/ |archive-date=2008-09-18 |url-status=dead }}</ref>}}
| {{no}}
| {{dunno}}
|-
! FFS
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! UFS1
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! UFS2
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-66 |"Soft dependencies" (softdep) in [[Software:NetBSD|NetBSD]], called "[[Soft updates|soft updates]]" in [[Software:FreeBSD|FreeBSD]] provide meta-data consistency at all times without double writes ([[Journaling file system|journaling]])}} <ref>{{cite web|url=https://www.mckusick.com/softdep/suj.pdf|title=Journaled Soft-updates|first1=Marshall Kirk|last1=McKusick|first2=Jeff|last2=Roberson}}</ref> {{efn|Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE <ref>{{Cite web | url=https://wiki.freebsd.org/NewFAQs |title = NewFAQs - FreeBSD Wiki}}</ref><ref>{{Cite web | url=https://www.freebsd.org/releases/9.0R/announce.html | title=FreeBSD 9.0-RELEASE Announcement}}</ref>}}
| {{yes}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{no}}
|-
! [[HAMMER (file system)|HAMMER]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}} <!-- probably no? -->
| {{no}}
| {{dunno}}
|-
! [[Log-structured File System (BSD)|LFS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-38 |UDF, LFS, and NILFS are [[Log-structured file system|log-structured file system]]s and behave as if the entire file system were a journal.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Extended file system|ext]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Xiafs]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Ext2|ext2]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn |name=note-65 |Linux kernel versions 2.6.12 and newer.}}
| {{dunno}}
|-
! [[Ext3|ext3]]
| {{yes}}
| {{yes}}
| {{yes}} (2001) {{efn |name=note-62 |Off by default.}}
| {{yes}} (2001)
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
|-
! [[Ext4|ext4]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-62}}
| {{yes}}
| {{yes}}, optional <ref>{{cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=EXT4-Case-Insensitive-Linux-5.2|title=EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2}}</ref>
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}} (approximately 160 bytes)<ref>{{Cite web |title=2. High Level Design — The Linux Kernel documentation § 2.10. Inline Data |url=https://www.kernel.org/doc/html/latest/filesystems/ext4/overview.html#inline-data |access-date=2022-12-24 |website=www.kernel.org}}</ref>
|-
! [[Software:NOVA (filesystem)|NOVA]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
|-
! [[F2FS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-38}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Software:Lustre (file system)|Lustre]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-62}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{dunno}}
|-
! [[NILFS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-38}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[ReiserFS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-44 |Full block journaling for ReiserFS was added to Linux 2.6.8.}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Reiser4]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! OCFS
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[OCFS2]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[XFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-40 |Optionally no on IRIX and Linux.}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
|-
! JFS
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}} (1990)
| {{yes}}{{efn |name=note-30 |Particular [[Installable File System]] drivers and [[Operating system|operating system]]s may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[QFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Be File System|BFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{dunno}}
|-
! [[Novell Storage Services|NSS]]
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}{{efn |name=note-20 |Case-sensitivity/Preservation depends on client. Windows, DOS, and OS/2 clients don't see/keep case differences, whereas clients accessing via NFS or AFP may.}}
| {{yes}}{{efn |name=note-20}}
| {{yes}}{{efn |name=note-6 |The file change logs, last entry change timestamps, and other filesystem metadata, are all part of the extensive suite of auditing capabilities built into NDS/eDirectory called NSure Audit.<ref>{{cite web |url=http://www.novell.com/documentation/nsureaudit/html/netware_event_data.htm |title=Filesystem Events tracked by NSure}}</ref>}}
| {{no}}
| {{dunno}}
|-
! [[NetWare File System|NWFS]]
| {{yes}}{{efn |name=note-53 |Available only in the "NFS" namespace.}}
| {{yes}}{{efn |name=note-53}}
| {{no}}
| {{no}}
| {{yes}}{{efn |name=note-20}}
| {{yes}}{{efn |name=note-20}}
| {{yes}}{{efn |name=note-6}}
| {{no}}
| {{dunno}}
|-
! ODS-2
| {{yes}}
| {{yes}}{{efn |name=note-18 |These are referred to as "aliases".}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{dunno}}
|-
! ODS-5
| {{yes}}
| {{yes}}{{efn |name=note-18}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
|-
! [[Universal Disk Format|UDF]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-38}}
| {{yes}}{{efn |name=note-38}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}<ref>{{cite web |url=http://www.osta.org/specs/pdf/udf260.pdf |title=Universal Disk Format Specification – Revision 2.60 |page=34 |quote=This file, when small, can be embedded in the [Information Control Block] that describes it.}}</ref>
|-
! [[Veritas File System|VxFS]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
|-
! [[Fossil (file system)|Fossil]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{dunno}}
|-
! [[ZFS]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-56 |ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.}}
| {{no}}{{efn |name=note-56}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Btrfs]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |name=note-80 |Btrfs is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. It keeps track of last five transactions and uses checksums to find problematic drives, making write intent logs unnecessary.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! [[Bcachefs]]
| {{yes}}
| {{yes}}
| {{yes}}{{efn |Bcachefs is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. Journal commits are fairly expensive operations as they require issuing FLUSH and FUA operations to the underlying devices. By default, a journal flush is issued one second after a filesystem update has been done, which primarily records btree updates ordered by when they occured. This option may be useful on a personal workstation or laptop, and perhaps less appropriate on a server.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! [[MINIX file system|Minix V1]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[MINIX file system|Minix V2]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[MINIX file system|Minix V3]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! VMFS2
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! VMFS3
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! ReFS
| {{yes}}{{efn | Since Windows 10 Enterprise Insider Preview build 19536}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{yes}}{{efn |name=note-36}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! [[ISO 9660]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Rock Ridge]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Joliet (file system)|Joliet ("CDFS")]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[SquashFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[Software:Ceph|BlueStore/Cephfs]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
|- class="sortbottom"
! File system
! [[Hard link]]s
! [[Symbolic link]]s
! [[Journaling file system|Block journaling]]
! [[Journaling file system|Metadata-only journaling]]
! Case-sensitive
! Case-preserving
! File Change Log
! [[Execute in place|XIP]]
!Resident files
|}</div>

===Block capabilities===
Note that in addition to the below table, block capabilities can be implemented below the file system layer in Linux ([[Software:Logical Volume Manager (Linux)|LVM]], {{proper name|integritysetup}}, [[Software:Dm-crypt#cryptsetup|cryptsetup]]) or Windows (Volume Shadow Copy Service, [[SECURITY.BIN|SECURITY]]), etc.
<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed; margin: 0;"
! File system
! Internal snapshotting / branching
! [[Filesystem-level encryption|Encryption]]
! [[Data deduplication|Deduplication]]
! Data [[Checksum|checksum]]/ [[Error correction code|ECC]]
! [[Cache (computing)|Persistent Cache]]
! Multiple Devices
! [[Data compression|Compression]]
! Self-healing{{efn |name=note-82|A file system is self-healing if its capable to proactively autonomously detect and correct all but grave errors, faults and corruptions online both in internal metadata AND data. See US7694191B1 as example. This usually requires full checksumming as well as internal redundancy as well as corresponding logic.}}
|-
! [[Engineering:DECtape|DECtape]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
![[Software:BeeGFS|BeeGFS]]
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! Level-D
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:RT-11|RT-11]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! APFS
| {{yes}}
| {{yes}}
| {{yes}} <ref>{{cite web |url=http://www.manpagez.com/man/2/clonefile/ |title=clonefile(2) | quote=The cloned file dst shares its data blocks with the src file [..]}}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! Version 6 Unix file system (V6FS)
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! Version 7 Unix file system (V7FS)
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[ExFAT|exFAT]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[FAT12]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{partial}}{{efn |name=FATcompress|only inside of Stacker 3/4 and DriveSpace 3 compressed volumes<ref name="DMSDOS">{{cite web |title=DMSDOS CVF module |type=dmsdoc.doc |version=0.9.2.0 |date=1998-11-19 |url=http://cmp.felk.cvut.cz/~pisa/dmsdos/dmsdos.html |access-date=2016-11-01 |url-status=live |archive-url=https://web.archive.org/web/20161102123812/http://cmp.felk.cvut.cz/~pisa/dmsdos/dmsdos.html |archive-date=2016-11-02 |quote=Usually all data for one cluster are stored in contiguous sectors, but if the filesystem is too fragmented there may not be a 'free hole' that is large enough for the data. […] Drivespace 3 and Stacker know a hack for that situation: they allow storing the data of one cluster in several fragments on the disk.}}</ref>}}
| {{no}}
|-
! [[FAT16]]&nbsp;/ [[FAT16B]]&nbsp;/ [[FAT16X]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{partial}}{{efn |name=FATcompress}}
| {{no}}
|-
! [[FAT32]]&nbsp;/ [[FAT32X]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! GFS
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[High Performance File System|HPFS]]
| {{dunno}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[NTFS]]
| {{no}}
| {{yes}}
| {{yes}}{{efn |name=note-NTFS-Dedup |Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.}}<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/hh769303(v=vs.85).aspx|title=About Data Deduplication}}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! [[HFS Plus]]
| {{no}}
| {{no}}{{efn |name=note-77 |HFS+ does not actually encrypt files: to implement [[Software:FileVault|FileVault]], OS X creates an HFS+ filesystem in a sparse, encrypted disk image that is automatically mounted over the home directory when the user logs in.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! FFS
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! UFS1
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! UFS2
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[HAMMER (file system)|HAMMER]]
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Log-structured File System (BSD)|LFS]]
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Extended file system|ext]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Xiafs]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Ext2|ext2]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Ext3|ext3]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Ext4|ext4]]
| {{no}}
| {{yes}}, experimental <ref name="note-67">{{cite web |url=https://lwn.net/Articles/639427/ |title=Ext4 encryption}}</ref>
| {{no}}
| {{no}}<ref name="redhat-ext4andxfsnobitrotprotection" />
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:NOVA (filesystem)|NOVA]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! [[F2FS]]
| {{no}}
| {{yes}}, experimental <ref name="note-68">{{cite web |url=https://lwn.net/Articles/677620/ |title=F2FS encryption}}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! [[Software:Lustre (file system)|Lustre]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! [[NILFS]]
| {{yes}}, continuous{{efn |name=note-38}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[ReiserFS]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Reiser4]]
| {{dunno}}
| {{yes}}{{efn |name=note-50 |Reiser4 supports transparent compression and encryption with the ''cryptcompress'' plugin which is the default file handler in version 4.1.}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! OCFS
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[OCFS2]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[XFS]]
| {{no}}
| {{no}}
| {{yes}}<ref>{{cite web |url=https://manpages.debian.org/bullseye/xfsprogs/mkfs.xfs.8.en.html|title=mkfs.xfs(8) from xfsprogs 5.10.0-4|quote=By default, mkfs.xfs [..] will enable the reflink [=deduplication] feature. }}</ref>
| {{no}}<ref name="redhat-ext4andxfsnobitrotprotection">{{cite web | title=Red Hat: What is bitrot? | url=https://www.redhat.com/en/blog/what-bit-rot-and-how-can-i-detect-it-rhel}}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! JFS
| {{dunno}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{yes2}} only in JFS1 on AIX<ref>{{cite web |title=JFS data compression |publisher=IBM |url=https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/devicemanagement/jfsdatacomp.html |access-date=2020-07-26}}</ref>
| {{no}}
|-
! [[QFS]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Be File System|BFS]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Novell Storage Services|NSS]]
| {{yes}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! [[NetWare File System|NWFS]]
| {{dunno}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! ODS-2
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! ODS-5
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Universal Disk Format|UDF]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Veritas File System|VxFS]]
| {{yes}}{{efn |name=note-70 |VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.}}
| {{no}}
| {{Yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Fossil (file system)|Fossil]]
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! [[ZFS]]
| {{yes}}
| {{yes}}{{efn |name=zfscrypt |Applies to proprietary ZFS release 30 and ZFS On Linux. Encryption support is not yet available in all [[Organization:OpenZFS|OpenZFS]] ports.<ref>{{cite web|title=How to Manage ZFS Data Encryption|url=https://www.oracle.com/technical-resources/articles/solaris/manage-zfs-encryption.html|first=Darren|last=Moffat|date=July 2012|access-date=2022-08-14}}</ref><ref>{{cite web|title=Release zfs-0.8.0|website=[[GitHub]]|url=https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0|date=2020-01-21}}</ref><ref>{{cite web|title=Feature Flags - OpenZFS|url=http://open-zfs.org/wiki/Feature_Flags}}</ref>}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}{{efn | [[LZJB]] (optimized for performance while providing decent data compression)<br>[[Software:LZ4 (compression algorithm)|LZ4]] (faster & higher ratio than lzjb)<br>[[Software:Gzip|gzip]] levels: 1 (fastest) to 9 (best), default is 6<br>[[Software:Zstd|zstd]] positive: 1 (fastest) to 19 (best), default is 3<br>zstd negative: 1(best & default)-10, 20, 30, …, 100, 500, 1000(fastest)<br>zle: compresses runs of zeros.<ref>{{cite web|url=https://openzfs.github.io/openzfs-docs/man/master/7/zfsprops.7.html|title=zfsprops.7 — OpenZFS documentation|website=[[GitHub]]|date=2023-08-26|accessdate=2023-09-14}}</ref>}}
| {{yes}}
|-
! [[Btrfs]]
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}{{efn | disabling copy-on-write (COW) to prevent fragmentation also disables data checksumming}}
| {{no}}
| {{yes}}
| {{yes}}{{efn | [[Software:Zlib|zlib]] levels: 1 to 9, default is 3<br>[[Software:Lempel–Ziv–Oberhumer|LZO]] (no levels) faster than ZLIB, worse ratio<br>[[Software:Zstd|zstd]] levels: 1 to 15 (higher levels are not available)<ref>{{cite web|url=https://btrfs.readthedocs.io/en/latest/Compression.html|title=Compression — BTRFS documentation|website=[[GitHub]]|date=2023-07-26|accessdate=2023-09-14}}</ref>}}
| {{yes}}
|-
! [[Bcachefs]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}{{efn | none<br>[[Cyclic redundancy check#Standards and common use|CRC-32C]]&nbsp;(default)<br>crc64<br>chacha20/poly1305 (When encryption is enabled. Encryption can only be specified for the entire filesystem, not per file or directory)<ref name="b.PoO">{{cite web |last1=Overstreet |first1=Kent |title=bcachefs: Principles of Operation |url=https://bcachefs.org/bcachefs-principles-of-operation.pdf |access-date=10 May 2023 |date=18 Dec 2021}}</ref>}}
| {{no}}
| {{yes}}
| {{yes}}{{efn | none (default)<br>The three currently supported algorithms are [[Software:Gzip|gzip]], [[Software:LZ4 (compression algorithm)|LZ4]], [[Software:Zstd|zstd]].<br>The compression level may also be optionally specified, as an integer between 0 and 15, e.g. lz4:15. 0 specifies the default compression level, 1 specifies the fastest and lowest compression ratio, and 15 the slowest and best compression ratio.<ref>{{cite web |title= bcachefs/ Compression |url=https://bcachefs.org/Compression/ |access-date=14 Jan 2024 |date=11 Sep 2023}}</ref>}}
| {{no}}
|-
! [[MINIX file system|Minix V1]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[MINIX file system|Minix V2]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[MINIX file system|Minix V3]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! VMFS2
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! VMFS3
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! ReFS
| {{dunno}}
| {{no}}
| {{yes}}
| {{yes}}{{efn |By using the per-file "integrity stream" that internally stores a checksum per cluster. Those per cluster checksums are not accessible so it is actually a per file feature and not a per block feature. Integrity streams are not enabled by default.}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! [[ISO 9660]]
| {{no}}
| {{no}}
| {{no}}{{efn|name=note-79|Some file system creation implementations reuse block references and support deduplication this way.  This is not supported by the standard, but usually works well due to the file system's read-only nature.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Rock Ridge]]
| {{no}}
| {{no}}
| {{no}}{{efn|name=note-79}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Joliet (file system)|Joliet ("CDFS")]]
| {{no}}
| {{no}}
| {{no}}{{efn|name=note-79}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[SquashFS]]
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! [[Software:Ceph|BlueStore/Cephfs]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|- class="sortbottom"
! File system
! Internal snapshotting / branching
! [[Filesystem-level encryption|Encryption]]
! [[Data deduplication|Deduplication]]
! Data [[Checksum|checksum]]/ [[Error correction code|ECC]]
! [[Cache (computing)|Persistent Cache]]
! Multiple Devices
! [[Data compression|Compression]]
! Self-healing{{efn |name=note-82}}
|}</div>

===Resize capabilities===
"Online" and "offline" are synonymous with "mounted" and "not mounted".

{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed;"
|-
!scope="col"|File system
!scope="col"|Host OS
!scope="col"|Offline grow
!scope="col"|Online grow
!scope="col"|Offline shrink
!scope="col"|Online shrink
!scope="col"|Add and remove physical volumes
|-
!scope="row"|[[FAT16]]&nbsp;/ [[FAT16B]]&nbsp;/ [[FAT16X]]
|misc.
|{{yes}}{{efn|name="libparted"|With software based on [[Software:GNU Parted|GNU Parted]].}}
|{{no}}
|{{yes}}{{efn|name="libparted"}}
|{{no}}
|{{no}}
|-
!scope="row"|[[FAT32]]&nbsp;/ [[FAT32X]]
|misc.
|{{yes}}{{efn|name="libparted"}}
|{{no}}
|{{yes}}{{efn|name="libparted"}}
|{{no}}
|{{no}}
|-
!scope="row"|[[ExFAT|exFAT]]
|misc.
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[NTFS]]
|Windows
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|-
!scope="row"|ReFS
|Windows
|{{dunno}}
|{{yes}}
|{{dunno}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Hierarchical File System (Apple)|HFS]]
|macOS
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[HFS Plus|HFS+]]
|macOS
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|-
!scope="row"|APFS
|macOS
|{{dunno}}
|{{dunno}}
|{{dunno}}
|{{dunno}}
|{{dunno}}
|-
!scope="row"|[[SquashFS]]
|Linux
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Software:NOVA (filesystem)|NOVA]]
|Linux
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[JFS (file system)|JFS]]<ref>{{cite web|url=https://www.kernel.org/doc/Documentation/filesystems/jfs.txt|title=IBM's Journaled File System (JFS) for Linux}}</ref>
|Linux
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[XFS]]<ref>{{cite web|url=https://docs.oracle.com/cd/E37670_01/E37355/html/ol_grow_xfs.html|title=Growing an XFS File System}}</ref>
|Linux
|{{no}}
|{{yes}}
|{{no}}<ref name="xfs-shrink">{{Cite web |date=2022-07-17 |title=Shrinking Support - xfs.org |url=http://xfs.org/index.php/Shrinking_Support |url-status=dead |archive-url=https://web.archive.org/web/20220717073119/http://xfs.org/index.php/Shrinking_Support |archive-date=2022-07-17 |access-date=2022-12-18 |website=XFS Wiki}}</ref>
|{{no}}<ref name="xfs-shrink" />
|{{no}}
|-
!scope="row"|[[Software:Lustre (file system)|Lustre]]<ref name="wiki-faq-old">{{cite web|url=http://wiki.lustre.org/Frequently_Asked_Questions_(Old_Wiki)|title=Frequently Asked Questions (Old Wiki)|access-date=5 May 2018}}</ref>
|Linux
|{{dunno}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|-
!scope="row"|[[F2FS]]<ref>{{Cite web | url=https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/ |title = Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem}}</ref>
|Linux
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[NTFS]]<ref>{{cite web|url=http://linux.die.net/man/8/ntfsresize|title=<code>ntfsresize(8)</code>}}</ref>
|Linux
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Ext2|ext2]]<ref name="unix.com">{{man|8|resize2fs|Linux}}</ref>
|Linux
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Ext3|ext3]]<ref name="unix.com"/>
|Linux
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[ReiserFS]]<ref>{{cite web|url=https://www.suse.com/documentation/sles11/stor_admin/data/biuymaa.html|title=Resizing File Systems}}</ref>
|Linux
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Reiser4]]<ref>{{cite web|url=https://reiser4.wiki.kernel.org/index.php/Resize_reiserfs|title=Resize reiserfs|website=Reiserfs wiki}}</ref>
|Linux
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Ext4|ext4]]<ref name="unix.com"/>
|Linux
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|-
!scope="row"|[[Btrfs]]<ref>{{cite web|title=Just Enough Operating System (JeOS): Technical Information {{!}} SUSE|url=https://www.suse.com/products/server/technical-information/|website=www.suse.com|access-date=28 April 2018|language=en}}</ref>
|Linux
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
!scope="row"|[[Bcachefs]]<ref name="b.PoO"/>
|Linux
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|-
!scope="row"|[[NILFS]]<ref>{{cite web|url=http://nilfs.sourceforge.net/en/man8/nilfs-resize.8.html|title=<code>nilfs-resize(8)</code>}}</ref>
|Linux
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|-
!scope="row"|[[ZFS]]
|misc.
|{{no}}
|{{yes}}
|{{no}}
|{{partial}}<ref>Mirror and single-disk vdevs can be wholly removed from a pool, but not RAID-Z vdevs. {{cite web|title=OpenZFS 7614 - zfs device evacuation/removal|website=[[GitHub]]|url=https://github.com/zfsonlinux/zfs/pull/6900}}</ref>
|{{yes}}
|-
!scope="row"|[[JFS (file system)|JFS2]]
|[[Software:AIX|AIX]]
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|-
!scope="row"|UFS2<ref>{{cite web|url=https://www.freebsd.org/doc/handbook/disks-growing.html|title=Resizing and Growing Disks}}</ref>
|FreeBSD
|{{yes}}
|{{yes}} (FreeBSD 10.0-RELEASE or later)
|{{no}}
|{{no}}
|{{no}}
|-
!scope="row"|[[HAMMER (file system)|HAMMER]]
|DragonflyBSD
|{{dunno}}
|{{dunno}}
|{{dunno}}
|{{dunno}}
|{{dunno}}
|-
!scope="row"|[[Software:Ceph|BlueStore/Cephfs]]
|Linux
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|}

=== Allocation and layout policies ===
<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed;"
! File system
![[Sparse file]]s
![[Block suballocation]]<!-- was Block fragmentation -->
! Tail packing
! [[Extent (file systems)|Extents]]
! Variable file block size{{efn |name=note-41 |Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to [[Extent (file systems)|extents]] but a slightly different implementational choice.) The current implementation in UFS2 is read-only.}}
! [[Allocate-on-flush]]<!-- was Delayed allocation -->
! Copy on write
! [[Engineering:Trim (computing)|Trim]] support
|-
! [[Engineering:DECtape|DECtape]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
![[Software:BeeGFS|BeeGFS]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
|-
! Level-D
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
|-
! APFS
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{yes}}<ref>{{cite web |url=http://www.zdnet.com/article/wwdc-2017-macoss-new-file-system/|title=Mac users, meet APFS: macOS's new file system - ZDNet|website=[[ZDNet]]}}</ref><ref>{{cite web |url=https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html|title=Apple File System Guide - FAQ}}</ref>
|-
! Version 6 Unix file system (V6FS)
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
|-
! Version 7 Unix file system (V7FS)
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
|-
! [[ExFAT|exFAT]]
| {{no}}
| {{no}}
| {{no}}
| {{partial}} (only if the file fits into one contiguous block range)
| {{no}}
| {{no}}
| {{no}}
| {{yes}} (Linux)
|-
! [[FAT12]]
| {{partial}} (only inside of compressed volumes)<ref name="CVF808"/>
| {{partial}} (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes<ref name="DMSDOS"/>)
| {{no}}
| {{partial}} (only inside of compressed volumes)<ref name="CVF814"/>
| {{no}}
| {{no}}
| {{no}}
| {{yes}} (Linux)
|-
! [[FAT16]]&nbsp;/ [[FAT16B]]&nbsp;/ [[FAT16X]]
| {{partial}} (only inside of compressed volumes)<ref name="CVF808">{{cite web|url=http://www.techhelpmanual.com/808-cvf_region__mdfat.html|title=CVF Region: MDFAT}}</ref>
| {{partial}} (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes<ref name="DMSDOS"/>)
| {{no}}
| {{partial}} (only inside of compressed volumes)<ref name="CVF814">{{cite web|url=http://www.techhelpmanual.com/814-mapping_dos_fat_to_mdfat.html|title=Mapping DOS FAT to MDFAT}}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{yes}} (Linux)
|-
! [[FAT32]]&nbsp;/ [[FAT32X]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}} (Linux)
|-
! GFS
| {{yes}}
| {{no}}
| {{partial}}{{efn |Only for "stuffed" inodes}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}}
|-
! [[High Performance File System|HPFS]]
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} (Linux)
|-
! [[NTFS]]
| {{yes}}
| {{partial}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} (NT 6.1+; Linux)
|-
! [[HFS Plus]]
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} (macOS)
|-
! FFS
| {{yes}}
| {{yes2}} 8:1{{efn |name=note-45 |Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
|-
! UFS1
| {{yes}}
| {{yes2}} 8:1{{efn |name=note-45}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
|-
! UFS2
| {{yes}}
| {{yes2}} 8:1{{efn |name=note-45}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{yes}}<ref>{{Cite web | url=https://svnweb.freebsd.org/base?view=revision&revision=216796 |title = &#91;base&#93; Revision 216796}}</ref><ref>{{Cite web | url=https://www.freebsd.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+8.4-RELEASE |title = Newfs(8)}}</ref>
|-
! [[Log-structured File System (BSD)|LFS]]
| {{yes}}
| {{yes2}} 8:1{{efn |name=note-45}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{dunno}}
|-
! [[Extended file system|ext]]
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Xiafs]]
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Ext2|ext2]]
| {{yes}}
| {{no}}{{efn |name=note-47 |Fragments were planned, but never actually implemented on ext2 and ext3.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! [[Ext3|ext3]]
| {{yes}}
| {{no}}{{efn |name=note-47}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! [[Ext4|ext4]]
| {{yes}}
| {{no}}{{efn |name=note-47}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
|-
! [[Software:NOVA (filesystem)|NOVA]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{dunno}}
|-
! [[F2FS]]
| {{yes}}
| {{no}}
| {{no}}
| {{partial}}{{efn |name=note-75 | Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}<ref>{{cite mailing list |url=https://lkml.org/lkml/2014/09/23/32 |title=[PATCH 2/3] f2fs: Introduce FITRIM in f2fs_ioctl |author=Jaeguk Kim |mailing-list=linux-kernel |date=2014-09-22}}</ref>
|-
! [[Software:Lustre (file system)|Lustre]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
|-
! [[NILFS]]
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}} (Linux NILFS2)
|-
! [[ReiserFS]]
| {{yes}}
| {{yes}}{{efn |name=note-73 |Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Reiser4]]
| {{yes}}
| {{yes}}{{efn |name=note-73}}
| {{yes}}
| {{yes}}{{efn |name=note-39 |In "extents" mode.}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{maybe|Testing}}<ref>{{cite web |title=Reiser4 discard support |url=https://reiser4.wiki.kernel.org/index.php/Reiser4_discard_support |website=Reiser4 FS Wiki}}</ref>
|-
! OCFS
| {{dunno}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[OCFS2]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} (Linux)
|-
! [[XFS]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}, on request<ref>{{cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=XFS-Linux-4.9-Shared-Extents|title=XFS Adds Shared Data Extents For Linux 4.9}}</ref>
| {{yes}} (Linux)
|-
! [[JFS (file system)|JFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} (Linux)
|-
! [[QFS]]
| {{dunno}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Be File System|BFS]]
| {{dunno}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}} ([[Software:Haiku (operating system)|Haiku]])
|-
! [[Novell Storage Services|NSS]]
| {{dunno}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
|-
! [[NetWare File System|NWFS]]
| {{dunno}}
| {{yes}}{{efn |name=note-42 |Each possible size (in sectors) of file tail has a corresponding suballocation block chain in which all the tails of that size are stored. The overhead of managing suballocation block chains is usually less than the amount of block overhead saved by being able to increase the block size but the process is less efficient if there is not much free disk space.}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! ODS-5
| {{dunno}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Veritas File System|VxFS]]
| {{yes}}
| {{dunno}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[Universal Disk Format|UDF]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{dunno}}{{efn |name=note-46 |Depends on UDF implementation.}}
| {{yes}}, for [[Engineering:Write once read many|write once read many]] media
| {{no}}
|-
! [[Fossil (file system)|Fossil]]
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! [[ZFS]]
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! [[Btrfs]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! [[Bcachefs]]
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{dunno}}
|-
! VMFS2
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! VMFS3
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
|-
! ReFS
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{dunno}}
| {{yes}}
| {{yes}} (NT 6.1+)
|-
! [[ISO 9660]]
| {{no}}
| {{no}}
| {{no}}
| {{yes}}{{efn|name=note-81|ISO 9660 Level 3 only}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Rock Ridge]]
| {{no}}
| {{no}}
| {{no}}
| {{yes}}{{efn|name=note-81}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Joliet (file system)|Joliet ("CDFS")]]
| {{no}}
| {{no}}
| {{no}}
| {{yes}}{{efn|name=note-81}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[SquashFS]]
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:Ceph|BlueStore/Cephfs]]
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{yes}}
| {{yes}}
|-class="sortbottom"
! File system
![[Sparse file]]s
![[Block suballocation]]<!-- was Block fragmentation -->
! Tail packing
! [[Extent (file systems)|Extents]]
! Variable file block size{{efn |name=note-41}}
! [[Allocate-on-flush]]<!-- was Delayed allocation -->
! Copy on write
! [[Engineering:Trim (computing)|Trim]] support
|}
</div>

== OS support ==
<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed; margin: 0;"
! File system
! [[Engineering:DOS|DOS]]
! [[Software:Linux|Linux]]
! [[Software:MacOS|macOS]]
! Windows&nbsp;9x (historic)
! [[Software:Microsoft Windows|Windows]] (current)
! [[Software:Classic Mac OS|Classic]]<br>[[Software:Classic Mac OS|Mac OS]]
! [[Software:FreeBSD|FreeBSD]]
! OS/2
! [[Software:BeOS|BeOS]]
! [[Software:Minix|Minix]]
! [[Software:Solaris (operating system)|Solaris]]
! z/OS
! [[Software:Android (operating system)|Android]]<wbr/><ref>{{cite tech report |type=Documentation |title=Android Kernel File System Support |publisher=Android Open Source Project |access-date=2023-01-11 |url=https://source.android.com/docs/core/architecture/android-kernel-file-system-support}}</ref>
|-
! APFS
| {{no}}
| {{partial}} (read-only with apfs-fuse<ref>{{Cite web | url=https://github.com/sgan81/apfs-fuse |title = GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)|website = [[GitHub]]|date = 2020-01-18}}</ref> or linux-apfs<ref>{{Cite web | url=https://github.com/eafer/linux-apfs |title = APFS module for linux, with experimental write support. This tree is just for development, please use linux-apfs-oot instead.: Linux-apfs/Linux-apfs|website = [[GitHub]]|date = 2019-12-14}}</ref>)
| {{yes}} <br />(Since macOS Sierra)
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:BeeGFS|BeeGFS]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
|-
! [[Engineering:DECtape|DECtape]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! Level-D
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Software:RT-11|RT-11]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! Version 6 Unix file system (V6FS)
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! Version 7 Unix file system (V7FS)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
|-
! [[ExFAT|exFAT]]
| {{no}}
| {{yes}} (since 5.4,<ref>{{cite mailing list |mailing-list=linux-kernel |author=Namjae Jeon |title=[PATCH v12 00/13] add the latest exfat driver |url=https://lkml.org/lkml/2020/1/20/420 |date=20 January 2020 |access-date=18 December 2021 }}</ref> available as a kernel module or [[Software:Filesystem in Userspace|FUSE]] driver for earlier versions)
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}} (available as a [[Software:Filesystem in Userspace|FUSE]] driver)
| {{no}}
| {{no}}
| {{no}}
| {{yes}} (available as a [[Software:Filesystem in Userspace|FUSE]] driver)
| {{no}}
| {{yes|With kernel 5.10}}
|-
! [[FAT12]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{partial}} (via dosdir, dosread, doswrite)
| {{yes}}
| {{dunno}}
| {{yes}}
|-
! [[FAT16]]&nbsp;/ [[FAT16B]]&nbsp;/ [[FAT16X]]
| {{yes}} (FAT16 from DOS 3.0, FAT16B from DOS 3.31, FAT16X from DOS 7.0)
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{partial}} (via dosdir, dosread, doswrite, not FAT16X)
| {{yes}}
| {{dunno}}
| {{yes}}
|-
! [[FAT32]]&nbsp;/ [[FAT32X]]
| {{yes}} (from DOS 7.10)
| {{yes}}
| {{yes}}
| {{yes}} (from Windows 95 OSR2)
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{yes}}
|-
! GFS
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[High Performance File System|HPFS]]
| {{partial}} (with third-party drivers)
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}}
| {{yes}} (from OS/2 1.2)
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[NTFS]]
| {{partial}} (with third-party drivers)
| {{yes}} Native since Linux Kernel 5.15 NTFS3. Older kernels may use backported NTFS3 driver or ntfs-3g<ref name="NTFS3 Pull Request acceptance">{{cite web |title=NTFS3 Pull Request acceptance|url=https://lkml.iu.edu/hypermail/linux/kernel/2109.0/03731.html}}</ref>
| {{partial|Read only, write support needs Paragon NTFS or ntfs-3g}}
| {{needs}} 3rd-party drivers like Paragon NTFS for Win98, DiskInternals NTFS Reader
| {{yes}}
| {{no}}
| {{yes}} with ntfs-3g
| {{dunno}}
| {{yes}} with ntfs-3g
| {{no}}
| {{yes}} with ntfs-3g
| {{dunno}}
| {{needs|With third party tools}}
|-
! Apple [[Hierarchical File System (Apple)|HFS]]
| {{no}}
| {{yes}}
| {{no}} write support since Mac OS X 10.6 and no support at all since macOS 10.15
| {{no}}
| {{needs}} Paragon HFS+ <ref name="Paragon HFS">{{cite web |title=Paragon HFS+ for Windows 10 |url=http://www.paragon-software.com/home/hfs-windows/download.html}}</ref>
| {{yes}}
| {{no}}
| {{dunno}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
|-
! Apple [[HFS Plus]]
| {{no}}
| {{partial}} - writing support only to unjournalled FS
| {{yes}}
| {{no}}
| {{needs}} Paragon HFS+ <ref name="Paragon HFS"/>
| {{yes}} from Mac OS 8.1
| {{no}}
| {{dunno}}
| {{yes2|with addon}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
|-
! FFS
| {{no}}
| {{dunno}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! UFS1
| {{no}}
| {{partial}} - read only
| {{yes}}
| {{no}}
| {{partial}} (with ufs2tools, read only)
| {{dunno}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! UFS2
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{partial}} (with ufs2tools, read only)
| {{dunno}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Log-structured File System (BSD)|LFS]]
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Extended file system|ext]]
| {{no}}
| {{yes}} - until 2.1.20
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Xiafs]]
| {{no}}
| {{yes}} - until 2.1.20<br />
Experimental port available to 2.6.32 and later <ref name="Porting an Ancient Filesystem to Modern Linux">{{cite web |title=Porting an Ancient Filesystem to Modern Linux |website=Time To Pull The Plug |url=http://time.to.pullthepl.ug/blog/2013/6/24/porting-an-ancient-filesystem-to-modern-linux/ |access-date=2016-04-22 |archive-url=https://web.archive.org/web/20170621190933/http://time.to.pullthepl.ug/blog/2013/6/24/porting-an-ancient-filesystem-to-modern-linux/ |archive-date=2017-06-21 |url-status=dead }}</ref><ref name="Github modern-xiafs">{{cite web |title=A port of the xiafs filesystem to modern Linux kernels. |website=Github (cdtk) |url=https://github.com/ctdk/modern-xiafs|date=2019-06-28 }}</ref>
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Ext2|ext2]]
| {{no}}
| {{yes}}
| {{needs}} Paragon ExtFS <ref name="Paragon ExtFS for Mac">{{cite web |title=Paragon ExtFS for Mac |url=https://www.paragon-software.com/ufsdhome/extfs-mac}}</ref> or ext2fsx
| {{partial}} (read-only, with explore2fs)<ref name="explore2fs">{{cite web|url=http://www.chrysocome.net/explore2fs|title= Explore2fs|website=chrysocome.net}}</ref>
| {{needs}} Paragon ExtFS <ref name="Paragon ExtFS for Windows">{{cite web |title=Paragon ExtFS for Windows |url=https://www.paragon-software.com/home/extfs-windows}}</ref> or partial with Ext2 IFS<ref name="Ext2 IFS for Windows">{{cite web |title=FAQ |website=Ext2 Installable File System For Windows |url=http://www.fs-driver.org/faq.html}} (Provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.)</ref> or ext2fsd<ref name="Ext2fs Driver">{{cite web |last1=Branten |first1=Bo |url=http://www.ext2fsd.com/ |title=Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8) |access-date=2012-07-24 |archive-url=https://web.archive.org/web/20120723091043/http://www.ext2fsd.com/ |archive-date=2012-07-23 |url-status=dead }}</ref>
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Ext3|ext3]]
| {{no}}
| {{yes}}
| {{needs}} Paragon ExtFS <ref name="Paragon ExtFS for Mac"/> or partial with ext2fsx (journal not updated on writing)
| {{partial}} (read-only, with explore2fs)<ref name="explore2fs"/>
| {{needs}} Paragon ExtFS <ref name="Paragon ExtFS for Windows"/> or partial with Ext2 IFS<ref name="Ext2 IFS for Windows"/> or ext2fsd<ref name="Ext2fs Driver"/>
| {{yes}}<ref name="ext3">{{cite web |title=FreeBSD Handbook |url=https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-linux.html}}</ref>
| {{no}}
| {{yes2|with addon}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
|-
! [[Ext4|ext4]]
| {{no}}
| {{yes}}
| {{needs}} Paragon ExtFS <ref name="Paragon ExtFS for Mac"/>
| {{no}}
| {{yes}}, with the optional [[Software:Windows Subsystem for Linux#WSL 2|WSL2]]; physical and VHDX virtual disks.<ref>
      {{cite web |first=Scott |last=Hanselman |website=Newsletter of Wonderful Things
          |title=WSL2 can now mount Linux ext4 disks directly |date=2021-11-02 |access-date=2023-10-01
          |url=https://www.hanselman.com/blog/wsl2-can-now-mount-linux-ext4-disks-directly}}</ref><ref>
      {{cite web |author=Microsoft Corp. |website=Microsoft Learn |date=2023-07-17<!-- The latest ed., unversioned. -->
          |title=Windows technical documentation: Windows development environment: Windows Subsystem for Linux. 
          |url=https://learn.microsoft.com/windows/wsl/basic-commands#mount-a-disk-or-device |url-status=live
          |archive-url=https://web.archive.org/web/20211227193303/https://docs.microsoft.com/en-us/windows/wsl/wsl2-mount-disk <!-- The site was renamed docs. to learn. in 2022. -->
          |publication-date=2021-12-09 |archive-date=2021-12-27 |access-date=2023-10-01}}</ref>
| {{dunno}}
| {{yes}} since FreeBSD 12.0<ref name="ext3"/>
| {{no}}
| {{yes2|with addon}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{yes}}
|-
! [[Software:NOVA (filesystem)|NOVA]]
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:Lustre (file system)|Lustre]]
| {{no}}
| {{yes}}<ref name="lustre">{{cite web |title=Lustre Wiki |url=http://wiki.lustre.org/index.php?title=Main_Page}}</ref>
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[NILFS]]
| {{no}}
| {{yes}} as an external kernel module
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[F2FS]]
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! [[ReiserFS]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{partial}} - Read Only from 6.0 to 10.x<ref>{{Cite web |url=https://www.freebsd.org/cgi/man.cgi?query=reiserfs&apropos=0&sektion=0&manpath=FreeBSD+10.4-RELEASE&arch=default&format=html |title=FreeBSD 10.4 MAN page - reiserfs |website=www.freebsd.org |access-date=2019-08-05}}</ref> and dropped in 11.0<ref>{{Cite web |url=https://www.linuxquestions.org/questions/%2Absd-17/freebsd-11-and-reiserfs-4175595198/ |title=FreeBSD 11 and Reiserfs |date=2016-12-19 |website=www.linuxquestions.org |language=en |access-date=2019-08-05}}</ref><ref>{{Cite web |url=https://marc.info/?l=freebsd-commits-all&m=146349940607224&w=2 |title='svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC |website=marc.info |access-date=2019-08-05}}</ref>
| {{dunno}}
| {{yes2|with addon}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Reiser4]]
| {{no}}
| {{yes}} with a kernel patch
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! SpadFS
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! OCFS
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[OCFS2]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[XFS]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{partial}}
| {{dunno}}
| {{partial|with addon (read only)}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[JFS (file system)|JFS]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[QFS]]
| {{no}}
| {{partial}} - client only<ref>{{cite web |url=https://docs.oracle.com/cd/E22586_01/html/E22570/gledk.html |title=About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide |access-date=2016-03-14}}</ref>
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[Be File System]]
| {{no}}
| {{partial}} - read-only
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Novell Storage Services|NSS]]
| {{no}}
| {{yes}} via EVMS{{efn |name=EVMS |Supported using only EVMS; not currently supported using LVM}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[NetWare File System|NWFS]]
| {{partial}} (with Novell drivers)
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{yes}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! ODS-2
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! ODS-5
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Universal Disk Format|UDF]]
| {{no}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[Veritas File System|VxFS]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[Fossil (file system)|Fossil]]
| {{no}}
| {{yes}}{{efn |name=fossil-p9p |Provided in [[Software:Plan 9 from User Space|Plan 9 from User Space]]}}
| {{yes}}{{efn |name=fossil-p9p}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}{{efn |name=fossil-p9p}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}{{efn |name=fossil-p9p}}
| {{dunno}}
| {{no}}
|-
! [[ZFS]]
| {{no}}
| {{yes}} with [[Software:Filesystem in Userspace|FUSE]]<ref name="zfs on fuse">{{cite web |title=ZFS Filesystem for FUSE/Linux |website=Wizy Wiki |date=30 November 2009 |url=http://www.wizy.org/wiki/ZFS_on_FUSE |archive-url=https://web.archive.org/web/20130513101601/http://www.wizy.org/wiki/ZFS_on_FUSE |archive-date=13 May 2013}}</ref> or as an external kernel module<ref name="ZoL">{{cite web |title=ZFS on Linux |url=http://zfsonlinux.org/ |publisher=Lawrence Livermore National Laboratory}}</ref>
| {{yes}} with Read/Write Developer Preview<ref name="zfs on mac os x">{{cite web |last1=Kim |first1=Arnold |date=4 October 2007 |url=http://www.macrumors.com/2007/10/04/apple-seeds-zfs-read-write-developer-preview-1-1-for-leopard/ |title=Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard |website=Mac Rumors}}</ref>
| {{no}}
| {{yes}}<ref>{{cite web|title=OpenZFS on Windows|url=https://openzfsonwindows.org/}}</ref>
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! [[Btrfs]]
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{yes}} with WinBtrfs<ref name="Github btrfs">{{cite web |title=WinBtrfs |website=Github (maharmstone) |url=https://github.com/maharmstone/btrfs|date=2020-11-22 }}</ref>
| {{dunno}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[Bcachefs]]
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! VMFS2
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! VMFS3
| {{no}}
| {{dunno}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{no}}
| {{no}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! IBM HFS
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! IBM zFS
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! ReFS
| {{no}}
| {{needs}} Paragon ReFS for Linux
| {{dunno}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{no}}
|-
! [[ISO 9660]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
! [[Rock Ridge]]
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[Joliet (file system)|Joliet ("CDFS")]]
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{no}}
|-
! [[SquashFS]]
| {{no}}
| {{yes}}
| {{partial}} (There are ports of unsquashfs and mksquashfs.)
| {{no}}
| {{partial}} (There are ports of unsquashfs and mksquashfs.)
| {{no}}
| {{partial}} (There are ports of unsquashfs and mksquashfs and fusefs-port.<ref>{{cite web|url=http://www.freshports.org/sysutils/squashfs-tools/|title=squashfs-tools|website=Freshports}}</ref><ref>{{cite web|url=http://www.freshports.org/sysutils/fusefs-squashfuse/|title=fusefs-squashfuse|website=Freshports}}</ref>)
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! [[Software:Ceph|BlueStore/Cephfs]]
| {{no}}
| {{yes}}
| {{no}}{{efn|name=cephfs-fuse-driver|FUSE based driver available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.}}
| {{no}}
| {{no}}{{efn|name=cephfs-dokany-driver|Filesystem driver "Dokany" available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.}}
| {{no}}
| {{no}}{{efn|name=cephfs-fuse-driver}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|- class="sortbottom"
! File system
! [[Engineering:DOS|DOS]]
! [[Software:Linux|Linux]]
! [[Software:MacOS|macOS]]
! Windows&nbsp;9x (historic)
! [[Software:Microsoft Windows|Windows]] (current)
! [[Software:Classic Mac OS|Classic]]<br>[[Software:Classic Mac OS|Mac OS]]
! [[Software:FreeBSD|FreeBSD]]
! OS/2
! [[Software:BeOS|BeOS]]
! [[Software:Minix|Minix]]
! [[Software:Solaris (operating system)|Solaris]]
! z/OS
! [[Software:Android (operating system)|Android]]
|}
</div>

== Limits ==
<!-- NOTE: Keep alphabetical order of rows – don't just add them at random. (Per Wikipedia style guide.) -->

While storage devices usually have their size expressed in powers of 10 (for instance a 1&nbsp;[[Terabyte|TB]] Solid State Drive will contain at least 1,000,000,000,000 (10<sup>12</sup>, 1000<sup>4</sup>) bytes), filesystem limits are invariably powers of 2, so usually expressed with IEC prefixes. For instance, a 1&nbsp;[[Tebibyte|TiB]] limit means 2<sup>40</sup>, 1024<sup>4</sup> bytes. Approximations (rounding down) using power of 10 are also given below to clarify.

<div style="overflow-x:auto">
{| class="wikitable sortable" style="width: auto; text-align: center; table-layout: fixed;"
! File system
! Maximum [[Filename|filename]] length
! Allowable characters in directory entries{{efn |name=note-25 |These are the restrictions imposed by the on-disk directory entry structures themselves. Particular [[Installable File System]] drivers may place restrictions of their own on file and directory names; [[Operating system|operating system]]s may also place restrictions of their own, across all filesystems. [[Engineering:DOS|DOS]], [[Software:Microsoft Windows|Windows]], and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters <nowiki>! # $ % & ' ( ) - @ ^ _ ` { } ~</nowiki>, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters <nowiki>" * / : < > ? \ | + , . ; = [ ]</nowiki>, control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 [[Unicode]] except <nowiki>\ / : ? * " &gt; &lt; | and NUL</nowiki> are allowed in file and directory names across all filesystems. [[Unix-like]] systems disallow the characters <nowiki>/ and NUL</nowiki> in file and directory names across all filesystems.}}
! Maximum pathname length
! Maximum file size
! Maximum volume size{{efn |name=note-4 |For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128&nbsp;[[Kibibyte|KiB]] (131.0&nbsp;[[Kilobyte|KB]]) for FAT — which is the cluster size range allowed by the on-disk data structures, although some [[Installable File System]] drivers and [[Operating system|operating system]]s do not support cluster sizes larger than 32&nbsp;[[Kibibyte|KiB]] (32.76&nbsp;[[Kilobyte|KB]])).}}
! Max number of files
|-
| {{rh}} class="table-rh" |[[AdvFS]]
| 255 characters
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="17592186044416" | 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]])
| data-sort-type="number" data-sort-value="17592186044416" | 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | APFS
| 255 [[UTF-8]] characters
| Unicode 9.0 encoded in [[UTF-8]]<ref>{{Cite web |title=Frequently Asked Questions |url=https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html}}</ref>
| {{dunno}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="0" {{dunno}}
|2<sup>63</sup> <ref>{{Cite web |title=Volume Format Comparison |url=https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/VolumeFormatComparison/VolumeFormatComparison.html}}</ref>
|-
| {{rh}} class="table-rh" |[[Bcachefs]]
| 255 bytes
| Any byte except '/' and NUL
| No limit defined
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
|2<sup>64</sup>
|-
| {{rh}} class="table-rh" |[[Software:BeeGFS|BeeGFS]]
|255 bytes
|Any byte except NUL{{efn |name=note-26}}
|No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Be File System|BFS]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="279172874240" | 12,288 [[Byte|byte]]s to 260&nbsp;[[Gibibyte|GiB]] (279.1&nbsp;[[Gigabyte|GB]]){{efn |name=note-3 |Varies wildly according to block size and fragmentation of block allocation groups.}}
| data-sort-type="number" data-sort-value="2305843009213693952" | 256&nbsp;[[Pebibyte|PiB]] (288.2&nbsp;[[Petabyte|PB]]) to 2&nbsp;[[Exbibyte|EiB]] (2.305&nbsp;[[Exabyte|EB]])
| Unlimited
|-
| {{rh}} class="table-rh" |[[Software:Ceph|BlueStore/Cephfs]]
| 255 characters
| any byte, except null, "/"
| No limit defined
| Max. 2<sup>64</sup> bytes, 1&nbsp;TiB (1.099&nbsp;TB) by default <ref>{{cite web |title=CephFS Maximum File Sizes and Performance |url=https://docs.ceph.com/en/mimic/cephfs/administration/}}</ref>
| Not limited
| Not limited, default is 100,000 files per directory <ref>{{cite web |title=CephFS Directory Fragmentation |url=https://docs.ceph.com/en/latest/cephfs/dirfrags/}}</ref>
|-
| {{rh}} class="table-rh" |[[Btrfs]]
| 255 bytes
| Any byte except '/' and NUL
| No limit defined
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
|2<sup>64</sup>
|-
| {{rh}} class="table-rh" | CBM DOS
| 16 bytes
| Any byte except NUL
| 0 (no directory hierarchy)
| data-sort-type="number" data-sort-value="16777216" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]])
| data-sort-type="number" data-sort-value="16777216" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | CP/M file system
| 8.3
| [[ASCII]] except for <nowiki>&lt; &gt; . , ; : = ? * [ ]</nowiki>
| No directory hierarchy (but accessibility of files depends on user areas via USER command since CP/M 2.2)
| data-sort-type="number" data-sort-value="0" | 32&nbsp;[[Mebibyte|MiB]] (33.55&nbsp;[[Megabyte|MB]])
| data-sort-type="number" data-sort-value="0" | 512&nbsp;[[Mebibyte|MiB]] (536.8&nbsp;[[Megabyte|MB]])<!-- at least in CP/M 3 -->
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Engineering:DECtape|DECtape]]
| 6.3
| A–Z, 0–9
| DTxN:FILNAM.EXT = 15
| data-sort-type="number" data-sort-value="369280" | 369,280 [[Byte|byte]]s (577 * 640)
| data-sort-type="number" data-sort-value="369280" | 369,920 [[Byte|byte]]s (578 * 640)
| {{dunno}}
|-
| {{rh}} class="table-rh" | Disk Operating System (GEC DOS)
| {{dunno}}
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}} at least 131,072 [[Byte|byte]]s
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | Elektronika BK tape format
| 16 bytes
| {{dunno}}
| No directory hierarchy
| data-sort-type="number" data-sort-value="65536" | 64&nbsp;[[Kibibyte|KiB]] (65.53&nbsp;[[Kilobyte|KB]])
| data-sort-type="number" data-sort-value="800000" | Not limited. Approx. 800&nbsp;[[Kibibyte|KiB]] (819.2&nbsp;[[Kilobyte|KB]]) (one side) for 90 min cassette
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[ExFAT|exFAT]]
| 255 [[UTF-16]] characters
| [[Unicode]] except for control codes 0x0000 - 0x001F or <nowiki>" * / : < > ? \ |</nowiki> <ref>https://www.ntfs.com/exfat-filename-dentry.htm</ref>
| 32,760 characters with each path component no more than 255 characters<ref name="msdn-FS-functionality">{{cite web |date=2021-01-07 |title=File System Functionality Comparison |url=https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits |access-date=2022-08-14 |website=Microsoft Docs |publisher=Microsoft}}</ref>
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])<ref name="msdn-FS-functionality" />
| data-sort-type="number" data-sort-value="75557863725914323419136" | 64&nbsp;[[Zebibyte|ZiB]] (75.55&nbsp;[[Zettabyte|ZB]]) (2<sup>76</sup>&nbsp;[[Byte|byte]]s)
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Extended file system|ext]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Ext2|ext2]]
| 255 bytes
| Any byte except NUL, /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2199023255552" | 16&nbsp;[[Gibibyte|GiB]] (17.17&nbsp;[[Gigabyte|GB]]) to 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]){{efn |name=note-4}}
| data-sort-type="number" data-sort-value="35184372088832" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]) to 32&nbsp;[[Tebibyte|TiB]] (35.18&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Ext3|ext3]]
| 255 bytes
| Any byte except NUL, /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2199023255552" | 16&nbsp;[[Gibibyte|GiB]] (17.17&nbsp;[[Gigabyte|GB]]) to 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]){{efn |name=note-4}}
| data-sort-type="number" data-sort-value="35184372088832" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]) to 32&nbsp;[[Tebibyte|TiB]] (35.18&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Ext4|ext4]]
| 255 bytes<ref>{{cite web |author=Vimal A.R |date=16 July 2016 |title=Max file-name length in an EXT4 file system. |url=https://arvimal.blog/2016/07/21/max-file-name-length-in-an-ext4-file-system/ |archive-url=https://web.archive.org/web/20210228121426/https://arvimal.blog/2016/07/21/max-file-name-length-in-an-ext4-file-system/ |archive-date=28 February 2021 |website=arvimal.blog}}</ref>
| Any byte except NUL, /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="17592186044416" | 16&nbsp;[[Gibibyte|GiB]] (17.17&nbsp;[[Gigabyte|GB]]) to 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]]){{efn |name=note-4}}<ref name="ext4-features">{{cite web |date=9 June 2008 |title=Interviews/EricSandeen |url=http://fedoraproject.org/wiki/Interviews/EricSandeen |website=Fedora Project Wiki}}</ref>
| data-sort-type="number" data-sort-value="1152921504606846976" | 1&nbsp;[[Exbibyte|EiB]] (1.152&nbsp;[[Exabyte|EB]])
|2<sup>32</sup> (static [[Inode|inode]] limit specified at [[Disk formatting|creation]])
|-
| {{rh}} class="table-rh" | [[F2FS]]
| 255 bytes
| Any byte except NUL, /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="4329690886144" | 4,228,213,756 KiB (4.329 [[Terabyte|TB]])
| data-sort-type="number" data-sort-value="17592186044416" | 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | FAT (8-bit)
| 6.3 (binary files) / 9 characters (ASCII files)
| [[ASCII]] (0x00 and 0xFF not allowed in first character)
| No directory hierarchy
| data-sort-type="number" data-sort-value="0" {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[FAT12]]/[[FAT16]]
| [[8.3 filename|8.3]] (255 UCS-2<!-- UCS-2, not UTF-16! --> characters with LFN){{efn |name=note-24 |Depends on whether the [[FAT12]], [[FAT16]], and [[FAT32]] ''implementation'' has support for LFNs. Where it does not, as in OS/2, [[Engineering:DOS|DOS]], [[Software:Windows 95|Windows 95]], [[Software:Windows 98|Windows 98]] in DOS-only mode and the Linux "msdos" driver, file names are limited to [[8.3 filename|8.3 format]] of 8-bit OEM characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also must not contain lowercase letters. A few special device names (CON, NUL, AUX, PRN, LPT1, COM1, etc.) should be avoided, as some operating systems (notably DOS, OS/2 and Windows) reserve them.}}
| SFN: OEM A-Z, 0-9, <nowiki>! # $ % & ' ( ) - @ ^ _ ` { } ~</nowiki>, 0x80-0xFF, 0x20. LFN: [[Unicode]] except NUL, <nowiki>" * / : < > ? \ |</nowiki> {{efn |name=note-25}}{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="33554432" | 32&nbsp;[[Mebibyte|MiB]] (33.55&nbsp;[[Megabyte|MB]]) (4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]])){{efn |name="note-fsize"|On-disk structures would support up to 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]]), but practical file size is limited by volume size.}}
| data-sort-type="number" data-sort-value="33554432" | 1&nbsp;[[Mebibyte|MiB]] (1.048&nbsp;[[Megabyte|MB]]) to 32&nbsp;[[Mebibyte|MiB]] (33.55&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[FAT16B]]/[[FAT16X]]
| [[8.3 filename|8.3]] (255 UCS-2<!-- UCS-2, not UTF-16! --> characters with LFN){{efn |name=note-24}}
| SFN: OEM A-Z, 0-9, <nowiki>! # $ % & ' ( ) - @ ^ _ ` { } ~</nowiki>, 0x80-0xFF, 0x20. LFN: [[Unicode]] except NUL, <nowiki>" * / : < > ? \ |</nowiki> {{efn |name=note-25}}{{efn |name=note-24}}{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483648" | 2 (4) [[Gibibyte|GiB]]{{efn |name="note-fsize"}} (2.147&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="2147483648" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]]) to 2 (4) [[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[FAT32]]/[[FAT32X]]
| [[8.3 filename|8.3]] (255 UCS-2<!-- UCS-2, not UTF-16! --> characters with LFN){{efn |name=note-24}}
| SFN: OEM A-Z, 0-9, <nowiki>! # $ % & ' ( ) - @ ^ _ ` { } ~</nowiki>, 0x80-0xFF, 0x20. LFN: [[Unicode]] except NUL, <nowiki>" * / : < > ? \ |</nowiki> {{efn |name=note-25}}{{efn |name=note-24}}{{efn |name=note-26}}
| 32,760 characters with each path component no more than 255 characters<ref name="msdn-FS-functionality" />
| data-sort-type="number" data-sort-value="4294967295" | 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]])<ref name="msdn-FS-functionality" />
| data-sort-type="number" data-sort-value="17592186044415" | 512&nbsp;[[Mebibyte|MiB]] (536.8&nbsp;[[Megabyte|MB]]) to 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]]){{efn |While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32&nbsp;[[Gibibyte|GiB]] (34.35&nbsp;[[Gigabyte|GB]]). This includes, notoriously, the [[Software:Windows XP|Windows XP]] installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use [[Software:Fdisk|FDISK]] from a [[Software:Windows Me|Windows ME]] Emergency Boot Disk to avoid.<ref>{{cite web |title= Limitations of the FAT32 File System in Windows XP |publisher=Microsoft |url=http://support.microsoft.com/kb/314463 |archive-url=https://web.archive.org/web/20140330033436/http://support.microsoft.com/kb/314463 |archivedate=2014-03-30 |url-status=dead}}</ref>}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | FATX
| 42 bytes{{efn |name=note-24}}
| ASCII.
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="2147483648" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]]) to 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |FFS
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="4294967296" | 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="281474976710656" | 256&nbsp;[[Tebibyte|TiB]] (281.4&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Fossil (file system)|Fossil]]
| {{dunno}}
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | GEC DOS filing system extended
| 8 bytes
| A–Z, 0–9. Period was directory separator
| {{dunno}} No limit defined (workaround for OS limit)
| data-sort-type="number" data-sort-value="0" {{dunno}} at least 131,072 [[Byte|byte]]s
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Software:GEMDOS|GEMDOS]]
| 8.3
| A-Z, a-z, 0-9 <nowiki>! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > | [ ] ( ) _</nowiki><ref>{{cite web |title=GEMDOS Overview |url=http://cd.textfiles.com/ataricompendium/BOOK/HTML/CHAP2.HTM}}</ref>
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |GFS2
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 100&nbsp;[[Tebibyte|TiB]] (109.95&nbsp;[[Terabyte|TB]]) to 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-83 |Depends on CPU arch. For 32bit kernels the max is 16&nbsp;TiB (17.59&nbsp;TB). <ref>{{cite web|url=https://access.redhat.com/solutions/1532|title=What are the file and file system size limitations for Red Hat Enterprise Linux?|website=Red Hat|date=2023-03-21}}</ref>}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 100&nbsp;[[Tebibyte|TiB]] (109.95&nbsp;[[Terabyte|TB]]) to 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-84 |Depends on CPU arch. For 32bit kernels the max is 16&nbsp;TiB (17.59&nbsp;TB). <ref>{{cite web|url=https://access.redhat.com/solutions/1532|title=What are the file and file system size limitations for Red Hat Enterprise Linux?|website=Red Hat|date=2023-03-21}}</ref>}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |GFS
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]) to 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-63 |Depends on kernel version and arch. For 2.4 kernels the max is 2&nbsp;TiB (2.199&nbsp;TB). For 32-bit 2.6 kernels it is 16&nbsp;TiB (17.59&nbsp;TB). For 64-bit 2.6 kernels it is 8&nbsp;EiB (9.223&nbsp;EB).}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]) to 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-63}}
| {{dunno}}

|-
| {{rh}} class="table-rh" |GPFS
| 255 UTF-8 codepoints
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="0" | 9&nbsp;EiB (10.37&nbsp;EB)
| data-sort-type="number" data-sort-value="633825300114114700748351602688" | 524,288&nbsp;[[Yobibyte|YiB]] (2<sup>99</sup>&nbsp;[[Byte|byte]]s)
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[HAMMER (file system)|HAMMER]]
| 1023 bytes<ref>{{cite web |author=Matthew Dillon |title=HAMMER2 Design Document |url=http://apollo.backplane.com/DFlyMisc/hammer2.txt |quote=we can allow filenames up to 1023 bytes long}}</ref>
| Any byte except NUL{{efn |name=note-26}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| data-sort-type="number" data-sort-value="1152921504606846976" | 1&nbsp;[[Exbibyte|EiB]] (1.152&nbsp;[[Exabyte|EB]])<ref>{{cite web |author=Matthew Dillon |date=June 21, 2008 |title=The HAMMER Filesystem |url=http://www.dragonflybsd.org/hammer/hammer.pdf}}</ref>
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Hierarchical File System (Apple)|HFS]]
| 31 bytes
| Any byte except <code>:</code>
| Unlimited
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="2199023255552" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[HFS Plus]]
| 255 UTF-16 characters{{efn |name=note-1 |The "classic" Mac OS provides two sets of functions to retrieve file names from an HFS Plus volume, one of them returning the full Unicode names, the other shortened names fitting in the older 31 byte limit to accommodate older applications.}}
| Any valid [[Unicode]]{{efn |name=note-26}}{{efn |name=note-2 |HFS Plus mandates support for an escape sequence to allow arbitrary Unicode. Users of older software might see the escape sequences instead of the desired characters.}}
| Unlimited
| data-sort-type="number" data-sort-value="9223372036854775808" | slightly less than 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="9223372036854775808" | slightly less than 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])<ref>{{cite web |date=July 26, 2016 |title=Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits |url=https://support.apple.com/en-us/HT201711 |url-status=dead |archive-url=https://web.archive.org/web/20190408213105/https://support.apple.com/en-us/HT201711 |archive-date=2019-04-08 |website=support.apple.com}}</ref><ref>{{cite web |date=February 20, 2012 |title=Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits |url=https://support.apple.com/kb/TA21924 |website=support.apple.com}}</ref>
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[High Sierra Format]]
| {{dunno}}
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[High Performance File System|HPFS]]
| 255 bytes
| Any byte except NUL{{efn |name=note-27 |The "." and ".." directory entries in HPFS that are seen by applications programs are a partial fiction created by the [[Installable File System]] drivers. The on-disk data structure for a directory does not contain entries by those names, but instead contains a special "start" entry. Whilst on-disk directory entries by those names are not physically prohibited, they cannot be created in normal operation, and a directory containing such entries is corrupt.}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="2199023255552" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]){{efn |name=note-13 |This is the limit of the on-disk structures. The HPFS [[Installable File System]] driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64&nbsp;[[Gibibyte|GiB]] (68.71&nbsp;[[Gigabyte|GB]]).}}
| {{dunno}}
|-
| {{rh}} class="table-rh" | IBM SFS
| 8.8
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" | Non-hierarchical<ref>{{cite web |date=2015-06-03 |title=SFS file system |url=https://www.ibm.com/docs/en/cobol-aix/5.1?topic=systems-sfs-file-system |url-status=live |archive-url=https://web.archive.org/web/20220913063022/https://www.ibm.com/docs/en/cobol-aix/5.1?topic=systems-sfs-file-system |archive-date=2022-09-13 |access-date=2022-09-13 |website=www.ibm.com}}</ref>
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[ISO 9660:1988|1988]]
| Level&nbsp;1: 8.3,<br />Level&nbsp;2&nbsp;&amp;&nbsp;3: ~&nbsp;180
| Depends on Level{{efn |[[ISO 9660]]}}
| ~ 180 bytes?
| data-sort-type="number" data-sort-value="8796093022208" | 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]]) (Level 1 & 2) to 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]]) (Level 3){{efn |Through the use of multi-extents, a file can consist of multiple segments, each up to 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]]) in size. See [[ISO 9660]]}}
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]]){{efn |Assuming the typical 2048 Byte sector size. The volume size is specified as a 32 bit value identifying the number of sectors on the volume.}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[ISO 9660:1999|1999]]
| {{dunno}}
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |JFS
| 255 bytes
| Any [[Unicode]] except NUL
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="4503599627370496" | 4&nbsp;[[Pebibyte|PiB]] (4.503&nbsp;[[Petabyte|PB]])
| data-sort-type="number" data-sort-value="36028797018963968" | 32&nbsp;[[Pebibyte|PiB]] (36.02&nbsp;[[Petabyte|PB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |JFS1
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="4503599627370496" | 512&nbsp;[[Tebibyte|TiB]] (562.9&nbsp;[[Terabyte|TB]]) to 4&nbsp;[[Pebibyte|PiB]] (4.503&nbsp;[[Petabyte|PB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Joliet (file system)|Joliet ("CDFS")]]
| 64 characters
| All UCS-2 code except *, /, \, :, ;, and ?<ref>{{cite web |date=22 May 1995 |title=Joliet Specification |url=http://bmrc.berkeley.edu/people/chaffee/jolspec.html |archive-url=https://web.archive.org/web/20090414104421/http://bmrc.berkeley.edu/people/chaffee/jolspec.html |archive-date=14 April 2009}}</ref>
| {{dunno}}
| data-sort-type="number" data-sort-value="8796093022208" | same as [[ISO 9660:1988|1988]]
| data-sort-type="number" data-sort-value="8796093022208" | same as [[ISO 9660:1988|1988]]
| {{dunno}}
|-
| {{rh}} class="table-rh" | Level-D
| 6.3
| A–Z, 0–9
| DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67
| data-sort-type="number" data-sort-value="206158430208" | 34,359,738,368 words (2<sup>35</sup>); 206,158,430,208 SIXBIT bytes
| data-sort-type="number" data-sort-value="11392000000" | Approx 12&nbsp;[[Gibibyte|GiB]] (12.88&nbsp;[[Gigabyte|GB]]) (64 * 178&nbsp;[[Mebibyte|MiB]] (186.6&nbsp;[[Megabyte|MB]]))
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Software:Lustre (file system)|Lustre]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]]) on [[ZFS]]
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Macintosh File System|MFS]]
| 255 bytes
| Any byte except <code>:</code>
| No path (flat filesystem)
| data-sort-type="number" data-sort-value="268435456" | 256&nbsp;[[Mebibyte|MiB]] (268.4&nbsp;[[Megabyte|MB]])
| data-sort-type="number" data-sort-value="268435456" | 256&nbsp;[[Mebibyte|MiB]] (268.4&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | MicroDOS file system
| 14 bytes
| {{dunno}}
| {{dunno}}
| data-sort-type="number" data-sort-value="16777216" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]])
| data-sort-type="number" data-sort-value="33554432" | 32&nbsp;[[Mebibyte|MiB]] (33.55&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |Minix V1 FS
| 14 or 30 bytes, set at filesystem creation time
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="268966912" | 256.5 [[Mebibyte|MiB]] (268.9 [[Megabyte|MB]]) {{efn |name=note-file-size-vs-filesystem-size |Sparse files can be larger than the file system size, even though they can't contain more data.}}
| data-sort-type="number" data-sort-value="67108864" | 64&nbsp;[[Mebibyte|MiB]] (67.10&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |Minix V2 FS
| 14 or 30 bytes, set at filesystem creation time
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483647" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]]) {{efn |name=note-file-size-vs-filesystem-size}}
| data-sort-type="number" data-sort-value="1073741824" | 1&nbsp;[[Gibibyte|GiB]] (1.073&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |Minix V3 FS
| 60 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="2147483647" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])<!-- max file size is a signed 32-bit int -->
| data-sort-type="number" data-sort-value="4294967296" | 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[NILFS]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Software:NOVA (filesystem)|NOVA]]
| 255 bytes
| Any byte except NUL, /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Novell Storage Services|NSS]]
| 256 characters
| Depends on namespace used{{efn |name=note-28 |NSS allows files to have multiple names, in separate namespaces.}}
| Only limited by client
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]])
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[NTFS]]
| 255 characters<!--See MSKB http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfiles/html/msdn_longfile.asp-->
| In Win32 namespace: any [[UTF-16]] code unit (case-insensitive) except <code>/\:*"?&lt;&gt;&#124;</code> as well as [[Null character|NUL]]
In [[POSIX]] namespace: any [[UTF-16]] code unit (case-sensitive) except <code>/</code> as well as [[Null character|NUL]]<ref>{{cite web |last1=Russon |first1=Richard |last2=Fledel |first2=Yuval |title=NTFS Documentation |url=http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf}}</ref>
| 32,767 characters with each path component (directory or filename) up to 255 characters long{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;TiB (17.59&nbsp;TB) to 8&nbsp;PiB (9.007&nbsp;PB){{efn |name=note-55 |This is the limit of the on-disk structures. The NTFS driver for [[Software:Windows NT|Windows NT]] limits the volume size that it can handle to 256&nbsp;[[Tebibyte|TiB]] (281.4&nbsp;[[Terabyte|TB]]) and the file size to 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]]) respectively; in Windows 10 version 1709, the limit is 8&nbsp;PiB (9.007&nbsp;PB) when using 2&nbsp;MiB (2.097&nbsp;MB) cluster size.}}<ref name=":0">{{Cite web |date=2022-05-26 |title=NTFS overview |url=https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview |url-status=live |archive-url=https://web.archive.org/web/20220526213037/https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview |archive-date=2022-05-26 |access-date=2022-06-05 |website=Microsoft Docs}}</ref>
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;TiB (17.59&nbsp;TB) to 8&nbsp;PiB (9.007&nbsp;PB){{efn |name=note-55}}<ref name=":0" />
| 2<sup>32</sup>
|-
| {{rh}} class="table-rh" |[[NetWare File System|NWFS]]
| 80 bytes{{efn |name=note-52 |Some namespaces had lower name length limits. "LONG" had an 80-byte limit, "NWFS" 80 bytes, "NFS" 40 bytes and "DOS" imposed [[8.3 filename|8.3 filename]].}}
| Depends on namespace used{{efn |name=note-28}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="4294967296" | 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]])
| data-sort-type="number" data-sort-value="1099511627776" | 1&nbsp;[[Tebibyte|TiB]] (1.099&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |OCFS
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]])
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[OCFS2]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="4503599627370496" | 4&nbsp;[[Pebibyte|PiB]] (4.503&nbsp;[[Petabyte|PB]])
| data-sort-type="number" data-sort-value="4503599627370496" | 4&nbsp;[[Pebibyte|PiB]] (4.503&nbsp;[[Petabyte|PB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |ODS-5
| 236 bytes{{efn |name=note-15 |Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.}}
| {{dunno}}
| 4,096 bytes{{efn |name=note-16 |Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.}}
| data-sort-type="number" data-sort-value="1099511627776" | 1&nbsp;[[Tebibyte|TiB]] (1.099&nbsp;[[Terabyte|TB]])
| data-sort-type="number" data-sort-value="1099511627776" | 1&nbsp;[[Tebibyte|TiB]] (1.099&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[QFS]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]]){{efn |name=note-72 |QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.}}
| data-sort-type="number" data-sort-value="4503599627370496" | 4&nbsp;[[Pebibyte|PiB]] (4.503&nbsp;[[Petabyte|PB]]){{efn |name=note-72}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |ReFS
| In Win32 namespace: any [[UTF-16]] code unit (case-insensitive) except <code>/\:*"?&lt;&gt;&#124;</code> as well as [[Null character|NUL]]
In [[POSIX]] namespace: any [[UTF-16]] code unit (case-sensitive) except <code>/</code> as well as [[Null character|NUL]]<ref name="blogs.msdn.microsoft.com" /><ref>{{Cite web |last=Amigo |date=2015-04-02 |title=Invalid Characters in File Names |url=https://amigotechnotes.wordpress.com/2015/04/02/invalid-characters-in-file-names/ |access-date=2020-10-20 |website=Amigo's Technical Notes |language=en}}</ref>
| 32,767 characters with each path component (directory or filename) up to 255 characters long<ref name="blogs.msdn.microsoft.com" />
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])<ref name="blogs.msdn.microsoft.com" /><ref>{{Cite web |title=Resilient File System (ReFS) overview |url=https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview |access-date=2017-11-07 |website=Microsoft Docs |language=en-us}}</ref>
| data-sort-type="number" data-sort-value="1208925819614629174706176" | 1&nbsp;[[Yobibyte|YiB]] (1.208&nbsp;[[Yottabyte|YB]])<ref name="blogs.msdn.microsoft.com" />
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[ReiserFS]]
| 4,032 bytes/255 characters
| Any byte except NUL or <code>'/'</code>{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]]){{efn |ReiserFS has a theoretical maximum file size of 1&nbsp;[[Exbibyte|EiB]] (1.152&nbsp;[[Exabyte|EB]]), but "page cache limits this to 8 Ti on architectures with 32 bit int"<ref>{{cite web |title=FAQ |date=15 October 2003 |website=namesys |url=http://www.namesys.com/faq.html#reiserfsspecs |archive-url=https://web.archive.org/web/20060719110322/http://www.namesys.com/faq.html#reiserfsspecs |archive-date=19 July 2006}}</ref>}} (v3.6), 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]]) (v3.5)
| data-sort-type="number" data-sort-value="17592186044416" | 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Reiser4]]
| 3,976 bytes
| Any byte except <code>/</code> and NUL
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="8796093022208" | 8&nbsp;[[Tebibyte|TiB]] (8.796&nbsp;[[Terabyte|TB]]) on x86
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Rock Ridge]]
| 255 bytes
| Any byte except NUL or /{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="8796093022208" | same as [[ISO 9660:1988|1988]]
| data-sort-type="number" data-sort-value="8796093022208" | same as [[ISO 9660:1988|1988]]
| {{dunno}}
|-
| {{rh}} class="table-rh" | [[Software:RT-11|RT-11]]
| 6.3
| A–Z, 0–9, $
| 0 (no directory hierarchy)
| data-sort-type="number" data-sort-value="33554432" | 33,554,432 [[Byte|byte]]s (65536 * 512)
| data-sort-type="number" data-sort-value="33554432" | 33,554,432 [[Byte|byte]]s
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[SquashFS]]
| 256 bytes
| {{dunno}}
| No limit defined
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Universal Disk Format|UDF]]
| 255 bytes
| Any [[Unicode]] except NUL
| 1,023 bytes{{efn |name=note-43 |This restriction might be lifted in newer versions.}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="17592186044415" | 512&nbsp;[[Mebibyte|MiB]] (536.8&nbsp;[[Megabyte|MB]]) to 16&nbsp;[[Tebibyte|TiB]] (17.59&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |UFS1
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="281474976710656" | 16&nbsp;[[Gibibyte|GiB]] (17.17&nbsp;[[Gigabyte|GB]]) to 256&nbsp;[[Tebibyte|TiB]] (281.4&nbsp;[[Terabyte|TB]])
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| Subdirectory per directory is 32,767<ref name="ufs-limit">{{cite web |title=Maximum Number of UFS Subdirectories |url=https://docs.oracle.com/cd/E19120-01/open.solaris/819-2723/fsfilesysappx-5/index.html |access-date=2019-02-12 |publisher=[[Company:Oracle Corporation|Oracle]]}}</ref>
|-
| {{rh}} class="table-rh" |UFS2
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="36028797018963968" | 512&nbsp;[[Gibibyte|GiB]] (549.7&nbsp;[[Gigabyte|GB]]) to 32&nbsp;[[Pebibyte|PiB]] (36.02&nbsp;[[Petabyte|PB]])
| data-sort-type="number" data-sort-value="649037107316853896642560" | 512&nbsp;[[Zebibyte|ZiB]] (604.4&nbsp;[[Zettabyte|ZB]])<ref>{{cite web |title=Frequently Asked Questions for FreeBSD 9.X and 10.X |url=https://www.freebsd.org/doc/faq/book.html |access-date=2016-03-20 |publisher=[[Software:FreeBSD|FreeBSD]] Documentation Project |quote=If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32&nbsp;KiB (32.76&nbsp;KB) => 16 Exa * 32&nbsp;KiB (32.76&nbsp;KB) => 512 ZettaBytes.}}</ref> (2<sup>79</sup> [[Byte|byte]]s)
| Subdirectory per directory is 32,767<ref name="ufs-limit" />
|-
| {{rh}} class="table-rh" |UniFS
| No limit defined (depends on client)
| {{dunno}}
| No limit defined (depends on client)
| Available cache space at time of write (depends on platform)
| No limit defined
| No limit defined
|-
| {{rh}} class="table-rh" | Version 6 Unix file system (V6FS)
| 14 bytes
| Any byte except [[Null character|NUL]] and <code>/</code>{{efn |name=note-26 |In these filesystems the directory entries named "." and ".." have special status. Directory entries with these names are not prohibited, and indeed exist as normal directory entries in the on-disk data structures. However, they are mandatory directory entries, with mandatory values, that are automatically created in each directory when it is created; and directories without them are considered corrupt.}}
| No limit defined{{efn |name=note-12 |The on-disk structures have no inherent limit. Particular [[Installable File System]] drivers and [[Operating system|operating system]]s may impose limits of their own, however. Limited by its Current Directory Structure (CDS), [[Engineering:DOS|DOS]] does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 bytes<!-- without the pending NUL character --> for FAT, or 255 characters for LFNs. Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Older POSIX APIs which rely on the <code>PATH_MAX</code> constant have a limit of 4,096 bytes on Linux but this can be worked around. Linux itself has no hard path length limits.<ref>{{cite web|url=https://eklitzke.org/path-max-is-tricky|title=PATH_MAX Is Tricky|website=Evan Klitzke’s web log}}</ref><ref>{{cite web|url=https://insanecoding.blogspot.com/2007/11/pathmax-simply-isnt.html|title=PATH_MAX simply isn't|website=Insane Coding|date=2007-11-03}}</ref>}}
| data-sort-type="number" data-sort-value="16777216" | 16&nbsp;[[Mebibyte|MiB]] (16.77&nbsp;[[Megabyte|MB]]){{efn |name=note-57 |The file size in the inode is 1 8-bit byte followed by 1 16-bit word, for 24 bits. The actual maximum was 8,847,360 bytes, with 7 singly-indirect blocks and 1 doubly-indirect block; PWB/UNIX 1.0's variant had 8 singly-indirect blocks, making the maximum 524,288 bytes or half a [[Megabyte|MB]].}}
| data-sort-type="number" data-sort-value="33554432" | 32&nbsp;[[Mebibyte|MiB]] (33.55&nbsp;[[Megabyte|MB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" | Version 7 Unix file system (V7FS)
| 14 bytes
| Any byte except NUL or <code>/</code>{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="1073741824" | 1&nbsp;[[Gibibyte|GiB]] (1.073&nbsp;[[Gigabyte|GB]]){{efn |name=note-58 |The actual maximum was 1,082,201,088 bytes, with 10 direct blocks, 1 singly-indirect block, 1 doubly-indirect block, and 1 triply-indirect block. The 4.0BSD and 4.1BSD versions, and the [[Software:UNIX System V|System V]] version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4&nbsp;[[Gibibyte|GiB]] (4.294&nbsp;[[Gigabyte|GB]]).}}
| data-sort-type="number" data-sort-value="2199023255552" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |VMFS2
| 128
| Any byte except NUL or <code>/</code>{{efn |name=note-26}}
| 2,048
| data-sort-type="number" data-sort-value="4398046511104" | 4&nbsp;[[Tebibyte|TiB]] (4.398&nbsp;[[Terabyte|TB]]){{efn |name=note-74 |Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.}}
| data-sort-type="number" data-sort-value="70368744177664" | 64&nbsp;[[Tebibyte|TiB]] (70.36&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |VMFS3
| 128
| Any byte except NUL or <code>/</code>{{efn |name=note-26}}
| 2,048
| data-sort-type="number" data-sort-value="2199023255552" | 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]){{efn |name=note-74}}
| data-sort-type="number" data-sort-value="70368744177664" | 64&nbsp;[[Tebibyte|TiB]] (70.36&nbsp;[[Terabyte|TB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Veritas File System|VxFS]]
| 255 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="0" {{dunno}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[XFS]]
| 255 bytes{{efn |Note that the filename can be much longer [[XFS]]}}
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-9 |XFS has a limitation under Linux 2.4 of 64&nbsp;[[Tebibyte|TiB]] (70.36&nbsp;[[Terabyte|TB]]) file size, but Linux 2.4 only supports a maximum block size of 2&nbsp;[[Tebibyte|TiB]] (2.199&nbsp;[[Terabyte|TB]]). This limitation is not present under [[Software:IRIX|IRIX]].}}
| data-sort-type="number" data-sort-value="9223372036854775808" | 8&nbsp;[[Exbibyte|EiB]] (9.223&nbsp;[[Exabyte|EB]]){{efn |name=note-9}}
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[Xiafs]]
| 248 bytes
| Any byte except NUL{{efn |name=note-26}}
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="67108864" | 64&nbsp;[[Mebibyte|MiB]] (67.10&nbsp;[[Megabyte|MB]])
| data-sort-type="number" data-sort-value="2147483648" | 2&nbsp;[[Gibibyte|GiB]] (2.147&nbsp;[[Gigabyte|GB]])
| {{dunno}}
|-
| {{rh}} class="table-rh" |[[ZFS]]
| 255 bytes
| Any [[Unicode]] except NUL
| No limit defined{{efn |name=note-12}}
| data-sort-type="number" data-sort-value="18446744073709551616" | 16&nbsp;[[Exbibyte|EiB]] (18.44&nbsp;[[Exabyte|EB]])
| data-sort-type="number" data-sort-value="340282366920938463463374607431768211456" | 281,474,976,710,656&nbsp;[[Yobibyte|YiB]] (2<sup>128</sup>&nbsp;[[Byte|byte]]s)
|2<sup>128</sup>
|- class="sortbottom"
! File system
! Maximum filename length
! Allowable characters in directory entries{{efn |name=note-25}}
! Maximum pathname length
! Maximum file size
! Maximum volume size{{efn |name=note-4}}
! Max number of files
|}
</div>

== See also ==
* [[List of file systems]]
* [[Software:Comparison of file archivers|Comparison of file archivers]]
* [[List of archive formats]]
* [[Software:Comparison of archive formats|Comparison of archive formats]]

== Notes ==
{{notelist|30em}}

== References ==
{{reflist|30em}}

== External links ==
* [https://web.archive.org/web/20040407211142/http://aurora.zemris.fer.hr/filesystems/ A speed comparison of filesystems on Linux 2.4.5] (archived)
* [https://www.debian-administration.org/article/388/Filesystems_ext3_reiser_xfs_jfs_comparison_on_Debian_Etch Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch] {{Webarchive|url=https://web.archive.org/web/20180304191727/https://debian-administration.org/article/388/Filesystems_ext3_reiser_xfs_jfs_comparison_on_Debian_Etch |date=2018-03-04 }} (April 23, 2006)
* [https://www.ogris.de/blkalloc/ Block allocation strategies of various filesystems]
* [https://unix.stackexchange.com/questions/165/what-are-the-disadvantages-of-ext4-reiserfs-jfs-and-xfs What are the (dis)advantages of ext4, ReiserFS, JFS, and XFS? - Unix & Linux Stack Exchange]

[[Category:Computer file systems| ]]
[[Category:Software comparisons|File systems]]

{{Sourceattribution|Comparison of file systems}}