Comparison of file systems

百度毫不动摇坚持和完善党的领导，毫不动摇把党建设得更加坚强有力，就能让亿万人民精诚团结、众志成城，在新时代的浩荡东风里，推动承载着中国人民伟大梦想的航船破浪前进，胜利驶向光辉的彼岸。

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

General information

File system	Creator	Year of introduction	Original operating system
DECtape	DEC	1964	PDP-6 Monitor
OS/3x0 FS	IBM	1964	OS/360
Level-D	DEC	1968	TOPS-10
George 3	ICT (later ICL)	1968	George 3
Version 6 Unix file system (V6FS)	Bell Labs	1972	Version 6 Unix
RT-11 file system	DEC	1973	RT-11
Disk Operating System (GEC DOS)	GEC	1973	Core Operating System
CP/M file system	Digital Research (Gary Kildall)	1974	CP/M^[1]^[2]
ODS-1	DEC	1975	RSX-11
GEC DOS filing system extended	GEC	1977	OS4000
FAT (8-bit)	Microsoft (Marc McDonald) for NCR	1977	Microsoft Standalone Disk BASIC-80 (later Microsoft Standalone Disk BASIC-86)
DOS 3.x	Apple	1978	Apple DOS
UCSD p-System	UCSD	1978	UCSD p-System
CBM DOS	Commodore	1978	Commodore BASIC
Atari DOS	Atari	1979	Atari 8-bit
Version 7 Unix file system (V7FS)	Bell Labs	1979	Version 7 Unix
ODS-2	DEC	1979	OpenVMS
FAT12	Seattle Computer Products (Tim Paterson)	1980	QDOS/86-DOS (later IBM PC DOS 1.0)
ProDOS	Apple	1980	Apple SOS (later ProDOS 8)
DFS	Acorn Computers Ltd	1982	Acorn BBC Micro MOS
ADFS	Acorn Computers Ltd	1983	Acorn Electron (later Arthur/RISC OS)
FFS	Kirk McKusick	1983	4.2BSD
FAT16	IBM, Microsoft	1984	PC DOS 3.0, MS-DOS 3.0
MFS	Apple	1984	System 1
Elektronika BK tape format	NPO "Scientific centre" (now Sitronics)	1985	Vilnius Basic, BK monitor program
HFS	Apple	1985	System 2.1
Amiga OFS^[1]	Metacomco for Commodore	1985	Amiga OS
GEMDOS	Digital Research	1985	Atari TOS
NWFS	Novell	1985	NetWare 286
High Sierra	Ecma International	1986	MSCDEX for MS-DOS 3.1/3.2^[3]
FAT16B	Compaq	1987	Compaq MS-DOS 3.31
Minix V1 FS	Andrew S. Tanenbaum	1987	MINIX 1.0
Amiga FFS	Commodore	1988	Amiga OS 1.3
ISO 9660:1988	Ecma International, ISO	1988	MS-DOS, "classic" Mac OS, and AmigaOS
HPFS	IBM & Microsoft	1989	OS/2 1.2
Rock Ridge	IEEE	1990 c. 1990	Unix
JFS1	IBM	1990	AIX^[a]
VxFS	VERITAS	1991	SVR4.0
ext	Rémy Card	1992	Linux
AdvFS	DEC	1993^[4]	Digital Unix
NTFS	Microsoft (Gary Kimura, Tom Miller)	1993	Windows NT 3.1
LFS	Margo Seltzer	1993	Berkeley Sprite
ext2	Rémy Card	1993	Linux, Hurd
Xiafs	Q. Frank Xia	1993	Linux
UFS1	Kirk McKusick	1994	4.4BSD
XFS	SGI	1994	IRIX
HFS	IBM	1994	MVS/ESA (now z/OS)
FAT16X	Microsoft	1995	MS-DOS 7.0 / Windows 95
Joliet ("CDFS") (extension to ISO 9660)	Microsoft	1995	Microsoft Windows, Linux, "classic" Mac OS, and FreeBSD
UDF	ISO/ECMA/OSTA	1995	—
FAT32, FAT32X	Microsoft	1996	MS-DOS 7.10 / Windows 95 OSR2^[b]
QFS	Sun Microsystems	1996	Solaris
GPFS	IBM	1996	AIX, Linux
Be File System	Be Inc. (D. Giampaolo, Cyril Meurillon)	1996	BeOS
Minix V2 FS	Andrew S. Tanenbaum	1997	MINIX 2.0
HFS Plus	Apple	1998	Mac OS 8.1
NSS	Novell	1998	NetWare 5
PolyServe File System (PSFS)	PolyServe	1998	Windows, Linux
ODS-5	DEC	1998	OpenVMS V7.2
WAFL	NetApp	1998	Data ONTAP
ext3	Stephen Tweedie	1999	Linux
ISO 9660:1999	Ecma International, ISO	1999	Microsoft Windows, Linux, "classic" Mac OS, FreeBSD, and AmigaOS
JFS	IBM	1999	OS/2 Warp Server for e-business
GFS	Sistina (Red Hat)	2000	Linux
ReiserFS	Namesys	2001	Linux
zFS	IBM	2001	z/OS (backported to OS/390)
FATX	Microsoft	2002	Xbox
UFS2	Kirk McKusick	2002	FreeBSD 5.0
OCFS	Oracle Corporation	2002	Linux
SquashFS	Phillip Lougher, Robert Lougher	2002	Linux
VMFS2	VMware	2002	VMware ESX Server 2.0
Lustre	Cluster File Systems^[5]	2002	Linux
Fossil	Bell Labs	2003	Plan 9 version 4
Google File System	Google	2003	Linux
ZFS	Sun Microsystems	2004	Solaris
Reiser4	Namesys	2004	Linux
Non-Volatile File System	Palm, Inc.	2004	Palm OS Garnet
BeeGFS	Fraunhofer/ ThinkParQ	2005	Linux
GlusterFS	Gluster Inc.	2005	Linux
Minix V3 FS	Andrew S. Tanenbaum	2005	MINIX 3
OCFS2	Oracle Corporation	2005	Linux
NILFS	NTT	2005	Linux
VMFS3	VMware	2005	VMware ESX Server 3.0
GFS2	Red Hat	2006	Linux
ext4	various	2006	Linux
exFAT	Microsoft	2006	Windows CE 6.0
Btrfs	Chris Mason	2007	Linux
JXFS	Hyperion Entertainment	2008	AmigaOS 4.1
HAMMER	Matthew Dillon	2008	DragonFly BSD 2.0
LSFS	StarWind Software	2009	Linux, FreeBSD, Windows
UniFS	Nasuni	2009	Cloud
CASL	Nimble Storage	2010	Linux
OrangeFS	Omnibond and others	2011	Linux
VMFS5	VMware	2011	vSphere 5.0+
CHFS	University of Szeged	2011	NetBSD 6.0+
ReFS	Microsoft	2012	Windows Server 2012
F2FS	Samsung Electronics	2012	Linux
bcachefs	Kent Overstreet	2015	Linux
APFS	Apple	2016	macOS High Sierra, iOS 10.3
NOVA	UC, San Diego	2017	Linux
BlueStore/Cephfs	Red Hat, University of California, Santa Cruz	2017	Linux
HAMMER2	Matthew Dillon^[6]	2017	DragonFly BSD 5.0
EROFS	Huawei^[7]	2018	Linux, Android
VaultFS	Swiss Vault	2022	Linux / Unix

Metadata

File system	Stores file owner	POSIX file permissions	Creation timestamps	Last access/ read timestamps	Last metadata change timestamps	Last archive timestamps	Access control lists	Security/ MAC labels	Extended attributes/ Alternate data streams/ forks	Metadata checksum/ ECC
Bcachefs	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes
BeeGFS	Yes	Yes	No	Yes	Yes	No	Yes	?	Yes	Yes
CP/M file system	No	No	Yes^[c]	No	No	No	No	No	No	No
DECtape^[8]	No	No	Yes	No	No	No	No	No	No	No
Elektronika BK tape format	No	No	No	No	No	No	No	No	No	Yes
Level-D	Yes	Yes	Yes	Yes (date only)	Yes	Yes	Yes (FILDAE)	No	No	No
RT-11^[9]	No	No	Yes (date only)	No	No	No	No	No	No	Yes
Version 6 Unix file system (V6FS)^[10]	Yes	Yes	No	Yes	No	No	No	No	No	No
Version 7 Unix file system (V7FS)^[11]	Yes	Yes	No	Yes	No	No	No	No	No	No
exFAT	No	No	Yes	Yes	No	No	No	No	No	No
FAT12/FAT16/FAT32	No	No	Yes	Yes	No^[d]	No	No	No	No^[e]	No
HPFS	Yes^[f]	No	Yes	Yes	No	No	No	?	Yes	No
NTFS	Yes	Yes^[g]	Yes	Yes	Yes	No	Yes	Yes^[h]	Yes	No
ReFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes^[i]	Yes
HFS	No	No	Yes	No	No	Yes	No	No	Yes	No
HFS Plus	Yes	Yes	Yes	Yes	Yes	Yes	Yes	?	Yes	No
FFS	Yes	Yes	No	Yes	Yes	No	No	No	No	No
UFS1	Yes	Yes	No	Yes	Yes	No	Yes^[j]	Yes^[j]	No^[k]	No
UFS2	Yes	Yes	Yes	Yes	Yes	No	Yes^[j]	Yes^[j]	Yes	Partial
HAMMER	Yes	Yes	Yes	Yes	Yes	?	Yes	Yes	No	Yes
LFS	Yes	Yes	No	Yes	Yes	No	No	No	No	No
EROFS	Yes	Yes	No	No	Yes	No	Yes	Yes	Yes	No
ext	Yes	Yes	No	No	No	No	No	No	No	No
Xiafs	Yes	Yes	No	Yes	Yes	No	No	No	No	No
ext2	Yes	Yes	No	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	No
ext3	Yes	Yes	No	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	No
ext4	Yes	Yes	Yes	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	Partial^[m]
NOVA	Yes	Yes	Yes	Yes	Yes	No	No	No	No	Yes
Lustre	Yes	Yes	No	Yes	Yes	No	Yes	Yes	Yes	No
F2FS	Yes	Yes	Yes	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	No
GPFS	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes
GFS	Yes	Yes	No	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	No
NILFS	Yes	Yes	Yes	No	Yes	No	No	No	No	Yes
ReiserFS	Yes	Yes	No	Yes	Yes	No	Yes^[l]	Yes^[l]	Yes	No
Reiser4	Yes	Yes	No	Yes	Yes	No	No	No	No	No
OCFS	No	Yes	No	No	Yes	Yes	No	No	No	No
OCFS2	Yes	Yes	No	Yes	Yes	No	No	No	No	No
XFS	Yes	Yes	Yes^[n]	Yes	Yes	No	Yes	Yes^[l]	Yes	Yes
JFS	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
QFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	No
BFS	Yes	Yes	Yes	No	No	No	No	No	Yes	No
AdvFS	Yes	Yes	No	Yes	Yes	No	Yes	No	Yes	No
NSS	Yes	Yes	Yes^[o]	Yes^[o]	Yes	Yes^[o]	Yes	?	Yes^[p]^[q]	No
NWFS	Yes	?	Yes^[o]	Yes^[o]	Yes	Yes^[o]	Yes	?	Yes^[p]^[q]	No
ODS-5	Yes	Yes	Yes	?	?	Yes	Yes	?	Yes^[r]	No
APFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VxFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes^[l]	No
UDF	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes
Fossil	Yes	Yes^[s]	No	Yes	Yes	No	No	No	No	No
ZFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes^[t]	Yes^[u]	Yes
Btrfs	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes
Minix V1	Yes	Yes	No	No	No	No	No	No	No	No
Minix V2	Yes	Yes	No	Yes	Yes	No	No	No	No	No
Minix V3	Yes	Yes	No	Yes	Yes	No	No	No	No	No
VMFS2	Yes	Yes	No	Yes	Yes	No	No	No	No	No
VMFS3	Yes	Yes	No	Yes	Yes	No	No	No	No	No
ISO 9660:1988	No	No	Yes	No	No	No	No	No	No	No
Rock Ridge	Yes	Yes	No	Yes^[v]	Yes	No	No^[w]	No^[x]	No^[x]	No
Joliet ("CDFS") (extension to ISO 9660)	No	No	Yes	No	No	No	No	No	No	No
ISO 9660:1999	No	No	Yes	No	No	No	No	No	No	No
High Sierra	No	No	Yes	No	No	No	No	No	No	No
SquashFS	Yes	Yes	No	No	Yes	No	No	Yes	Yes	No
BlueStore/Cephfs	Yes	Yes	Yes	Yes	?	No	Yes	Yes	Yes	Yes
File system	Stores file owner	POSIX file permissions	Creation timestamps	Last access/ read timestamps	Last metadata change timestamps	Last archive timestamps	Access control lists	Security/ MAC labels	Extended attributes/ Alternate data streams/ forks	Metadata checksum/ ECC

All widely used file systems record a last modified time stamp (also known as "mtime"). It is not included in the table.

Individual file systems may record additional special types of date and time stamps. For example, the specification of ISO 9660 includes a "File Expiration Date and Time" and a "File Effective Date and Time".^[15]

Features

File capabilities

File system	Hard links	Symbolic links	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	XIP	Resident files (inline data)
DECtape	No	No	No	No	No	No	No	No	?
BeeGFS	No	Yes	Yes	Yes	Yes	Yes	No	No	?
Level-D	No	No	No	No	No	No	No	No	?
RT-11	No	No	No	No	No	No	No	No	?
APFS	Yes	Yes	?	?	Optional	Yes	?	?	?
Version 6 Unix file system (V6FS)	Yes	No	No	No	Yes	Yes	No	No	No
Version 7 Unix file system (V7FS)	Yes	No^[y]	No	No	Yes	Yes	No	No	No
exFAT	No	No	No	Partial (with 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 / FAT16B / FAT16X	No	No	No	Partial (with TFAT16 only)	No	Partial (with VFAT LFNs only)	No	No	No
FAT32 / FAT32X	No	No	No?	Partial (with TFAT32 only)	No	Partial (with VFAT LFNs only)	No	No	No
GFS	Yes	Yes^[z]	Yes	Yes^[aa]	Yes	Yes	No	No	?
HPFS	No	No	No	No	No	Yes	No	No	?
NTFS	Yes	Yes^[ab]	No^[ac]	Yes^[ac] (2000)	Yes^[ad]	Yes	Yes	?	Yes (approximately 700 bytes)
HFS Plus	Yes^[17]	Yes	No	Yes^[ae]	Optional^[af]	Yes	Yes^[ag]	No	?
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^[ah] ^[22] ^[ai]	Yes	Yes	No	?	No
HAMMER	Yes	Yes	Yes	Yes	Yes	Yes	?	No	?
LFS	Yes	Yes	Yes^[aj]	No	Yes	Yes	No	No	?
EROFS	Yes	Yes	No	No	Yes	Yes	No	No	Yes
ext	Yes	Yes	No	No	Yes	Yes	No	No	?
Xiafs	Yes	Yes	No	No	Yes	Yes	No	No	?
ext2	Yes	Yes	No	No	Yes	Yes	No	Yes^[ak]	?
ext3	Yes	Yes	Yes (2001) ^[al]	Yes (2001)	Yes	Yes	No	Yes	?
ext4	Yes	Yes	Yes^[al]	Yes	Yes, optional ^[25]	Yes	No	Yes	Yes (approximately 160 bytes)^[26]
NOVA	Yes	Yes	No	Yes	Yes	Yes	No	Yes	?
F2FS	Yes	Yes	Yes^[aj]	No	Yes	Yes	No	No	?
Lustre	Yes	Yes	Yes^[al]	Yes	Yes	Yes	Yes	No	?
NILFS	Yes	Yes	Yes^[aj]	No	Yes	Yes	No	No	?
ReiserFS	Yes	Yes	Yes^[am]	Yes	Yes	Yes	No	?	?
Reiser4	Yes	Yes	Yes	No	Yes	Yes	No	?	?
OCFS	No	Yes	No	No	Yes	Yes	No	No	?
OCFS2	Yes	Yes	Yes	Yes	Yes	Yes	No	No	?
XFS	Yes	Yes	Yes^[al]	Yes	Yes^[an]	Yes	Yes	?	?
JFS	Yes	Yes	Yes	Yes (1990)	Yes^[ao]	Yes	No	?	?
QFS	Yes	Yes	No	Yes	Yes	Yes	No	No	?
BFS	Yes	Yes	No	Yes	Yes	Yes	?	No	?
NSS	Yes	Yes	?	Yes	Yes^[ap]	Yes^[ap]	Yes^[aq]	No	?
NWFS	Yes^[ar]	Yes^[ar]	No	No	Yes^[ap]	Yes^[ap]	Yes^[aq]	No	?
ODS-2	Yes	Yes^[as]	No	Yes	No	No	Yes	No	?
ODS-5	Yes	Yes^[as]	No	Yes	No	Yes	Yes	?	?
UDF	Yes	Yes	Yes^[aj]	Yes^[aj]	Yes	Yes	No	Yes	Yes^[28]
VxFS	Yes	Yes	Yes	No	Yes	Yes	Yes	?	?
Fossil	No	No	No	No	Yes	Yes	Yes	No	?
ZFS	Yes	Yes	Yes^[at]	No^[at]	Yes	Yes	No	No	Yes (112 bytes)^[29]
Btrfs	Yes	Yes	Yes^[au]	No	Yes	Yes	?	?	Yes (2 KiB)^[30]
Bcachefs	Yes	Yes	Yes^[av]	No	Yes	Yes	?	?	?
Minix V1	Yes	Yes	No	No	Yes	Yes	No	No	?
Minix V2	Yes	Yes	No	No	Yes	Yes	No	No	?
Minix V3	Yes	Yes	No	No	Yes	Yes	No	No	?
VMFS2	Yes	Yes	No	Yes	Yes	Yes	No	No	?
VMFS3	Yes	Yes	No	Yes	Yes	Yes	No	No	?
ReFS	Yes^[aw]	Yes	?	?	Yes^[ad]	Yes	?	?	?
ISO 9660	No	No	No	No	No	No	No	No	?
Rock Ridge	Yes	Yes	No	No	Yes	Yes	No	No	?
Joliet ("CDFS") (extension to ISO 9660)	No	No	No	No	No	Yes	No	No	?
SquashFS	Yes	Yes	No	No	Yes	Yes	No	No	?
BlueStore/Cephfs	Yes	Yes	Yes	Yes	Yes	Yes	No	No	?
File system	Hard links	Symbolic links	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	XIP	Resident files

Block capabilities

Note that in addition to the below table, block capabilities can be implemented below the file system layer in Linux (LVM, integritysetup, cryptsetup) or Windows (Volume Shadow Copy Service, SECURITY), etc.

File system	Internal snapshotting / branching	Encryption	Deduplication	Data checksum/ ECC	Persistent Cache	Multiple Devices	Compression	Self-healing^[ax]
DECtape	No	No	No	No	No	No	No	No
BeeGFS	No	No	Yes	No	No	No	Yes	No
Level-D	No	No	No	No	No	No	No	No
RT-11	No	No	No	No	No	No	No	No
APFS	Yes	Yes	Yes ^[31]	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	No	No	No	No	No	No	No	No
FAT12	No	No	No	No	No	No	Partial^[ay]	No
FAT16 / FAT16B / FAT16X	No	No	No	No	No	No	Partial^[ay]	No
FAT32 / FAT32X	No	No	No	No	No	No	No	No
GFS	No	No	?	No	No	No	No	No
HPFS	?	No	?	No	No	No	No	No
NTFS	No	Yes	Yes^[az]^[33]	No	No	No	Yes	No
HFS Plus	No	No^[ba]	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	Yes	No	Yes	Yes	No	No	No	No
LFS	Yes	No	No	No	No	No	No	No
EROFS	No	No	Yes	No	No	Yes	Yes	No
ext	No	No	No	No	No	No	No	No
Xiafs	No	No	No	No	No	No	No	No
ext2	No	No	No	No	No	No	No	No
ext3	No	No	No	No	No	No	No	No
ext4	No	Yes, experimental ^[34]	No	No^[35]	No	No	No	No
NOVA	Yes	No	No	Yes	No	No	No	?
F2FS	No	Yes, experimental ^[36]	No	No	No	No	Yes	No
Lustre	No	No	No	No	Yes	Yes	No	No
NILFS	Yes, continuous^[aj]	No	No	Yes	No	No	No	No
ReiserFS	No	No	No	No	No	No	No	No
Reiser4	?	Yes^[bb]	?	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^[37]	No^[35]	No	No	No	No
JFS	?	No	?	No	No	No	only in JFS1 on AIX^[38]	No
QFS	No	No	No	No	No	No	No	No
BFS	No	No	No	No	No	No	No	No
NSS	Yes	Yes	?	No	No	No	Yes	No
NWFS	?	No	?	No	No	No	Yes	No
ODS-2	Yes	No	No	No	No	No	No	No
ODS-5	Yes	No	No	No	No	No	No
UDF	No	No	No	No	No	No	No	No
VxFS	Yes^[bc]	No	Yes	No	No	No	No	No
Fossil	Yes	No	Yes	No	No	No	Yes	No
ZFS	Yes	Yes^[bd]	Yes	Yes	Yes	Yes	Yes^[be]	Yes
Btrfs	Yes	No	Yes	Yes^[bf]	No	Yes	Yes^[bg]	Yes
Bcachefs	Yes	Yes	No	Yes^[bh]	No	Yes	Yes^[bi]	No
Minix V1	No	No	No	No	No	No	No	No
Minix V2	No	No	No	No	No	No	No	No
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	No^[bj]	No	Yes	No^[bk]	No	No	No^[bl]	No^[bk]
ISO 9660	No	No	No^[bm]	No	No	No	No	No
Rock Ridge	No	No	No^[bm]	No	No	No	No	No
Joliet ("CDFS") (extension to ISO 9660)	No	No	No^[bm]	No	No	No	No	No
SquashFS	No	No	Yes	Yes	No	No	Yes	No
BlueStore/Cephfs	Yes	No	No	Yes	Yes	Yes	Yes	Yes
File system	Internal snapshotting / branching	Encryption	Deduplication	Data checksum/ ECC	Persistent Cache	Multiple Devices	Compression	Self-healing^[ax]

Resize capabilities

"Online" and "offline" are synonymous with "mounted" and "not mounted".

File system	Host OS	Offline grow	Online grow	Offline shrink	Online shrink	Add and remove physical volumes
FAT16 / FAT16B / FAT16X	misc.	Yes^[bn]	No	Yes^[bn]	No	No
FAT32 / FAT32X	misc.	Yes^[bn]	No	Yes^[bn]	No	No
exFAT	misc.	No	No	No	No	No
NTFS	Windows	Yes	Yes	Yes	Yes	No
ReFS	Windows	?	Yes	?	No	No
HFS	macOS	No	No	No	No	No
HFS+	macOS	No	Yes	No	Yes	No
APFS	macOS	?	Yes	?	Yes	?
EROFS	Linux	Yes	No	No	No	Yes
SquashFS	Linux	No	No	No	No	No
NOVA	Linux	No	No	No	No	No
JFS^[48]	Linux	Yes	No	No	No	No
XFS^[49]	Linux	No	Yes	No^[50]	No^[50]	No
Lustre^[51]	Linux	?	Yes	No	No	Yes
F2FS^[52]	Linux	Yes	No	No	No	No
NTFS^[53]	Linux	Yes	No	Yes	No	No
ext2^[54]	Linux	Yes	No	Yes	No	No
ext3^[54]	Linux	Yes	Yes	Yes	No	No
ReiserFS^[55]	Linux	Yes	Yes	Yes	No	No
Reiser4^[56]	Linux	Yes	Yes	Yes	No	No
ext4^[54]	Linux	Yes	Yes	Yes	No	No
Btrfs^[57]	Linux	Yes	Yes	Yes	Yes	Yes
Bcachefs^[44]	Linux	Yes	Yes	No	No	Yes
NILFS^[58]	Linux	No	Yes	No	Yes	No
ZFS	misc.	No	Yes	No	Yes	Partial^[59]
JFS2	AIX	Yes	Yes	Yes	Yes	No
UFS2^[60]	FreeBSD	Yes	Yes (FreeBSD 10.0-RELEASE or later)	No	No	No
HAMMER	DragonflyBSD	?	?	?	?	?
BlueStore/Cephfs	Linux	No	Yes	No	Yes	Yes

Allocation and layout policies

File system	Sparse files	Block suballocation	Tail packing	Extents	Variable file block size^[bo]	Allocate-on-flush	Copy on write	Trim support
DECtape	No	No	No	No	No	No	No	No
BeeGFS	Yes	No	No	Yes	Yes	Yes	Yes	?
Level-D	No	No	No	Yes	No	No	No	?
APFS	Yes	?	?	Yes	?	Yes	Yes	Yes^[61]^[62]
Version 6 Unix file system (V6FS)	Yes	No	No	No	No	No	?	No
Version 7 Unix file system (V7FS)	Yes	No	No	No	No	No	?	No
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)^[63]	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes^[32])	No	Partial (only inside of compressed volumes)^[64]	No	No	No	Yes (Linux)
FAT16 / FAT16B / FAT16X	Partial (only inside of compressed volumes)^[63]	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes^[32])	No	Partial (only inside of compressed volumes)^[64]	No	No	No	Yes (Linux)
FAT32 / FAT32X	No	No	No	No	No	No	No	Yes (Linux)
GFS	Yes	No	Partial^[bp]	No	No	No	?	Yes
HPFS	No	No	No	Yes	No	No	?	Yes (Linux)
NTFS	Yes	Partial	No	Yes	No	No	?	Yes (NT 6.1+; Linux)
HFS Plus	No	No	No	Yes	No	No	?	Yes (macOS)
FFS	Yes	8:1^[bq]	No	No	No	No	?	No
UFS1	Yes	8:1^[bq]	No	No	No	No	?	No
UFS2	Yes	8:1^[bq]	No	No	Read-only so far	No	?	Yes^[65]^[66]
LFS	Yes	8:1^[bq]	No	No	No	No	Yes	?
EROFS	Yes	Yes	Yes	Yes	No	No	No	No
ext	Yes	No	No	No	No	No	No	No
Xiafs	Yes	No	No	No	No	No	?	?
ext2	Yes	No^[br]	No	No	No	No	No	Yes
ext3	Yes	No^[br]	No	No	No	No	No	Yes
ext4	Yes	No^[br]	No	Yes	No	Yes	No	Yes
NOVA	Yes	No	No	Yes	No	No	Yes	?
F2FS	Yes	No	No	Partial^[bs]	No	Yes	Yes	Yes^[67]
Lustre	Yes	No	No	Yes	No	Yes	?	?
NILFS	Yes	No	No	No	No	Yes	Yes	Yes (Linux NILFS2)
ReiserFS	Yes	Yes^[bt]	Yes	No	No	No	?	?
Reiser4	Yes	Yes^[bt]	Yes	Yes^[bu]	No	Yes	?	Testing^[68]
OCFS	?	No	No	Yes	No	No	?	?
OCFS2	Yes	No	No	Yes	No	No	?	Yes (Linux)
XFS	Yes	No	No	Yes	No	Yes	Yes, on request^[69]	Yes (Linux)
JFS	Yes	Yes	No	Yes	No	No	?	Yes (Linux)
QFS	?	Yes	No	No	No	No	?	?
BFS	?	No	No	Yes	No	No	?	Yes (Haiku)
NSS	?	No	No	Yes	No	Yes	?	?
NWFS	?	Yes^[bv]	No	No	No	No	?	?
ODS-5	?	No	No	Yes	No	No	?	?
VxFS	Yes	?	No	Yes	No	No	?	?
UDF	Yes	No	No	Yes	No	Depends on implementation.	Yes, for write once read many media	No
Fossil	?	No	No	No	No	No	?	?
ZFS	Yes	Yes	No	No	Yes	Yes	Yes	Yes
Btrfs	Yes	Yes	No^[30]	Yes	Yes	Yes	Yes	Yes
Bcachefs	?	?	?	Yes	?	Yes	Yes	?
VMFS2	Yes	Yes	No	No	No	No	?	?
VMFS3	Yes	Yes	No	No	No	No	?	?
ReFS	Yes	?	?	?	No	?	Yes	Yes (NT 6.1+)
ISO 9660	No	No	No	ISO 9660 Level 3 only	No	No	No	No
Rock Ridge (extension to ISO 9660)	No	No	No	extended from ISO 9660	No	No	No	No
Joliet ("CDFS") (extension to ISO 9660)	No	No	No	extended from ISO 9660	No	No	No	No
SquashFS	Yes	No	Yes	No	No	No	No	No
BlueStore/Cephfs	Yes	?	?	?	?	No	Yes	Yes
File system	Sparse files	Block suballocation	Tail packing	Extents	Variable file block size^[bo]	Allocate-on-flush	Copy on write	Trim support

OS support

File system	DOS	Linux	macOS	Windows 9x (historic)	Windows (current)	Classic Mac OS	FreeBSD	OS/2	BeOS	Minix	Solaris	z/OS	Android^[70]
APFS	No	Partial (read-only with apfs-fuse^[71] or linux-apfs^[72])	Yes (Since macOS Sierra)	No	No	No	No	No	No	No	No	No	No
BeeGFS	No	Yes	?	No	No	No	No	No	?	?	?	No	No
DECtape	No	No	No	No	No	No	No	No	No	No	No	No	No
Level-D	No	?	?	No	No	No	No	No	No	No	?	?	No
RT-11	No	No	No	No	No	No	No	No	No	No	No	No	No
Version 6 Unix file system (V6FS)	No	?	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	?	?	?	No	No
exFAT	No	Yes (since 5.4,^[73] available as a kernel module or FUSE driver for earlier versions)	Yes	No	Yes	No	Yes (available as a FUSE driver)	No	No	No	Yes (available as a FUSE driver)	No	With kernel 5.10
FAT12	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Partial (via dosdir, dosread, doswrite)	Yes	?	Yes
FAT16 / FAT16B / 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	?	Yes
FAT32 / FAT32X	Yes (from DOS 7.10)	Yes	Yes	Yes (from Windows 95 OSR2)	Yes	?	Yes	Yes	Yes	No	Yes	?	Yes
GFS	No	Yes	?	No	No	No	No	?	?	?	?	?	No
HPFS	Partial (with third-party drivers)	Yes	?	No	No	?	Yes	Yes (from OS/2 1.2)	?	No	?	?	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^[74]	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	?	Yes with ntfs-3g	No	Yes with ntfs-3g	?	With third party tools
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+ ^[75]	Yes	No	?	Yes	No	?	No	No
Apple HFS Plus	No	Partial - writing support only to unjournalled FS	Yes	No	Needs Paragon HFS+ ^[75]	Yes from Mac OS 8.1	No	?	with addon	No	?	No	No
FFS	No	?	Yes	No	?	?	Yes	?	?	?	?	?	No
UFS1	No	Partial - read only	Yes	No	Partial (with ufs2tools, read only)	?	Yes	No	?	?	Yes	?	No
UFS2	No	Yes	Yes	No	Partial (with ufs2tools, read only)	?	Yes	No	?	?	?	?	No
LFS	No	?	?	No	No	?	No	No	?	?	?	?	No
EROFS	No	Yes	Needs - since erofs-utils 1.4	No	No	No	No	No	No	No	No	No	Yes
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 Experimental port available to 2.6.32 and later ^[76]^[77]	No	No	No	No	No	No	No	No	No	No	No
ext2	No	Yes	Needs Paragon ExtFS ^[78] or ext2fsx	Partial (read-only, with explore2fs)^[79]	Needs Paragon ExtFS ^[80] or partial with Ext2 IFS^[81] or ext2fsd^[82]	No	Yes	No	Yes	?	?	?	No
ext3	No	Yes	Needs Paragon ExtFS ^[78] or partial with ext2fsx (journal not updated on writing)	Partial (read-only, with explore2fs)^[79]	Needs Paragon ExtFS ^[80] or partial with Ext2 IFS^[81] or ext2fsd^[82]	Partial (read only)^{[citation needed]}	Yes^[83]	No	with addon	?	Yes	?	Yes
ext4	No	Yes	Needs Paragon ExtFS ^[78]	No	Yes, with the optional WSL2; physical and VHDX virtual disks.^[84]^[85]	?	Yes since FreeBSD 12.0^[83]	No	with addon	?	?	?	Yes
NOVA	No	Yes	No	No	No	No	No	No	No	No	No	No	No
Lustre	No	Yes^[86]	?	No	No	?	No	?	?	?	Yes	?	No
NILFS	No	Yes as an external kernel module	?	No	?	?	No	?	?	?	?	?	No
F2FS	No	Yes	No	No	No	No	No	No	No	No	No	No	Yes
ReiserFS	No	Yes	?	No	No	?	Partial - Read Only from 6.0 to 10.x^[87] and dropped in 11.0^[88]^[89]	?	with addon	?	?	?	No
Reiser4	No	Yes with a kernel patch	?	No	No	?	No	?	?	?	?	?	No
SpadFS	No	Yes	No	No	No	No	?	No	No	No	No	No	No
OCFS	No	Yes	?	No	No	?	No	No	?	?	?	?	No
OCFS2	No	Yes	?	No	No	?	No	No	?	?	?	?	No
XFS	No	Yes	?	No	No	?	Partial	?	with addon (read only)	?	?	?	No
JFS	No	Yes	?	No	No	?	No	Yes	?	?	?	?	No
QFS	No	Partial - client only^[90]	?	No	No	?	No	No	?	?	Yes	?	No
Be File System	No	Partial - read-only	?	No	No	?	No	No	Yes	?	?	?	No
NSS	No	Yes via EVMS^[bw]	?	No	No	?	No	No	?	?	?	?	No
NWFS	Partial (with Novell drivers)	?	?	No	No	?	Yes	No	?	?	?	?	No
ODS-2	No	?	?	No	No	?	No	No	?	?	?	?	No
ODS-5	No	?	?	No	No	?	No	No	?	?	?	?	No
UDF	No	Yes	Yes	?	Yes	?	Yes	?	?	?	Yes	?	No
VxFS	No	Yes	?	No	No	?	No	No	?	?	Yes	?	No
Fossil	No	Yes^[bx]	Yes^[bx]	No	No	No	Yes^[bx]	No	No	No	Yes^[bx]	?	No
ZFS	No	Yes with FUSE^[91] or as an external kernel module^[92]	Yes with Read/Write Developer Preview^[93]	No	With third-party software (OpenZFS).^[94]	No	Yes	No	No	No	Yes	No	No
Btrfs	No	Yes	?	No	Yes with WinBtrfs^[95]	?	No	?	?	?	?	?	No
Bcachefs	No	Yes	No	No	No	No	No	No	No	No	No	No	No
VMFS2	No	?	?	No	No	?	No	No	?	?	?	?	No
VMFS3	No	?	?	No	No	?	No	No	?	?	?	?	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	?	No	Yes	?	?	?	?	?	?	?	No
ISO 9660	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No
Rock Ridge (extension to ISO 9660)	No	Yes	Yes	No	No	No	Yes	No	No	Yes	Yes	?	No
Joliet ("CDFS") (extension to ISO 9660)	No	Yes	Yes	Yes	Yes	?	Yes	Yes	Yes	?	Yes	?	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.^[96]^[97])	No	No	No	No	No	No
BlueStore/Cephfs	No	Yes	No^[by]	No	No^[bz]	No	No^[by]	No	No	No	No	No	No
File system	DOS	Linux	macOS	Windows 9x (historic)	Windows (current)	Classic Mac OS	FreeBSD	OS/2	BeOS	Minix	Solaris	z/OS	Android

Limits

While storage devices usually have their size expressed in powers of 10 (for instance a 1 TB Solid State Drive will contain at least 1,000,000,000,000 (10¹², 1000⁴) bytes), filesystem limits are invariably powers of 2, so usually expressed with IEC prefixes. For instance, a 1 TiB limit means 2⁴⁰, 1024⁴ bytes. Approximations (rounding down) using power of 10 are also given below to clarify.

File system	Maximum filename length	Allowable characters in directory entries^[ca]	Maximum pathname length	Maximum file size	Maximum volume size^[cb]	Max number of files
AdvFS	255 characters	Any byte except NUL^[cc]	No limit defined^[cd]	16 TiB (17.59 TB)	16 TiB (17.59 TB)	?
APFS	255 UTF-8 characters	Unicode 9.0 encoded in UTF-8^[98]	?	8 EiB (9.223 EB)	?	2⁶³ ^[99]
Bcachefs	255 bytes	Any byte except '/' and NUL	No limit defined	16 EiB (18.44 EB)	16 EiB (18.44 EB)	2⁶⁴
BeeGFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	16 EiB (18.44 EB)	16 EiB (18.44 EB)	?
BFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	12,288 bytes to 260 GiB (279.1 GB)^[ce]	256 PiB (288.2 PB) to 2 EiB (2.305 EB)	Unlimited
BlueStore/Cephfs	255 characters	any byte, except null, "/"	No limit defined	Max. 2⁶⁴ bytes, 1 TiB (1.099 TB) by default ^[100]	Not limited	Not limited, default is 100,000 files per directory ^[101]
Btrfs	255 bytes	Any byte except '/' and NUL	No limit defined	16 EiB (18.44 EB)	16 EiB (18.44 EB)	2⁶⁴
CBM DOS	16 bytes	Any byte except NUL	0 (no directory hierarchy)	16 MiB (16.77 MB)	16 MiB (16.77 MB)	?
CP/M file system	8.3	ASCII except for < > . , ; : = ? * [ ]	No directory hierarchy (but accessibility of files depends on user areas via USER command since CP/M 2.2)	32 MiB (33.55 MB)	512 MiB (536.8 MB)	?
DECtape	6.3	A–Z, 0–9	DTxN:FILNAM.EXT = 15	369,280 bytes (577?×?640)	369,920 bytes (578?×?640)	?
Disk Operating System (GEC DOS)	?	?	?	? at least 131,072 bytes	?	?
Elektronika BK tape format	16 bytes	?	No directory hierarchy	64 KiB (65.53 KB)	Not limited. Approx. 800 KiB (819.2 KB) (one side) for 90 min cassette	?
EROFS	255 bytes	Any byte except NUL, /^[cc]	No limit defined^[cd]	16 EiB (18.44 EB)	1 EiB (1.152 EB)	2⁶⁴
exFAT	255 UTF-16 characters	Unicode except for control codes 0x0000 - 0x001F or " * / : < > ? \ \| ^[102]	32,760 characters with each path component no more than 255 characters^[103]	16 EiB (18.44 EB)^[103]	64 ZiB (75.55 ZB) (2⁷⁶ bytes)	?
ext	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	2 GiB (2.147 GB)	2 GiB (2.147 GB)	?
ext2	255 bytes	Any byte except NUL, /^[cc]	No limit defined^[cd]	16 GiB (17.17 GB) to 2 TiB (2.199 TB)^[cb]	2 TiB (2.199 TB) to 32 TiB (35.18 TB)	?
ext3	255 bytes	Any byte except NUL, /^[cc]	No limit defined^[cd]	16 GiB (17.17 GB) to 2 TiB (2.199 TB)^[cb]	2 TiB (2.199 TB) to 32 TiB (35.18 TB)	?
ext4	255 bytes^[104]	Any byte except NUL, /^[cc]	No limit defined^[cd]	16 GiB (17.17 GB) to 16 TiB (17.59 TB)^[cb]^[105]	1 EiB (1.152 EB)	2³² (static inode limit specified at creation)
F2FS	255 bytes	Any byte except NUL, /^[cc]	No limit defined^[cd]	4,228,213,756 KiB (4.329 TB)	16 TiB (17.59 TB)	?
FAT (8-bit)	6.3 (binary files) / 9 characters (ASCII files)	ASCII (0x00 and 0xFF not allowed in first character)	No directory hierarchy	?	?	?
FAT12/FAT16	8.3 (255 UCS-2 characters with LFN)^[cf]	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ^[ca]^[cc]	No limit defined^[cd]	32 MiB (33.55 MB) (4 GiB (4.294 GB))^[cg]	1 MiB (1.048 MB) to 32 MiB (33.55 MB)	?
FAT16B/FAT16X	8.3 (255 UCS-2 characters with LFN)^[cf]	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ^[ca]^[cf]^[cc]	No limit defined^[cd]	2 (4) GiB^[cg] (2.147 GB)	16 MiB (16.77 MB) to 2 (4) GiB (2.147 GB)	?
FAT32/FAT32X	8.3 (255 UCS-2 characters with LFN)^[cf]	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ^[ca]^[cf]^[cc]	32,760 characters with each path component no more than 255 characters^[103]	4 GiB (4.294 GB)^[103]	512 MiB (536.8 MB) to 16 TiB (17.59 TB)^[ch]	?
FATX	42 bytes^[cf]	ASCII.	No limit defined^[cd]	2 GiB (2.147 GB)	16 MiB (16.77 MB) to 2 GiB (2.147 GB)	?
FFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	4 GiB (4.294 GB)	256 TiB (281.4 TB)	?
Fossil	?	?	?	?	?	?
GEC DOS filing system extended	8 bytes	A–Z, 0–9. Period was directory separator	? No limit defined (workaround for OS limit)	? at least 131,072 bytes	?	?
GEMDOS	8.3	A-Z, a-z, 0-9 ! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > \| [ ] ( ) _^[107]	?	?	?	?
GFS2	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	100 TiB (109.95 TB) to 8 EiB (9.223 EB)^[ci]	100 TiB (109.95 TB) to 8 EiB (9.223 EB)^[cj]	?
GFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	2 TiB (2.199 TB) to 8 EiB (9.223 EB)^[ck]	2 TiB (2.199 TB) to 8 EiB (9.223 EB)^[ck]	?
GPFS	255 UTF-8 codepoints	Any byte except NUL^[cc]	No limit defined^[cd]	9 EiB (10.37 EB)	524,288 YiB (2⁹⁹ bytes)	?
HAMMER	1023 bytes^[110]	Any byte except NUL^[cc]	?	?	1 EiB (1.152 EB)^[111]	?
HFS	31 bytes	Any byte except `:`	Unlimited	2 GiB (2.147 GB)	2 TiB (2.199 TB)	?
HFS Plus	255 UTF-16 characters^[cl]	Any valid Unicode^[cc]^[cm]	Unlimited	slightly less than 8 EiB (9.223 EB)	slightly less than 8 EiB (9.223 EB)^[112]^[113]	?
High Sierra Format	?	?	?	?	?	?
HPFS	255 bytes	Any byte except NUL^[cn]	No limit defined^[cd]	2 GiB (2.147 GB)	2 TiB (2.199 TB)^[co]	?
IBM SFS	8.8	?	?	Non-hierarchical^[114]	?	?
ISO 9660:1988	Level 1: 8.3, Level 2 & 3: ~ 180	Depends on Level^[cp]	~ 180 bytes?	4 GiB (4.294 GB) (Level 1 & 2) to 8 TiB (8.796 TB) (Level 3)^[cq]	8 TiB (8.796 TB)^[cr]	?
ISO 9660:1999	?	?	?	?	?	?
JFS	255 bytes	Any Unicode except NUL	No limit defined^[cd]	4 PiB (4.503 PB)	32 PiB (36.02 PB)	?
JFS1	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	8 EiB (9.223 EB)	512 TiB (562.9 TB) to 4 PiB (4.503 PB)	?
Joliet ("CDFS") (extension to ISO 9660)	64 characters	All UCS-2 code except *, /, \, :, ;, and ?^[115]	?	same as ISO 9660:1988	same as ISO 9660:1988	?
Level-D	6.3	A–Z, 0–9	DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67	34,359,738,368 words (2³⁵); 206,158,430,208 SIXBIT bytes	Approx 12 GiB (12.88 GB) (64?×?178 MiB (186.6 MB))	?
Lustre	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	16 EiB (18.44 EB) on ZFS	16 EiB (18.44 EB)	?
MFS	255 bytes	Any byte except `:`	No path (flat filesystem)	256 MiB (268.4 MB)	256 MiB (268.4 MB)	?
MicroDOS file system	14 bytes	?	?	16 MiB (16.77 MB)	32 MiB (33.55 MB)	?
Minix V1 FS	14 or 30 bytes, set at filesystem creation time	Any byte except NUL^[cc]	No limit defined^[cd]	256.5 MiB (268.9 MB) ^[cs]	64 MiB (67.10 MB)	?
Minix V2 FS	14 or 30 bytes, set at filesystem creation time	Any byte except NUL^[cc]	No limit defined^[cd]	2 GiB (2.147 GB) ^[cs]	1 GiB (1.073 GB)	?
Minix V3 FS	60 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	2 GiB (2.147 GB)	4 GiB (4.294 GB)	?
NILFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	8 EiB (9.223 EB)	8 EiB (9.223 EB)	?
NOVA	255 bytes	Any byte except NUL, /^[cc]	No limit defined^[cd]	16 EiB (18.44 EB)	16 EiB (18.44 EB)	?
NSS	256 characters	Depends on namespace used^[ct]	Only limited by client	8 TiB (8.796 TB)	8 TiB (8.796 TB)	?
NTFS	255 characters	In Win32 namespace: any UTF-16 code unit (case-insensitive) except `/\:*"?<>\|` as well as NUL In POSIX namespace: any UTF-16 code unit (case-sensitive) except `/` as well as NUL^[116]	32,767 characters with each path component (directory or filename) up to 255 characters long^[cd]. However, the limit is approximate due to UNC, and some limitations may be removed on demand ^[117].	16 TiB (17.59 TB) to 8 PiB (9.007 PB)^[cu]^[118]	16 TiB (17.59 TB) to 8 PiB (9.007 PB)^[cu]^[118]	2³²
NWFS	80 bytes^[cv]	Depends on namespace used^[ct]	No limit defined^[cd]	4 GiB (4.294 GB)	1 TiB (1.099 TB)	?
OCFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	8 TiB (8.796 TB)	8 TiB (8.796 TB)	?
OCFS2	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	4 PiB (4.503 PB)	4 PiB (4.503 PB)	?
ODS-5	236 bytes^[cw]	?	4,096 bytes^[cx]	1 TiB (1.099 TB)	1 TiB (1.099 TB)	?
QFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	16 EiB (18.44 EB)^[cy]	4 PiB (4.503 PB)^[cy]	?
ReFS	255 UTF-16 characters^[119]	In Win32 namespace: any UTF-16 code unit (case-insensitive) except `/\:*"?<>\|` as well as NUL In POSIX namespace: any UTF-16 code unit (case-sensitive) except `/` as well as NUL^[119]^[120]	32,767 characters with each path component (directory or filename) up to 255 characters long^[119]	16 EiB (18.44 EB)^[119]^[121]	1 YiB (1.208 YB)^[119]	?
ReiserFS	4,032 bytes/255 characters	Any byte except NUL or `'/'`^[cc]	No limit defined^[cd]	8 TiB (8.796 TB)^[cz] (v3.6), 4 GiB (4.294 GB) (v3.5)	16 TiB (17.59 TB)	?
Reiser4	3,976 bytes	Any byte except `/` and NUL	No limit defined^[cd]	8 TiB (8.796 TB) on x86	?	?
Rock Ridge (extension to ISO 9660)	255 bytes	Any byte except NUL or /^[cc]	No limit defined^[cd]	same as ISO 9660:1988	same as ISO 9660:1988	?
RT-11	6.3	A–Z, 0–9, $	0 (no directory hierarchy)	33,554,432 bytes (65536?×?512)	33,554,432 bytes	?
SquashFS	256 bytes	?	No limit defined	16 EiB (18.44 EB)	16 EiB (18.44 EB)	?
UDF	255 bytes	Any Unicode except NUL	1,023 bytes^[da]	16 EiB (18.44 EB)	512 MiB (536.8 MB) to 16 TiB (17.59 TB)	?
UFS1	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	16 GiB (17.17 GB) to 256 TiB (281.4 TB)	16 EiB (18.44 EB)	Subdirectory per directory is 32,767^[123]
UFS2	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	512 GiB (549.7 GB) to 32 PiB (36.02 PB)	512 ZiB (604.4 ZB)^[124] (2⁷⁹ bytes)	Subdirectory per directory is 32,767^[123]
UniFS	No limit defined (depends on client)	?	No limit defined (depends on client)	Available cache space at time of write (depends on platform)	No limit defined	No limit defined
VaultFS	configurable (1024 default)	Any byte except NUL	No limit defined	No limit defined	No limit defined	No limit defined
Version 6 Unix file system (V6FS)	14 bytes	Any byte except NUL and `/`^[cc]	No limit defined^[cd]	16 MiB (16.77 MB)^[db]	32 MiB (33.55 MB)	?
Version 7 Unix file system (V7FS)	14 bytes	Any byte except NUL or `/`^[cc]	No limit defined^[cd]	1 GiB (1.073 GB)^[dc]	2 TiB (2.199 TB)	?
VMFS2	128	Any byte except NUL or `/`^[cc]	2,048	4 TiB (4.398 TB)^[dd]	64 TiB (70.36 TB)	?
VMFS3	128	Any byte except NUL or `/`^[cc]	2,048	2 TiB (2.199 TB)^[dd]	64 TiB (70.36 TB)	?
VxFS	255 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	16 EiB (18.44 EB)	?	?
XFS	255 bytes^[de]	Any byte except NUL or `/`^[cc]	No limit defined^[cd]	8 EiB (9.223 EB)^[df]	8 EiB (9.223 EB)^[df]	2⁶⁴
Xiafs	248 bytes	Any byte except NUL^[cc]	No limit defined^[cd]	64 MiB (67.10 MB)	2 GiB (2.147 GB)	?
ZFS	1023 bytes	Any Unicode except NUL	No limit defined^[cd]	16 EiB (18.44 EB)	281,474,976,710,656 YiB (2¹²⁸ bytes)	2¹²⁸
File system	Maximum filename length	Allowable characters in directory entries^[ca]	Maximum pathname length	Maximum file size	Maximum volume size^[cb]	Max number of files

Date ranges
File system	Start date (time)	End date (time)	Granularity (last modified time)
FAT12, FAT16, FAT32^[dg]	2025-08-10 00:00:00	2025-08-10 23:59:58	2 seconds
NTFS	2025-08-10	62025-08-10	0.0000001 seconds (100 nanoseconds)
exFAT ^[dh]	2025-08-10	2025-08-10	0.01 seconds (10 milliseconds)
ext2, ext3	2025-08-10	2025-08-10	1 second
ext4	2025-08-10	2025-08-10	0.000000001 seconds (1 nanosecond)
BtrFS	2025-08-10 00:00:00	2025-08-10 23:34:33	0.000000001 seconds (1 nanosecond)
JFS	unknown	unknown	0.000000001 seconds (1 nanosecond)
XFS	2025-08-10	2025-08-10	0.000000001 seconds (1 nanosecond)
ReiserFS	2025-08-10	2025-08-10	1 second
tux3	unknown	unknown	0.00390625 seconds (1/256th of a second)
ISO 9660^[127]	2025-08-10	2025-08-10	0.01 seconds (10 milliseconds)
UDF	2025-08-10	2025-08-10	0.000001 seconds (1 microsecond)
HFS Plus	2025-08-10	2025-08-10	1 second

Time granularity
Granularity	Sub-microsecond	Sub-millisecond	Sub-second	One second	Above one second
File systems	ext4, BtrFS, JFS, XFS, NTFS	UDF	exFAT, ISO 9660, tux3	ext2, ext3, ReiserFS, HFS Plus	FAT

Notes

^ IBM introduced JFS with the initial release of 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.
^ Microsoft first introduced FAT32 in MS-DOS 7.1 / Windows 95 OSR2 (OEM Service Release 2) and then later in 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.
^ Implemented in later versions as an extension
^ 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.
^ Particular Installable File System drivers and operating systems 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 DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.
^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
^ NTFS access control lists 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 Cygwin.
^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.^[12]
^ Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS
^ ^a ^b ^c ^d Access-control lists and MAC labels are layered on top of extended attributes.
^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ Some Installable File System drivers and operating systems 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.
^ Metadata is mostly checksummed,^[13] however Direct/indirect/triple-indirect block maps are not protected by checksums^[14]
^ Creation time stored since June 2015, xfsprogs version 3.2.3
^ ^a ^b ^c ^d ^e ^f 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.
^ ^a ^b 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.
^ ^a ^b 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.
^ Record Management Services (RMS) attributes include record type and size, among many others.
^ File permission in 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.
^ Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.
^ Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.
^ Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.
^ libburnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.
^ ^a ^b libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.
^ System V Release 4, and some other Unix systems, retrofitted symbolic links to their versions of the Version 7 Unix file system, although the original version didn't support them.
^ 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
^ Optional journaling of data
^ As of Windows Vista, NTFS fully supports symbolic links.^[16] NTFS 3.0 (Windows 2000) and higher can create junctions, which allow entire directories (but not individual files) to be mapped to elsewhere in the directory tree of the same partition (file system). These are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.
^ ^a ^b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
^ ^a ^b 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.
^ 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.
^ 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.^[18] 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.^[19]^[20]
^ 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).^[21]
^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling)
^ Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE ^[23]^[24]
^ ^a ^b ^c ^d ^e ^f UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
^ Linux kernel versions 2.6.12 and newer.
^ ^a ^b ^c ^d Off by default.
^ Full block journaling for ReiserFS was added to Linux 2.6.8.
^ Optionally no on IRIX and Linux.
^ Particular Installable File System drivers and operating systems may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.
^ ^a ^b ^c ^d 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.
^ ^a ^b 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.^[27]
^ ^a ^b Available only in the "NFS" namespace.
^ ^a ^b These are referred to as "aliases".
^ ^a ^b 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.
^ 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.
^ 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 occurred. This option may be useful on a personal workstation or laptop, and perhaps less appropriate on a server.
^ Since Windows 10 Enterprise Insider Preview build 19536
^ ^a ^b 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.
^ ^a ^b only inside of Stacker 3/4 and DriveSpace 3 compressed volumes^[32]
^ Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.
^ HFS+ does not actually encrypt files: to implement 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.
^ Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
^ Applies to proprietary ZFS release 30 and ZFS On Linux. Encryption support is not yet available in all OpenZFS ports.^[39]^[40]^[41]
^ LZJB (optimized for performance while providing decent data compression)
LZ4 (faster & higher ratio than lzjb)
gzip levels: 1 (fastest) to 9 (best), default is 6
zstd positive: 1 (fastest) to 19 (best), default is 3
zstd negative: 1(best & default)-10, 20, 30, …, 100, 500, 1000(fastest)
zle: compresses runs of zeros.^[42]
^ disabling copy-on-write (COW) to prevent fragmentation also disables data checksumming
^ zlib levels: 1 to 9, default is 3
LZO (no levels) faster than ZLIB, worse ratio
zstd levels: -15 to 15, default is 3 (higher levels are not available and may not bring a significant improvement, lower levels are close to real time)^[43]
^ none
CRC-32C (default)
crc64
chacha20/poly1305 (When encryption is enabled. Encryption can only be specified for the entire filesystem, not per file or directory)^[44]
^ none (default)
The three currently supported algorithms are gzip, LZ4, zstd.
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.^[45]
^ * 3.7: Added file-level snapshot (only available in Windows Server 2022).^[46]
^ ^a ^b 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.^[47]
^ * 3.9: Added post process compression with LZ4 and ZSTD and transparent decompression.
^ ^a ^b ^c 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.
^ ^a ^b ^c ^d With software based on GNU Parted.
^ ^a ^b Variable block size refers to systems which support different block sizes on a per-file basis. This is similar to extents but a slightly different implementational choice.
^ Only for "stuffed" inodes
^ ^a ^b ^c ^d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
^ ^a ^b ^c Fragments were planned, but never actually implemented on ext2 and ext3.
^ Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.
^ ^a ^b Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.
^ In "extents" mode.
^ 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.
^ Supported using only EVMS; not currently supported using LVM
^ ^a ^b ^c ^d Provided in Plan 9 from User Space
^ ^a ^b FUSE based driver available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.
^ Filesystem driver "Dokany" available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.
^ ^a ^b ^c ^d ^e 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 systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
^ ^a ^b ^c ^d ^e 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 KiB (131.0 KB) for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KiB (32.76 KB)).
^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai ^aj ^ak ^al ^am 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.
^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai ^aj ^ak ^al ^am ^an ^ao The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. Limited by its Current Directory Structure (CDS), DOS does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 bytes 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 PATH_MAX constant have a limit of 4,096 bytes on Linux but this can be worked around. Linux itself has no hard path length limits.^[125]^[126]
^ Varies wildly according to block size and fragmentation of block allocation groups.
^ ^a ^b ^c ^d ^e ^f Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 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.
^ ^a ^b On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size.
^ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB (34.35 GB). This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid.^[106]
^ Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). ^[108]
^ Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). ^[109]
^ ^a ^b Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB (2.199 TB). For 32-bit 2.6 kernels it is 16 TiB (17.59 TB). For 64-bit 2.6 kernels it is 8 EiB (9.223 EB).
^ 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.
^ 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.
^ 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.
^ 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 GiB (68.71 GB).
^ ISO 9660#Restrictions
^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB (4.294 GB) in size. See ISO 9660#The 2 GiB (2.147 GB) (or 4 GiB (4.294 GB) depending on implementation) file size limit
^ 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.
^ ^a ^b Sparse files can be larger than the file system size, even though they can't contain more data.
^ ^a ^b NSS allows files to have multiple names, in separate namespaces.
^ ^a ^b This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TiB (281.4 TB) and the file size to 16 TiB (17.59 TB) respectively; in Windows 10 version 1709, the limit is 8 PiB (9.007 PB) when using 2 MiB (2.097 MB) cluster size.
^ 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.
^ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
^ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
^ ^a ^b 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.
^ ReiserFS has a theoretical maximum file size of 1 EiB (1.152 EB), but "page cache limits this to 8 Ti on architectures with 32 bit int"^[122]
^ This restriction might be lifted in newer versions.
^ 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 MB.
^ 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 System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4 GiB (4.294 GB).
^ ^a ^b 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.
^ Note that the filename can be much longer XFS#Extended attributes
^ ^a ^b XFS has a limitation under Linux 2.4 of 64 TiB (70.36 TB) file size, but Linux 2.4 only supports a maximum block size of 2 TiB (2.199 TB). This limitation is not present under IRIX.
^ FAT has different granularities for different time stamps. Only the date of last access is recorded, not the time. The file creation time (treated as "change time" by Linux for this specific file system) is recorded more granularly, at a hundredth of a second. FAT: General Overview of On-Disk Format, page 23.
^ exFAT records 10-millisecond increments for last modification and creation time stamps, but only one second for the last access time stamp. exFAT file system specification

References

^ Shustek, Len (2025-08-10). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.
^ Kildall, Gary Arlen (2025-08-10) [1993]. Kildall, Scott; Kildall, Kristin (eds.). "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family. Retrieved 2025-08-10.
^ Mace, Scott (2025-08-10). "Extensions to MS-DOS Run CD-ROM". InfoWorld. 8 (38): 1, 8. Retrieved 2025-08-10.
^ Warren, David (20 October 1993). "Polycenter File System - - HELP". Archived from the original on 9 March 2012.
^ "Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System" (Press release). Santa Clara, Calif.: Sun Microsystems, Inc. 12 September 2007. Archived from the original on 2 October 2007.
^ Matthew Dillon (2025-08-10). "hammer2/DESIGN". BSD Cross Reference. DragonFly BSD. Retrieved 2025-08-10.
^ "Huawei announces the EROFS Linux file system intended for Android devices". XDA Developer. June 1, 2018.
^ "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–26 .. 1–32.
^ "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–4 .. 1–12.
^ "Format of the Unix 6 file system" (PDF). Archived from the original (PDF) on 2025-08-10. Retrieved 2025-08-10.
^ See dinode structure on page 355 (FILESYS(5)) of "Unix Programmers Manual" (PDF) (Seventh ed.). Murray Hill, New Jersey: Bell Telephone Laboratories. January 1979. Retrieved 2025-08-10.
^ "Mandatory Integrity Control". Microsoft Docs. 25 March 2021. Retrieved 2025-08-10.
^ "Ext4 Disk Layout".
^ "Ext4 Metadata Checksums".
^ ECMA-119 - Volume and file structure of CDROM for information interchange - 4th edition, June 2019 at the Wayback Machine (archived 2025-08-10)
^ Mark Russinovich (February 2007). "Windows Administration: Inside the Windows Vista Kernel: Part 1". TechNet.
^ Siracusa, John (2025-08-10). "Mac OS X 10.7 Lion: the Ars Technica review". Ars Technica. Retrieved 14 December 2017. 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.
^ newfs_hfs(8) – Darwin and macOS System Manager's Manual
^ "File System Comparisons". Apple. Archived from the original on 2025-08-10. (hasn't been updated to discuss HFSX)
^ "Technical Note TN1150: HFS Plus Volume Format". Apple. (Very technical overview of HFS Plus and HFSX.)
^ "fslogger". Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ McKusick, Marshall Kirk; Roberson, Jeff. "Journaled Soft-updates" (PDF).
^ "NewFAQs - FreeBSD Wiki".
^ "FreeBSD 9.0-RELEASE Announcement".
^ "EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2".
^ "2. High Level Design — The Linux Kernel documentation § 2.10. Inline Data". www.kernel.org. Retrieved 2025-08-10.
^ "Filesystem Events tracked by NSure".
^ "Universal Disk Format Specification – Revision 2.60" (PDF). p. 34. This file, when small, can be embedded in the [Information Control Block] that describes it.
^ "zpool-features.7 - OpenZFS documentation". openzfs.github.io. Retrieved 2025-08-10.
^ ^a ^b "Inline files — BTRFS documentation".
^ "clonefile(2)". The cloned file dst shares its data blocks with the src file [..]
^ ^a ^b ^c "DMSDOS CVF module" (dmsdoc.doc). 0.9.2.0. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10. 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.
^ "About Data Deduplication". 31 May 2018.
^ "Ext4 encryption".
^ ^a ^b "Red Hat: What is bitrot?".
^ "F2FS encryption".
^ "mkfs.xfs(8) from xfsprogs 5.10.0-4". By default, mkfs.xfs [..] will enable the reflink [=deduplication] feature.
^ "JFS data compression". IBM. Retrieved 2025-08-10.
^ Moffat, Darren (July 2012). "How to Manage ZFS Data Encryption". Retrieved 2025-08-10.
^ "Release zfs-0.8.0". GitHub. 2025-08-10.
^ "Feature Flags - OpenZFS".
^ "zfsprops.7 — OpenZFS documentation". GitHub. 2025-08-10. Retrieved 2025-08-10.
^ "Compression — BTRFS documentation". GitHub. 2025-08-10. Retrieved 2025-08-10.
^ ^a ^b Overstreet, Kent (18 Dec 2021). "bcachefs: Principles of Operation" (PDF). Retrieved 10 May 2023.
^ "bcachefs/ Compression". 11 Sep 2023. Retrieved 14 Jan 2024.
^ "Resilient File System (ReFS) overview". Microsoft. Archived from the original on 25 September 2020. Retrieved 22 September 2020.
^ "Resilient File System Overview". Microsoft Docs. Microsoft. 29 February 2012. Retrieved 24 August 2022.
^ "IBM's Journaled File System (JFS) for Linux".
^ "Growing an XFS File System".
^ ^a ^b "Shrinking Support - xfs.org". XFS Wiki. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ "Frequently Asked Questions (Old Wiki)". Retrieved 5 May 2018.
^ "Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem".
^ "ntfsresize(8)".
^ ^a ^b ^c resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands
^ "Resizing File Systems".
^ "Resize reiserfs". Reiserfs wiki.
^ "Just Enough Operating System (JeOS): Technical Information | SUSE". www.suse.com. Retrieved 28 April 2018.
^ "nilfs-resize(8)".
^ Top-level vdevs can only be removed if the primary pool storage does not contain a top-level raidz vdev, all top-level vdevs have the same sector size, and the keys for all encrypted datasets are loaded. "MAN Pages zpool-remove.8".
^ "Resizing and Growing Disks".
^ "Mac users, meet APFS: macOS's new file system - ZDNet". ZDNet.
^ "Apple File System Guide - FAQ".
^ ^a ^b "CVF Region: MDFAT".
^ ^a ^b "Mapping DOS FAT to MDFAT".
^ "[base] Revision 216796".
^ "Newfs(8)".
^ Jaeguk Kim (2025-08-10). "[PATCH 2/3] f2fs: Introduce FITRIM in f2fs_ioctl". linux-kernel (Mailing list).
^ "Reiser4 discard support". Reiser4 FS Wiki.
^ "XFS Adds Shared Data Extents For Linux 4.9".
^ Android Kernel File System Support (Documentation). Android Open Source Project. Retrieved 2025-08-10.
^ "GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)". GitHub. 2025-08-10.
^ "APFS module for linux, with experimental write support. This tree is just for development, please use linux-apfs-oot instead.: Linux-apfs/Linux-apfs". GitHub. 2025-08-10.
^ Namjae Jeon (20 January 2020). "[PATCH v12 00/13] add the latest exfat driver". linux-kernel (Mailing list). Retrieved 18 December 2021.
^ "NTFS3 Pull Request acceptance".
^ ^a ^b "Paragon HFS+ for Windows 10".
^ "Porting an Ancient Filesystem to Modern Linux". Time To Pull The Plug. Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ "A port of the xiafs filesystem to modern Linux kernels". Github (cdtk). 2025-08-10.
^ ^a ^b ^c "Paragon ExtFS for Mac".
^ ^a ^b "Explore2fs". chrysocome.net.
^ ^a ^b "Paragon ExtFS for Windows".
^ ^a ^b "FAQ". Ext2 Installable File System For Windows. (Provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.)
^ ^a ^b Branten, Bo. "Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)". Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ ^a ^b "FreeBSD Handbook".
^ Hanselman, Scott (2025-08-10). "WSL2 can now mount Linux ext4 disks directly". Newsletter of Wonderful Things. Retrieved 2025-08-10.
^ Microsoft Corp. (2025-08-10). "Windows technical documentation: Windows development environment: Windows Subsystem for Linux". Microsoft Learn (published 2025-08-10). Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ "Lustre Wiki".
^ "FreeBSD 10.4 MAN page - reiserfs". www.freebsd.org. Retrieved 2025-08-10.
^ "FreeBSD 11 and Reiserfs". www.linuxquestions.org. 2025-08-10. Retrieved 2025-08-10.
^ "'svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC". marc.info. Retrieved 2025-08-10.
^ "About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide". Retrieved 2025-08-10.
^ "ZFS Filesystem for FUSE/Linux". Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013.
^ "ZFS on Linux". Lawrence Livermore National Laboratory.
^ Kim, Arnold (4 October 2007). "Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard". Mac Rumors.
^ "OpenZFS on Windows".
^ "WinBtrfs". Github (maharmstone). 2025-08-10.
^ "squashfs-tools". Freshports.
^ "fusefs-squashfuse". Freshports.
^ "Frequently Asked Questions".
^ "Volume Format Comparison".
^ "CephFS Maximum File Sizes and Performance".
^ "CephFS Directory Fragmentation".
^ "ExFAT: File Name Directory Entry".
^ ^a ^b ^c ^d "File System Functionality Comparison". Microsoft Docs. Microsoft. 2025-08-10. Retrieved 2025-08-10.
^ Vimal A.R (16 July 2016). "Max file-name length in an EXT4 file system". arvimal.blog. Archived from the original on 28 February 2021.
^ "Interviews/EricSandeen". Fedora Project Wiki. 9 June 2008.
^ "Limitations of the FAT32 File System in Windows XP". Microsoft. Archived from the original on 2025-08-10.
^ "GEMDOS Overview".
^ "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2025-08-10.
^ "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2025-08-10.
^ Matthew Dillon. "HAMMER2 Design Document". we can allow filenames up to 1023 bytes long
^ Matthew Dillon (June 21, 2008). "The HAMMER Filesystem" (PDF).
^ "Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits". support.apple.com. July 26, 2016. Archived from the original on 2025-08-10.
^ "Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits". support.apple.com. February 20, 2012.
^ "SFS file system". www.ibm.com. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ "Joliet Specification". 22 May 1995. Archived from the original on 14 April 2009.
^ Russon, Richard; Fledel, Yuval. "NTFS Documentation" (PDF).
^ alvinashcraft. "Maximum Path Length Limitation - Win32 apps". learn.microsoft.com. Retrieved 2025-08-10.
^ ^a ^b "NTFS overview". Microsoft Docs. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.
^ ^a ^b ^c ^d ^e Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS".
^ Amigo (2025-08-10). "Invalid Characters in File Names". Amigo's Technical Notes. Retrieved 2025-08-10.
^ "Resilient File System (ReFS) overview". Microsoft Docs. Retrieved 2025-08-10.
^ "FAQ". namesys. 15 October 2003. Archived from the original on 19 July 2006.
^ ^a ^b "Maximum Number of UFS Subdirectories". Oracle. Retrieved 2025-08-10.
^ "Frequently Asked Questions for FreeBSD 9.X and 10.X". FreeBSD Documentation Project. Retrieved 2025-08-10. If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KiB (32.76 KB) => 16 Exa * 32 KiB (32.76 KB) => 512 ZettaBytes.
^ "PATH_MAX Is Tricky". Evan Klitzke’s web log.
^ "PATH_MAX simply isn't". Insane Coding. 2025-08-10.
^ ECMA-119 - Volume and file structure of CDROM for information interchange - 4th edition, June 2019 at the Wayback Machine (archived 2025-08-10)

External links

A speed comparison of filesystems on Linux 2.4.5 (archived)
Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch Archived 2025-08-10 at the Wayback Machine (April 23, 2006)
Block allocation strategies of various filesystems
What are the (dis)advantages of ext4, ReiserFS, JFS, and XFS? - Unix & Linux Stack Exchange

[note-11-4] IBM introduced JFS with the initial release of 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.

[note-10-6] Microsoft first introduced FAT32 in MS-DOS 7.1 / Windows 95 OSR2 (OEM Service Release 2) and then later in 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.

[10] Implemented in later versions as an extension

[fat-ctime-15] 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.

[note-22-16] Particular Installable File System drivers and operating systems 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 DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.

[note-14-17] The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.

[note-5-18] NTFS access control lists 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 Cygwin.

[20] As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.^[12]

[21] Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS

[note-33-22] Access-control lists and MAC labels are layered on top of extended attributes.

[note-32-23] Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).

[note-23-24] ^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ Some Installable File System drivers and operating systems 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.

[27] Metadata is mostly checksummed,^[13] however Direct/indirect/triple-indirect block maps are not protected by checksums^[14]

[note-35-28] Creation time stored since June 2015, xfsprogs version 3.2.3

[note-31-29] ^ ^a ^b ^c ^d ^e ^f 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.

[note-19-30] 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.

[note-29-31] 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.

[note-17-32] Record Management Services (RMS) attributes include record type and size, among many others.

[note-61-33] File permission in 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.

[note-69-34] Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.

[note-60-35] Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.

[36] Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.

[37] urnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.

[note-78-38] urnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.

[note-59-40] System V Release 4, and some other Unix systems, retrofitted symbolic links to their versions of the Version 7 Unix file system, although the original version didn't support them.

[41] 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

[42] Optional journaling of data

[44] As of Windows Vista, NTFS fully supports symbolic links.^[16] NTFS 3.0 (Windows 2000) and higher can create junctions, which allow entire directories (but not individual files) to be mapped to elsewhere in the directory tree of the same partition (file system). These are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.

[note-37-45] NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.

[note-36-46] 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.

[note-48-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.

[52] 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.^[18] 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.^[19]^[20]

[54] 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).^[21]

[note-66-55] "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling)

[59] Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE ^[23]^[24]

[note-38-60] ^ ^a ^b ^c ^d ^e ^f UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.

[note-65-61] Linux kernel versions 2.6.12 and newer.

[note-62-62] Off by default.

[note-44-65] Full block journaling for ReiserFS was added to Linux 2.6.8.

[note-40-66] Optionally no on IRIX and Linux.

[67] Particular Installable File System drivers and operating systems may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.

[note-20-68] 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.

[note-6-70] 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.^[27]

[note-53-71] Available only in the "NFS" namespace.

[note-18-72] These are referred to as "aliases".

[note-56-74] 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.

[note-80-76] 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.

[78] 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 occurred. This option may be useful on a personal workstation or laptop, and perhaps less appropriate on a server.

[79] Since Windows 10 Enterprise Insider Preview build 19536

[note-82-80] 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.

[FATcompress-83] y inside of Stacker 3/4 and DriveSpace 3 compressed volumes^[32]

[note-NTFS-Dedup-84] Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.

[note-77-86] HFS+ does not actually encrypt files: to implement 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.

[note-50-90] Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.

[note-70-93] VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.

[zfscrypt-97] Applies to proprietary ZFS release 30 and ZFS On Linux. Encryption support is not yet available in all OpenZFS ports.^[39]^[40]^[41]

[99] LZJB (optimized for performance while providing decent data compression)
LZ4 (faster & higher ratio than lzjb)
gzip levels: 1 (fastest) to 9 (best), default is 6
zstd positive: 1 (fastest) to 19 (best), default is 3
zstd negative: 1(best & default)-10, 20, 30, …, 100, 500, 1000(fastest)
zle: compresses runs of zeros.^[42]

[100] sabling copy-on-write (COW) to prevent fragmentation also disables data checksumming

[102] zlib levels: 1 to 9, default is 3
LZO (no levels) faster than ZLIB, worse ratio
zstd levels: -15 to 15, default is 3 (higher levels are not available and may not bring a significant improvement, lower levels are close to real time)^[43]

[104] 
CRC-32C (default)
crc64
chacha20/poly1305 (When encryption is enabled. Encryption can only be specified for the entire filesystem, not per file or directory)^[44]

[106] (default)
The three currently supported algorithms are gzip, LZ4, zstd.
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.^[45]

[108] * 3.7: Added file-level snapshot (only available in Windows Server 2022).^[46]

[ReFSecc-110] 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.^[47]

[111] * 3.9: Added post process compression with LZ4 and ZSTD and transparent decompression.

[note-79-112] 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.

[libparted-113] With software based on GNU Parted.

[note-41-127] Variable block size refers to systems which support different block sizes on a per-file basis. This is similar to extents but a slightly different implementational choice.

[132] Only for "stuffed" inodes

[note-45-133] Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.

[note-47-136] Fragments were planned, but never actually implemented on ext2 and ext3.

[note-75-137] Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.

[note-73-139] Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.

[note-39-140] In "extents" mode.

[note-42-143] 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.

[EVMS-165] Supported using only EVMS; not currently supported using LVM

[fossil-p9p-166] Provided in Plan 9 from User Space

[cephfs-fuse-driver-174] FUSE based driver available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.

[cephfs-dokany-driver-175] Filesystem driver "Dokany" available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.

[note-25-176] 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 systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.

[note-4-177] 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 KiB (131.0 KB) for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KiB (32.76 KB)).

[note-26-178] ^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai ^aj ^ak ^al ^am 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.

[note-12-179] ^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai ^aj ^ak ^al ^am ^an ^ao The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. Limited by its Current Directory Structure (CDS), DOS does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 bytes 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 PATH_MAX constant have a limit of 4,096 bytes on Linux but this can be worked around. Linux itself has no hard path length limits.^[125]^[126]

[note-3-182] Varies wildly according to block size and fragmentation of block allocation groups.

[note-24-189] ^ ^a ^b ^c ^d ^e ^f Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 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.

[note-fsize-190] On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size.

[192] While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB (34.35 GB). This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid.^[106]

[note-83-195] Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). ^[108]

[note-84-197] Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). ^[109]

[note-63-198] Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB (2.199 TB). For 32-bit 2.6 kernels it is 16 TiB (17.59 TB). For 64-bit 2.6 kernels it is 8 EiB (9.223 EB).

[note-1-201] 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.

[note-2-202] 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.

[note-27-205] 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.

[note-13-206] 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 GiB (68.71 GB).

[208] ISO 9660#Restrictions

[209] Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB (4.294 GB) in size. See ISO 9660#The 2 GiB (2.147 GB) (or 4 GiB (4.294 GB) depending on implementation) file size limit

[210] 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.

[note-file-size-vs-filesystem-size-212] Sparse files can be larger than the file system size, even though they can't contain more data.

[note-28-213] NSS allows files to have multiple names, in separate namespaces.

[note-55-216] This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TiB (281.4 TB) and the file size to 16 TiB (17.59 TB) respectively; in Windows 10 version 1709, the limit is 8 PiB (9.007 PB) when using 2 MiB (2.097 MB) cluster size.

[note-52-218] 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.

[note-15-219] Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.

[note-16-220] Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.

[note-72-221] 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.

[226] ReiserFS has a theoretical maximum file size of 1 EiB (1.152 EB), but "page cache limits this to 8 Ti on architectures with 32 bit int"^[122]

[note-43-227] This restriction might be lifted in newer versions.

[note-57-232] 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 MB.

[note-58-233] 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 System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4 GiB (4.294 GB).

[note-74-234] 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.

[235] Note that the filename can be much longer XFS#Extended attributes

[note-9-236] XFS has a limitation under Linux 2.4 of 64 TiB (70.36 TB) file size, but Linux 2.4 only supports a maximum block size of 2 TiB (2.199 TB). This limitation is not present under IRIX.

[237] FAT has different granularities for different time stamps. Only the date of last access is recorded, not the time. The file creation time (treated as "change time" by Linux for this specific file system) is recorded more granularly, at a hundredth of a second. FAT: General Overview of On-Disk Format, page 23.

[238] xFAT records 10-millisecond increments for last modification and creation time stamps, but only one second for the last access time stamp. exFAT file system specification

[Shustek_2016-1] Shustek, Len (2025-08-10). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.

[Kildall_1993-2] Kildall, Gary Arlen (2025-08-10) [1993]. Kildall, Scott; Kildall, Kristin (eds.). "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family. Retrieved 2025-08-10.

[3] Mace, Scott (2025-08-10). "Extensions to MS-DOS Run CD-ROM". InfoWorld. 8 (38): 1, 8. Retrieved 2025-08-10.

[5] Warren, David (20 October 1993). "Polycenter File System - - HELP". Archived from the original on 9 March 2012.

[7] "Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System" (Press release). Santa Clara, Calif.: Sun Microsystems, Inc. 12 September 2007. Archived from the original on 2 October 2007.

[hammer2_design-8] Matthew Dillon (2025-08-10). "hammer2/DESIGN". BSD Cross Reference. DragonFly BSD. Retrieved 2025-08-10.

[9] "Huawei announces the EROFS Linux file system intended for Android devices". XDA Developer. June 1, 2018.

[11] "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–26 .. 1–32.

[12] "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–4 .. 1–12.

[Unixv6-13] "Format of the Unix 6 file system" (PDF). Archived from the original (PDF) on 2025-08-10. Retrieved 2025-08-10.

[Unixv7-14] See dinode structure on page 355 (FILESYS(5)) of "Unix Programmers Manual" (PDF) (Seventh ed.). Murray Hill, New Jersey: Bell Telephone Laboratories. January 1979. Retrieved 2025-08-10.

[19] "Mandatory Integrity Control". Microsoft Docs. 25 March 2021. Retrieved 2025-08-10.

[25] "Ext4 Disk Layout".

[26] "Ext4 Metadata Checksums".

[39] ECMA-119 - Volume and file structure of CDROM for information interchange - 4th edition, June 2019 at the Wayback Machine (archived 2025-08-10)

[43] Mark Russinovich (February 2007). "Windows Administration: Inside the Windows Vista Kernel: Part 1". TechNet.

[47] Siracusa, John (2025-08-10). "Mac OS X 10.7 Lion: the Ars Technica review". Ars Technica. Retrieved 14 December 2017. 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.

[49] newfs_hfs(8) – Darwin and macOS System Manager's Manual

[50] "File System Comparisons". Apple. Archived from the original on 2025-08-10. (hasn't been updated to discuss HFSX)

[51] "Technical Note TN1150: HFS Plus Volume Format". Apple. (Very technical overview of HFS Plus and HFSX.)

[53] "fslogger". Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[56] McKusick, Marshall Kirk; Roberson, Jeff. "Journaled Soft-updates" (PDF).

[57] "NewFAQs - FreeBSD Wiki".

[58] "FreeBSD 9.0-RELEASE Announcement".

[63] "EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2".

[64] "2. High Level Design — The Linux Kernel documentation § 2.10. Inline Data". www.kernel.org. Retrieved 2025-08-10.

[69] "Filesystem Events tracked by NSure".

[73] "Universal Disk Format Specification – Revision 2.60" (PDF). p. 34. This file, when small, can be embedded in the [Information Control Block] that describes it.

[75] "zpool-features.7 - OpenZFS documentation". openzfs.github.io. Retrieved 2025-08-10.

[btrfs-documentation-inline-files-77] "Inline files — BTRFS documentation".

[81] "clonefile(2)". The cloned file dst shares its data blocks with the src file [..]

[DMSDOS-82] "DMSDOS CVF module" (dmsdoc.doc). 0.9.2.0. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10. 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.

[85] "About Data Deduplication". 31 May 2018.

[note-67-87] "Ext4 encryption".

[redhat-ext4andxfsnobitrotprotection-88] "Red Hat: What is bitrot?".

[note-68-89] "F2FS encryption".

[91] "mkfs.xfs(8) from xfsprogs 5.10.0-4". By default, mkfs.xfs [..] will enable the reflink [=deduplication] feature.

[92] "JFS data compression". IBM. Retrieved 2025-08-10.

[94] Moffat, Darren (July 2012). "How to Manage ZFS Data Encryption". Retrieved 2025-08-10.

[95] "Release zfs-0.8.0". GitHub. 2025-08-10.

[96] "Feature Flags - OpenZFS".

[98] "zfsprops.7 — OpenZFS documentation". GitHub. 2025-08-10. Retrieved 2025-08-10.

[101] "Compression — BTRFS documentation". GitHub. 2025-08-10. Retrieved 2025-08-10.

[b.PoO-103] Overstreet, Kent (18 Dec 2021). "bcachefs: Principles of Operation" (PDF). Retrieved 10 May 2023.

[105] "bcachefs/ Compression". 11 Sep 2023. Retrieved 14 Jan 2024.

[TechNet-107] "Resilient File System (ReFS) overview". Microsoft. Archived from the original on 25 September 2020. Retrieved 22 September 2020.

[109] "Resilient File System Overview". Microsoft Docs. Microsoft. 29 February 2012. Retrieved 24 August 2022.

[114] "IBM's Journaled File System (JFS) for Linux".

[115] "Growing an XFS File System".

[xfs-shrink-116] "Shrinking Support - xfs.org". XFS Wiki. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[wiki-faq-old-117] "Frequently Asked Questions (Old Wiki)". Retrieved 5 May 2018.

[118] "Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem".

[119] "ntfsresize(8)".

[unix.com-120] resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands

[121] "Resizing File Systems".

[122] "Resize reiserfs". Reiserfs wiki.

[123] "Just Enough Operating System (JeOS): Technical Information | SUSE". www.suse.com. Retrieved 28 April 2018.

[124] "nilfs-resize(8)".

[125] Top-level vdevs can only be removed if the primary pool storage does not contain a top-level raidz vdev, all top-level vdevs have the same sector size, and the keys for all encrypted datasets are loaded. "MAN Pages zpool-remove.8".

[126] "Resizing and Growing Disks".

[128] "Mac users, meet APFS: macOS's new file system - ZDNet". ZDNet.

[129] "Apple File System Guide - FAQ".

[CVF808-130] "CVF Region: MDFAT".

[CVF814-131] "Mapping DOS FAT to MDFAT".

[134] "[base] Revision 216796".

[135] "Newfs(8)".

[138] Jaeguk Kim (2025-08-10). "[PATCH 2/3] f2fs: Introduce FITRIM in f2fs_ioctl". linux-kernel (Mailing list).

[141] "Reiser4 discard support". Reiser4 FS Wiki.

[142] "XFS Adds Shared Data Extents For Linux 4.9".

[144] Android Kernel File System Support (Documentation). Android Open Source Project. Retrieved 2025-08-10.

[145] "GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)". GitHub. 2025-08-10.

[146] "APFS module for linux, with experimental write support. This tree is just for development, please use linux-apfs-oot instead.: Linux-apfs/Linux-apfs". GitHub. 2025-08-10.

[147] Namjae Jeon (20 January 2020). "[PATCH v12 00/13] add the latest exfat driver". linux-kernel (Mailing list). Retrieved 18 December 2021.

[NTFS3_Pull_Request_acceptance-148] "NTFS3 Pull Request acceptance".

[Paragon_HFS-149] "Paragon HFS+ for Windows 10".

[Porting_an_Ancient_Filesystem_to_Modern_Linux-150] "Porting an Ancient Filesystem to Modern Linux". Time To Pull The Plug. Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[Github_modern-xiafs-151] "A port of the xiafs filesystem to modern Linux kernels". Github (cdtk). 2025-08-10.

[Paragon_ExtFS_for_Mac-152] "Paragon ExtFS for Mac".

[explore2fs-153] "Explore2fs". chrysocome.net.

[Paragon_ExtFS_for_Windows-154] "Paragon ExtFS for Windows".

[Ext2_IFS_for_Windows-155] "FAQ". Ext2 Installable File System For Windows. (Provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.)

[Ext2fs_Driver-156] Branten, Bo. "Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)". Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[ext3-157] "FreeBSD Handbook".

[158] Hanselman, Scott (2025-08-10). "WSL2 can now mount Linux ext4 disks directly". Newsletter of Wonderful Things. Retrieved 2025-08-10.

[159] Microsoft Corp. (2025-08-10). "Windows technical documentation: Windows development environment: Windows Subsystem for Linux". Microsoft Learn (published 2025-08-10). Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[lustre-160] "Lustre Wiki".

[161] "FreeBSD 10.4 MAN page - reiserfs". www.freebsd.org. Retrieved 2025-08-10.

[162] "FreeBSD 11 and Reiserfs". www.linuxquestions.org. 2025-08-10. Retrieved 2025-08-10.

[163] "'svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC". marc.info. Retrieved 2025-08-10.

[164] "About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide". Retrieved 2025-08-10.

[zfs_on_fuse-167] "ZFS Filesystem for FUSE/Linux". Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013.

[ZoL-168] "ZFS on Linux". Lawrence Livermore National Laboratory.

[zfs_on_mac_os_x-169] Kim, Arnold (4 October 2007). "Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard". Mac Rumors.

[170] "OpenZFS on Windows".

[Github_btrfs-171] "WinBtrfs". Github (maharmstone). 2025-08-10.

[172] "squashfs-tools". Freshports.

[173] "fusefs-squashfuse". Freshports.

[180] "Frequently Asked Questions".

[181] "Volume Format Comparison".

[183] "CephFS Maximum File Sizes and Performance".

[184] "CephFS Directory Fragmentation".

[185] "ExFAT: File Name Directory Entry".

[msdn-FS-functionality-186] "File System Functionality Comparison". Microsoft Docs. Microsoft. 2025-08-10. Retrieved 2025-08-10.

[187] Vimal A.R (16 July 2016). "Max file-name length in an EXT4 file system". arvimal.blog. Archived from the original on 28 February 2021.

[ext4-features-188] "Interviews/EricSandeen". Fedora Project Wiki. 9 June 2008.

[191] "Limitations of the FAT32 File System in Windows XP". Microsoft. Archived from the original on 2025-08-10.

[193] "GEMDOS Overview".

[194] "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2025-08-10.

[196] "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2025-08-10.

[199] Matthew Dillon. "HAMMER2 Design Document". we can allow filenames up to 1023 bytes long

[200] Matthew Dillon (June 21, 2008). "The HAMMER Filesystem" (PDF).

[203] "Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits". support.apple.com. July 26, 2016. Archived from the original on 2025-08-10.

[204] "Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits". support.apple.com. February 20, 2012.

[207] "SFS file system". www.ibm.com. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[211] "Joliet Specification". 22 May 1995. Archived from the original on 14 April 2009.

[214] Russon, Richard; Fledel, Yuval. "NTFS Documentation" (PDF).

[215] vinashcraft. "Maximum Path Length Limitation - Win32 apps". learn.microsoft.com. Retrieved 2025-08-10.

[:0-217] "NTFS overview". Microsoft Docs. 2025-08-10. Archived from the original on 2025-08-10. Retrieved 2025-08-10.

[blogs.msdn.microsoft.com-222] Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS".

[223] Amigo (2025-08-10). "Invalid Characters in File Names". Amigo's Technical Notes. Retrieved 2025-08-10.

[224] "Resilient File System (ReFS) overview". Microsoft Docs. Retrieved 2025-08-10.

[225] "FAQ". namesys. 15 October 2003. Archived from the original on 19 July 2006.

[ufs-limit-228] "Maximum Number of UFS Subdirectories". Oracle. Retrieved 2025-08-10.

[229] "Frequently Asked Questions for FreeBSD 9.X and 10.X". FreeBSD Documentation Project. Retrieved 2025-08-10. If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KiB (32.76 KB) => 16 Exa * 32 KiB (32.76 KB) => 512 ZettaBytes.

[230] "PATH_MAX Is Tricky". Evan Klitzke’s web log.

[231] "PATH_MAX simply isn't". Insane Coding. 2025-08-10.

[239] ECMA-119 - Volume and file structure of CDROM for information interchange - 4th edition, June 2019 at the Wayback Machine (archived 2025-08-10)

[1]

[2]

[3]

[a]

[4]

[b]

[5]

[6]

[7]

[c]

[8]

[9]

[10]

[11]

[d]

[e]

[f]

[g]

[h]

[i]

[j]

[k]

[l]

[m]

[n]

[o]

[p]

[q]

[r]

[s]

[t]

[u]

[v]

[w]

[x]

[15]

[y]

[z]

[aa]

[ab]

[ac]

[ad]

[17]

[ae]

[af]

[ag]

[ah]

[22]

[ai]

[aj]

[ak]

[al]

[25]

[26]

[am]

[an]

[ao]

[ap]

[aq]

[ar]

[as]

[28]

[at]

[29]

[au]

[30]

[av]

[aw]

[ax]

[31]

[ay]

[az]

[33]

[ba]

[34]

[35]

[36]

[bb]

[37]

[38]

[bc]

[bd]

[be]

[bf]

[bg]

[bh]

[bi]

[bj]

[bk]

[bl]

[bm]

[bn]

[48]

[49]

[50]

[51]

[52]

[53]

[54]

[55]

一边脸大一边脸小是什么原因	择期什么意思	白细胞低吃什么药可以增加白细胞	沙茶酱是什么做的	落叶像什么
屎壳郎吃什么	增强记忆力吃什么	黑色素是什么	or发什么音	舌头起泡什么原因
cpk是什么意思啊	茶颜悦色什么好喝	梨是什么季节的水果	2月25号是什么星座	女人养颜抗衰老吃什么最好
血糖高早餐吃什么	浑身疼是什么原因	儿童荨麻疹吃什么药	膀胱过度活动症吃什么药	乳头状瘤是什么病

孕早期头疼是什么原因hcv9jop7ns3r.cn	调休是什么意思hcv8jop2ns9r.cn	荨麻疹是什么原因hcv9jop6ns1r.cn	6月是什么星座hcv8jop2ns9r.cn	颈椎病挂号挂什么科ff14chat.com
女人安全期是什么时候hcv9jop4ns7r.cn	多吃蔬菜有什么好处hcv7jop9ns7r.cn	小孩吃什么有营养chuanglingweilai.com	什么在千里cl108k.com	凌晨五点是什么时辰hcv8jop1ns6r.cn
腺肌瘤是什么病hcv8jop3ns2r.cn	绿萝叶子发黄是什么原因hcv9jop6ns6r.cn	蜗牛是什么生肖hcv8jop6ns9r.cn	减肥最快的方法是什么hcv8jop8ns4r.cn	舌头发苦是什么原因造成的hcv8jop5ns8r.cn
女人性冷淡是什么原因sanhestory.com	为什么不能送手表bjcbxg.com	为什么乳头会有白色分泌物hcv8jop6ns8r.cn	三亚免税店什么最便宜hcv8jop9ns6r.cn	乌鸦飞进家里什么征兆hcv8jop2ns8r.cn

晋中·砥砺奋进的五年