Comparison of file systems

On this page

List article

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 ¹ ²
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³
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 ⁴
VxFS	VERITAS	1991	SVR4.0
ext	Rémy Card	1992	Linux
AdvFS	DEC	1993⁵	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")	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 ⁶
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 ⁷	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 ⁸	2017	DragonFly BSD 5.0
EROFS	Huawei ⁹	2018	Android
VaultFS	Swiss Vault	2022	Linux / Unix

Metadata

File system	Stores file owner	POSIXfile permissions	Creation timestamps	Last access/read timestamps	Last metadata changetimestamps	Last archivetimestamps	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¹⁰	No	No	No	No	No	No	No
DECtape ¹¹	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 ¹²	No	No	Yes (date only)	No	No	No	No	No	No	Yes
Version 6 Unix file system (V6FS)¹³	Yes	Yes	No	Yes	No	No	No	No	No	No
Version 7 Unix file system (V7FS)¹⁴	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¹⁵	No	No	No	No¹⁶	No
HPFS	Yes¹⁷	No	Yes	Yes	No	No	No	?	Yes	No
NTFS	Yes	Yes¹⁸	Yes	Yes	Yes	No	Yes	Yes¹⁹	Yes	No
ReFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes²⁰	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²¹	Yes²²	No²³	No
UFS2	Yes	Yes	Yes	Yes	Yes	No	Yes²⁴	Yes²⁵	Yes	Partial
HAMMER	Yes	Yes	Yes	Yes	Yes	?	Yes	Yes	No	Yes
LFS	Yes	Yes	No	Yes	Yes	No	No	No	No	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²⁶	Yes²⁷	Yes	No
ext3	Yes	Yes	No	Yes	Yes	No	Yes²⁸	Yes²⁹	Yes	No
ext4	Yes	Yes	Yes	Yes	Yes	No	Yes³⁰	Yes³¹	Yes	Partial³²
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³³	Yes³⁴	Yes	No
GPFS	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes
GFS	Yes	Yes	No	Yes	Yes	No	Yes³⁵	Yes³⁶	Yes	No
NILFS	Yes	Yes	Yes	No	Yes	No	No	No	No	Yes
ReiserFS	Yes	Yes	No	Yes	Yes	No	Yes³⁷	Yes³⁸	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³⁹	Yes	Yes	No	Yes	Yes⁴⁰	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⁴¹	Yes⁴²	Yes	Yes⁴³	Yes	?	Yes⁴⁴ ⁴⁵	No
NWFS	Yes	?	Yes⁴⁶	Yes⁴⁷	Yes	Yes⁴⁸	Yes	?	Yes⁴⁹ ⁵⁰	No
ODS-5	Yes	Yes	Yes	?	?	Yes	Yes	?	Yes⁵¹	No
APFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VxFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes⁵²	No
UDF	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes
Fossil	Yes	Yes⁵³	No	Yes	Yes	No	No	No	No	No
ZFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes⁵⁴	Yes⁵⁵	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⁵⁶	Yes	No	No⁵⁷	No⁵⁸	No⁵⁹	No
Joliet ("CDFS")	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	POSIXfile permissions	Creation timestamps	Last access/read timestamps	Last metadata changetimestamps	Last archivetimestamps	Access control lists	Security/MAC labels	Extended attributes/Alternate data streams/forks	Metadata checksum/ECC

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⁶⁰	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⁶¹	Yes	Yes⁶²	Yes	Yes	No	No	?
HPFS	No	No	No	No	No	Yes	No	No	?
NTFS	Yes	Yes⁶³	No⁶⁴	Yes⁶⁵ (2000)	Yes⁶⁶	Yes	Yes	?	Yes (approximately 700 bytes)
HFS Plus	Yes⁶⁷	Yes	No	Yes⁶⁸	Optional⁶⁹	Yes	Yes⁷⁰	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⁷¹ ⁷² ⁷³	Yes	Yes	No	?	No
HAMMER	Yes	Yes	Yes	Yes	Yes	Yes	?	No	?
LFS	Yes	Yes	Yes⁷⁴	No	Yes	Yes	No	No	?
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⁷⁵	?
ext3	Yes	Yes	Yes (2001) ⁷⁶	Yes (2001)	Yes	Yes	No	Yes	?
ext4	Yes	Yes	Yes⁷⁷	Yes	Yes, optional ⁷⁸	Yes	No	Yes	Yes (approximately 160 bytes)⁷⁹
NOVA	Yes	Yes	No	Yes	Yes	Yes	No	Yes	?
F2FS	Yes	Yes	Yes⁸⁰	No	Yes	Yes	No	No	?
Lustre	Yes	Yes	Yes⁸¹	Yes	Yes	Yes	Yes	No	?
NILFS	Yes	Yes	Yes⁸²	No	Yes	Yes	No	No	?
ReiserFS	Yes	Yes	Yes⁸³	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⁸⁴	Yes	Yes⁸⁵	Yes	Yes	?	?
JFS	Yes	Yes	Yes	Yes (1990)	Yes⁸⁶	Yes	No	?	?
QFS	Yes	Yes	No	Yes	Yes	Yes	No	No	?
BFS	Yes	Yes	No	Yes	Yes	Yes	?	No	?
NSS	Yes	Yes	?	Yes	Yes⁸⁷	Yes⁸⁸	Yes⁸⁹	No	?
NWFS	Yes⁹⁰	Yes⁹¹	No	No	Yes⁹²	Yes⁹³	Yes⁹⁴	No	?
ODS-2	Yes	Yes⁹⁵	No	Yes	No	No	Yes	No	?
ODS-5	Yes	Yes⁹⁶	No	Yes	No	Yes	Yes	?	?
UDF	Yes	Yes	Yes⁹⁷	Yes⁹⁸	Yes	Yes	No	Yes	Yes⁹⁹
VxFS	Yes	Yes	Yes	No	Yes	Yes	Yes	?	?
Fossil	No	No	No	No	Yes	Yes	Yes	No	?
ZFS	Yes	Yes	Yes¹⁰⁰	No¹⁰¹	Yes	Yes	No	No	Yes (112 bytes)¹⁰²
Btrfs	Yes	Yes	Yes¹⁰³	No	Yes	Yes	?	?	?
Bcachefs	Yes	Yes	Yes¹⁰⁴	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¹⁰⁵	Yes	?	?	Yes¹⁰⁶	Yes	?	?	?
ISO 9660	No	No	No	No	No	No	No	No	?
Rock Ridge	Yes	Yes	No	No	Yes	Yes	No	No	?
Joliet ("CDFS")	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¹⁰⁷
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 ¹⁰⁸	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¹⁰⁹	No
FAT16 / FAT16B / FAT16X	No	No	No	No	No	No	Partial¹¹⁰	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¹¹¹ ¹¹²	No	No	No	Yes	No
HFS Plus	No	No¹¹³	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
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 ¹¹⁴	No	No¹¹⁵	No	No	No	No
NOVA	Yes	No	No	Yes	No	No	No	?
F2FS	No	Yes, experimental ¹¹⁶	No	No	No	No	Yes	No
Lustre	No	No	No	No	Yes	Yes	No	No
NILFS	Yes, continuous¹¹⁷	No	No	Yes	No	No	No	No
ReiserFS	No	No	No	No	No	No	No	No
Reiser4	?	Yes¹¹⁸	?	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¹¹⁹	No¹²⁰	No	No	No	No
JFS	?	No	?	No	No	No	only in JFS1 on AIX¹²¹	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¹²²	No	Yes	No	No	No	No	No
Fossil	Yes	No	Yes	No	No	No	Yes	No
ZFS	Yes	Yes¹²³	Yes	Yes	Yes	Yes	Yes¹²⁴	Yes
Btrfs	Yes	No	Yes	Yes¹²⁵	No	Yes	Yes¹²⁶	Yes
Bcachefs	Yes	Yes	No	Yes¹²⁷	No	Yes	Yes¹²⁸	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¹²⁹	No	Yes	No¹³⁰	No	No	No¹³¹	No¹³²
ISO 9660	No	No	No¹³³	No	No	No	No	No
Rock Ridge	No	No	No¹³⁴	No	No	No	No	No
Joliet ("CDFS")	No	No	No¹³⁵	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¹³⁶

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¹³⁷	No	Yes¹³⁸	No	No
FAT32 / FAT32X	misc.	Yes¹³⁹	No	Yes¹⁴⁰	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	?	?	?	?	?
SquashFS	Linux	No	No	No	No	No
NOVA	Linux	No	No	No	No	No
JFS ¹⁴¹	Linux	Yes	No	No	No	No
XFS ¹⁴²	Linux	No	Yes	No¹⁴³	No¹⁴⁴	No
Lustre ¹⁴⁵	Linux	?	Yes	No	No	Yes
F2FS ¹⁴⁶	Linux	Yes	No	No	No	No
NTFS ¹⁴⁷	Linux	Yes	No	Yes	No	No
ext2 ¹⁴⁸	Linux	Yes	No	Yes	No	No
ext3 ¹⁴⁹	Linux	Yes	Yes	Yes	No	No
ReiserFS ¹⁵⁰	Linux	Yes	Yes	Yes	No	No
Reiser4 ¹⁵¹	Linux	Yes	Yes	Yes	No	No
ext4 ¹⁵²	Linux	Yes	Yes	Yes	No	No
Btrfs ¹⁵³	Linux	Yes	Yes	Yes	Yes	Yes
Bcachefs ¹⁵⁴	Linux	Yes	Yes	No	No	Yes
NILFS ¹⁵⁵	Linux	No	Yes	No	Yes	No
ZFS	misc.	No	Yes	No	Yes	Partial¹⁵⁶
JFS2	AIX	Yes	Yes	Yes	Yes	No
UFS2 ¹⁵⁷	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¹⁵⁸	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¹⁵⁹ ¹⁶⁰
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)¹⁶¹	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes¹⁶²)	No	Partial (only inside of compressed volumes)¹⁶³	No	No	No	Yes (Linux)
FAT16 / FAT16B / FAT16X	Partial (only inside of compressed volumes)¹⁶⁴	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes¹⁶⁵)	No	Partial (only inside of compressed volumes)¹⁶⁶	No	No	No	Yes (Linux)
FAT32 / FAT32X	No	No	No	No	No	No	No	Yes (Linux)
GFS	Yes	No	Partial¹⁶⁷	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¹⁶⁸	No	No	No	No	?	No
UFS1	Yes	8:1¹⁶⁹	No	No	No	No	?	No
UFS2	Yes	8:1¹⁷⁰	No	No	Yes	No	?	Yes¹⁷¹ ¹⁷²
LFS	Yes	8:1¹⁷³	No	No	No	No	Yes	?
ext	Yes	No	No	No	No	No	No	No
Xiafs	Yes	No	No	No	No	No	?	?
ext2	Yes	No¹⁷⁴	No	No	No	No	No	Yes
ext3	Yes	No¹⁷⁵	No	No	No	No	No	Yes
ext4	Yes	No¹⁷⁶	No	Yes	No	Yes	No	Yes
NOVA	Yes	No	No	Yes	No	No	Yes	?
F2FS	Yes	No	No	Partial¹⁷⁷	No	Yes	Yes	Yes¹⁷⁸
Lustre	Yes	No	No	Yes	No	Yes	?	?
NILFS	Yes	No	No	No	No	Yes	Yes	Yes (Linux NILFS2)
ReiserFS	Yes	Yes¹⁷⁹	Yes	No	No	No	?	?
Reiser4	Yes	Yes¹⁸⁰	Yes	Yes¹⁸¹	No	Yes	?	Testing¹⁸²
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¹⁸³	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¹⁸⁴	No	No	No	No	?	?
ODS-5	?	No	No	Yes	No	No	?	?
VxFS	Yes	?	No	Yes	No	No	?	?
UDF	Yes	No	No	Yes	No	?¹⁸⁵	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	Yes	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	Yes¹⁸⁶	No	No	No	No
Rock Ridge	No	No	No	Yes¹⁸⁷	No	No	No	No
Joliet ("CDFS")	No	No	No	Yes¹⁸⁸	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¹⁸⁹	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 ¹⁹⁰
APFS	No	Partial (read-only with apfs-fuse¹⁹¹ or linux-apfs¹⁹²)	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,¹⁹³ 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 ¹⁹⁴	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+ ¹⁹⁵	Yes	No	?	Yes	No	?	No	No
Apple HFS Plus	No	Partial - writing support only to unjournalled FS	Yes	No	Needs Paragon HFS+ ¹⁹⁶	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
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 ¹⁹⁷ ¹⁹⁸	No	No	No	No	No	No	No	No	No	No	No
ext2	No	Yes	Needs Paragon ExtFS ¹⁹⁹ or ext2fsx	Partial (read-only, with explore2fs)²⁰⁰	Needs Paragon ExtFS ²⁰¹ or partial with Ext2 IFS²⁰² or ext2fsd²⁰³	No	Yes	No	Yes	?	?	?	No
ext3	No	Yes	Needs Paragon ExtFS ²⁰⁴ or partial with ext2fsx (journal not updated on writing)	Partial (read-only, with explore2fs)²⁰⁵	Needs Paragon ExtFS ²⁰⁶ or partial with Ext2 IFS²⁰⁷ or ext2fsd²⁰⁸	Partial (read only)	Yes²⁰⁹	No	with addon	?	Yes	?	Yes
ext4	No	Yes	Needs Paragon ExtFS ²¹⁰	No	Yes, with the optional WSL2; physical and VHDX virtual disks.²¹¹ ²¹²	?	Yes since FreeBSD 12.0²¹³	No	with addon	?	?	?	Yes
NOVA	No	Yes	No	No	No	No	No	No	No	No	No	No	No
Lustre	No	Yes²¹⁴	?	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²¹⁵ and dropped in 11.0²¹⁶ ²¹⁷	?	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²¹⁸	?	No	No	?	No	No	?	?	Yes	?	No
Be File System	No	Partial - read-only	?	No	No	?	No	No	Yes	?	?	?	No
NSS	No	Yes via EVMS²¹⁹	?	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²²⁰	Yes²²¹	No	No	No	Yes²²²	No	No	No	Yes²²³	?	No
ZFS	No	Yes with FUSE ²²⁴ or as an external kernel module²²⁵	Yes with Read/Write Developer Preview²²⁶	No	Yes²²⁷	No	Yes	No	No	No	Yes	No	No
Btrfs	No	Yes	?	No	Yes with WinBtrfs²²⁸	?	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	No	Yes	Yes	No	No	No	Yes	No	No	Yes	Yes	?	No
Joliet ("CDFS")	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.²²⁹ ²³⁰)	No	No	No	No	No	No
BlueStore/Cephfs	No	Yes	No²³¹	No	No²³²	No	No²³³	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 (1012, 10004) bytes), filesystem limits are invariably powers of 2, so usually expressed with IEC prefixes. For instance, a 1 TiB limit means 240, 10244 bytes. Approximations (rounding down) using power of 10 are also given below to clarify.

File system	Maximum filename length	Allowable characters in directory entries²³⁴	Maximum pathname length	Maximum file size	Maximum volume size²³⁵	Max number of files
AdvFS	255 characters	Any byte except NUL²³⁶	No limit defined²³⁷	16 TiB (17.59 TB)	16 TiB (17.59 TB)	?
APFS	255 UTF-8 characters	Unicode 9.0 encoded in UTF-8 ²³⁸	?	8 EiB (9.223 EB)	?	263 ²³⁹
Bcachefs	255 bytes	Any byte except '/' and NUL	No limit defined	16 EiB (18.44 EB)	16 EiB (18.44 EB)	264
BeeGFS	255 bytes	Any byte except NUL²⁴⁰	No limit defined²⁴¹	16 EiB (18.44 EB)	16 EiB (18.44 EB)	?
BFS	255 bytes	Any byte except NUL²⁴²	No limit defined²⁴³	12,288 bytes to 260 GiB (279.1 GB)²⁴⁴	256 PiB (288.2 PB) to 2 EiB (2.305 EB)	Unlimited
BlueStore/Cephfs	255 characters	any byte, except null, "/"	No limit defined	Max. 264 bytes, 1 TiB (1.099 TB) by default ²⁴⁵	Not limited	Not limited, default is 100,000 files per directory ²⁴⁶
Btrfs	255 bytes	Any byte except '/' and NUL	No limit defined	16 EiB (18.44 EB)	16 EiB (18.44 EB)	264
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	?
exFAT	255 UTF-16 characters	Unicode except for control codes 0x0000 - 0x001F or " * / : < > ? \ \| ²⁴⁷	32,760 characters with each path component no more than 255 characters²⁴⁸	16 EiB (18.44 EB)²⁴⁹	64 ZiB (75.55 ZB) (276 bytes)	?
ext	255 bytes	Any byte except NUL²⁵⁰	No limit defined²⁵¹	2 GiB (2.147 GB)	2 GiB (2.147 GB)	?
ext2	255 bytes	Any byte except NUL, /²⁵²	No limit defined²⁵³	16 GiB (17.17 GB) to 2 TiB (2.199 TB)²⁵⁴	2 TiB (2.199 TB) to 32 TiB (35.18 TB)	?
ext3	255 bytes	Any byte except NUL, /²⁵⁵	No limit defined²⁵⁶	16 GiB (17.17 GB) to 2 TiB (2.199 TB)²⁵⁷	2 TiB (2.199 TB) to 32 TiB (35.18 TB)	?
ext4	255 bytes²⁵⁸	Any byte except NUL, /²⁵⁹	No limit defined²⁶⁰	16 GiB (17.17 GB) to 16 TiB (17.59 TB)²⁶¹ ²⁶²	1 EiB (1.152 EB)	232 (static inode limit specified at creation)
F2FS	255 bytes	Any byte except NUL, /²⁶³	No limit defined²⁶⁴	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)²⁶⁵	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ²⁶⁶ ²⁶⁷	No limit defined²⁶⁸	32 MiB (33.55 MB) (4 GiB (4.294 GB))²⁶⁹	1 MiB (1.048 MB) to 32 MiB (33.55 MB)	?
FAT16B/FAT16X	8.3 (255 UCS-2 characters with LFN)²⁷⁰	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ²⁷¹ ²⁷² ²⁷³	No limit defined²⁷⁴	2 (4) GiB ²⁷⁵ (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)²⁷⁶	SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ \| ²⁷⁷ ²⁷⁸ ²⁷⁹	32,760 characters with each path component no more than 255 characters²⁸⁰	4 GiB (4.294 GB)²⁸¹	512 MiB (536.8 MB) to 16 TiB (17.59 TB)²⁸²	?
FATX	42 bytes²⁸³	ASCII.	No limit defined²⁸⁴	2 GiB (2.147 GB)	16 MiB (16.77 MB) to 2 GiB (2.147 GB)	?
FFS	255 bytes	Any byte except NUL²⁸⁵	No limit defined²⁸⁶	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 ! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > \| [ ] ( ) _²⁸⁷	?	?	?	?
GFS2	255 bytes	Any byte except NUL²⁸⁸	No limit defined²⁸⁹	100 TiB (109.95 TB) to 8 EiB (9.223 EB)²⁹⁰	100 TiB (109.95 TB) to 8 EiB (9.223 EB)²⁹¹	?
GFS	255 bytes	Any byte except NUL²⁹²	No limit defined²⁹³	2 TiB (2.199 TB) to 8 EiB (9.223 EB)²⁹⁴	2 TiB (2.199 TB) to 8 EiB (9.223 EB)²⁹⁵	?
GPFS	255 UTF-8 codepoints	Any byte except NUL²⁹⁶	No limit defined²⁹⁷	9 EiB (10.37 EB)	524,288 YiB (299 bytes)	?
HAMMER	1023 bytes²⁹⁸	Any byte except NUL²⁹⁹	?	?	1 EiB (1.152 EB)³⁰⁰	?
HFS	31 bytes	Any byte except :	Unlimited	2 GiB (2.147 GB)	2 TiB (2.199 TB)	?
HFS Plus	255 UTF-16 characters³⁰¹	Any valid Unicode ³⁰² ³⁰³	Unlimited	slightly less than 8 EiB (9.223 EB)	slightly less than 8 EiB (9.223 EB)³⁰⁴ ³⁰⁵	?
High Sierra Format	?	?	?	?	?	?
HPFS	255 bytes	Any byte except NUL³⁰⁶	No limit defined³⁰⁷	2 GiB (2.147 GB)	2 TiB (2.199 TB)³⁰⁸	?
IBM SFS	8.8	?	?	Non-hierarchical³⁰⁹	?	?
ISO 9660:1988	Level 1: 8.3,Level 2 & 3: ~ 180	Depends on Level³¹⁰	~ 180 bytes?	4 GiB (4.294 GB) (Level 1 & 2) to 8 TiB (8.796 TB) (Level 3)³¹¹	8 TiB (8.796 TB)³¹²	?
ISO 9660:1999	?	?	?	?	?	?
JFS	255 bytes	Any Unicode except NUL	No limit defined³¹³	4 PiB (4.503 PB)	32 PiB (36.02 PB)	?
JFS1	255 bytes	Any byte except NUL³¹⁴	No limit defined³¹⁵	8 EiB (9.223 EB)	512 TiB (562.9 TB) to 4 PiB (4.503 PB)	?
Joliet ("CDFS")	64 characters	All UCS-2 code except *, /, \, :, ;, and ?³¹⁶	?	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 (235); 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³¹⁷	No limit defined³¹⁸	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³¹⁹	No limit defined³²⁰	256.5 MiB (268.9 MB) ³²¹	64 MiB (67.10 MB)	?
Minix V2 FS	14 or 30 bytes, set at filesystem creation time	Any byte except NUL³²²	No limit defined³²³	2 GiB (2.147 GB) ³²⁴	1 GiB (1.073 GB)	?
Minix V3 FS	60 bytes	Any byte except NUL³²⁵	No limit defined³²⁶	2 GiB (2.147 GB)	4 GiB (4.294 GB)	?
NILFS	255 bytes	Any byte except NUL³²⁷	No limit defined³²⁸	8 EiB (9.223 EB)	8 EiB (9.223 EB)	?
NOVA	255 bytes	Any byte except NUL, /³²⁹	No limit defined³³⁰	16 EiB (18.44 EB)	16 EiB (18.44 EB)	?
NSS	256 characters	Depends on namespace used³³¹	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 ³³²	32,767 characters with each path component (directory or filename) up to 255 characters long³³³	16 TiB (17.59 TB) to 8 PiB (9.007 PB)³³⁴ ³³⁵	16 TiB (17.59 TB) to 8 PiB (9.007 PB)³³⁶ ³³⁷	232
NWFS	80 bytes³³⁸	Depends on namespace used³³⁹	No limit defined³⁴⁰	4 GiB (4.294 GB)	1 TiB (1.099 TB)	?
OCFS	255 bytes	Any byte except NUL³⁴¹	No limit defined³⁴²	8 TiB (8.796 TB)	8 TiB (8.796 TB)	?
OCFS2	255 bytes	Any byte except NUL³⁴³	No limit defined³⁴⁴	4 PiB (4.503 PB)	4 PiB (4.503 PB)	?
ODS-5	236 bytes³⁴⁵	?	4,096 bytes³⁴⁶	1 TiB (1.099 TB)	1 TiB (1.099 TB)	?
QFS	255 bytes	Any byte except NUL³⁴⁷	No limit defined³⁴⁸	16 EiB (18.44 EB)³⁴⁹	4 PiB (4.503 PB)³⁵⁰	?
ReFS	255 UTF-16 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 ³⁵² ³⁵³	32,767 characters with each path component (directory or filename) up to 255 characters long³⁵⁴	16 EiB (18.44 EB)³⁵⁵ ³⁵⁶	1 YiB (1.208 YB)³⁵⁷	?
ReiserFS	4,032 bytes/255 characters	Any byte except NUL or '/'³⁵⁸	No limit defined³⁵⁹	8 TiB (8.796 TB)³⁶⁰ (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³⁶¹	8 TiB (8.796 TB) on x86	?	?
Rock Ridge	255 bytes	Any byte except NUL or /³⁶²	No limit defined³⁶³	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³⁶⁴	16 EiB (18.44 EB)	512 MiB (536.8 MB) to 16 TiB (17.59 TB)	?
UFS1	255 bytes	Any byte except NUL³⁶⁵	No limit defined³⁶⁶	16 GiB (17.17 GB) to 256 TiB (281.4 TB)	16 EiB (18.44 EB)	Subdirectory per directory is 32,767³⁶⁷
UFS2	255 bytes	Any byte except NUL³⁶⁸	No limit defined³⁶⁹	512 GiB (549.7 GB) to 32 PiB (36.02 PB)	512 ZiB (604.4 ZB)³⁷⁰ (279 bytes)	Subdirectory per directory is 32,767³⁷¹
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 /³⁷²	No limit defined³⁷³	16 MiB (16.77 MB)³⁷⁴	32 MiB (33.55 MB)	?
Version 7 Unix file system (V7FS)	14 bytes	Any byte except NUL or /³⁷⁵	No limit defined³⁷⁶	1 GiB (1.073 GB)³⁷⁷	2 TiB (2.199 TB)	?
VMFS2	128	Any byte except NUL or /³⁷⁸	2,048	4 TiB (4.398 TB)³⁷⁹	64 TiB (70.36 TB)	?
VMFS3	128	Any byte except NUL or /³⁸⁰	2,048	2 TiB (2.199 TB)³⁸¹	64 TiB (70.36 TB)	?
VxFS	255 bytes	Any byte except NUL³⁸²	No limit defined³⁸³	16 EiB (18.44 EB)	?	?
XFS	255 bytes³⁸⁴	Any byte except NUL or /³⁸⁵	No limit defined³⁸⁶	8 EiB (9.223 EB)³⁸⁷	8 EiB (9.223 EB)³⁸⁸	264
Xiafs	248 bytes	Any byte except NUL³⁸⁹	No limit defined³⁹⁰	64 MiB (67.10 MB)	2 GiB (2.147 GB)	?
ZFS	1023 bytes	Any Unicode except NUL	No limit defined³⁹¹	16 EiB (18.44 EB)	281,474,976,710,656 YiB (2128 bytes)	2128
File system	Maximum filename length	Allowable characters in directory entries³⁹²	Maximum pathname length	Maximum file size	Maximum volume size³⁹³	Max number of files

Notes

External links

A speed comparison of filesystems on Linux 2.4.5 (archived)
Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch Archived 2018-03-04 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

References

Shustek, Len (2016-08-02). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum. http://www.computerhistory.org/atchm/in-his-own-words-gary-kildall/ ↩
Kildall, Gary Arlen (2016-08-02) [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 2016-11-17. /wiki/Gary_Kildall ↩
Mace, Scott (1986-09-22). "Extensions to MS-DOS Run CD-ROM". InfoWorld. 8 (38): 1, 8. Retrieved 2016-11-09. https://books.google.com/books?id=ZS8EAAAAMBAJ&pg=PA1 ↩
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. /wiki/IBM_AIX ↩
Warren, David (20 October 1993). "Polycenter File System - - HELP". Archived from the original on 9 March 2012. https://web.archive.org/web/20120309144054/http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html ↩
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. /wiki/Microsoft ↩
"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. https://web.archive.org/web/20071002091821/http://www.sun.com/aboutsun/pr/2007-09/sunflash.20070912.2.xml ↩
Matthew Dillon (2018-12-09). "hammer2/DESIGN". BSD Cross Reference. DragonFly BSD. Retrieved 2019-03-06. /wiki/Matthew_Dillon_(computer_scientist) ↩
"Huawei announces the EROFS Linux file system intended for Android devices". XDA Developer. June 1, 2018. https://www.xda-developers.com/huawei-erofs-linux-file-system-android/ ↩
Implemented in later versions as an extension ↩
"RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–26 .. 1–32. http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf ↩
"RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–4 .. 1–12. http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf ↩
"Format of the Unix 6 file system" (PDF). Archived from the original (PDF) on 2016-09-21. Retrieved 2016-02-21. https://web.archive.org/web/20160921012843/http://www.utdallas.edu/~venky/os/Proj/disk.pdf ↩
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 2016-02-21. http://web.cuzuco.com/~cuzuco/v7/v7vol1.pdf ↩
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. /wiki/Installable_File_System ↩
The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however. /wiki/OS/2 ↩
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. /wiki/Access_control_list ↩
As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.[12] /wiki/Mandatory_Integrity_Control ↩
Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS ↩
Access-control lists and MAC labels are layered on top of extended attributes. ↩
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). /wiki/UFS1_(file_system) ↩
Access-control lists and MAC labels are layered on top of extended attributes. ↩
Access-control lists and MAC labels are layered on top of extended attributes. ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
Metadata is mostly checksummed,[13] however Direct/indirect/triple-indirect block maps are not protected by checksums[14] ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
Creation time stored since June 2015, xfsprogs version 3.2.3 ↩
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. /wiki/Installable_File_System ↩
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. /wiki/UTC ↩
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. /wiki/UTC ↩
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. /wiki/UTC ↩
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. ↩
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. /wiki/Novell_Directory_Services ↩
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. /wiki/UTC ↩
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. /wiki/UTC ↩
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. /wiki/UTC ↩
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. ↩
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. /wiki/Novell_Directory_Services ↩
Record Management Services (RMS) attributes include record type and size, among many others. ↩
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. /wiki/Installable_File_System ↩
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. /wiki/9P_(protocol) ↩
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. /wiki/Libburnia ↩
libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists. /wiki/Libburnia ↩
libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists. /wiki/Libburnia ↩
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. /wiki/Unix ↩
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.[15] 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. ↩
NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling. ↩
NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling. ↩
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. /wiki/Services_for_Unix ↩
Siracusa, John (2011-07-20). "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. https://arstechnica.com/gadgets/2011/07/mac-os-x-10-7/12/#hfs-problems ↩
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.[17] 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.[18][19] ↩
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).[20] ↩
"Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling) /wiki/Soft_dependencies ↩
McKusick, Marshall Kirk; Roberson, Jeff. "Journaled Soft-updates" (PDF). https://www.mckusick.com/softdep/suj.pdf ↩
Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE [22][23] ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
Linux kernel versions 2.6.12 and newer. ↩
Off by default. ↩
Off by default. ↩
"EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2". https://www.phoronix.com/scan.php?page=news_item&px=EXT4-Case-Insensitive-Linux-5.2 ↩
"2. High Level Design — The Linux Kernel documentation § 2.10. Inline Data". www.kernel.org. Retrieved 2022-12-24. https://www.kernel.org/doc/html/latest/filesystems/ext4/overview.html#inline-data ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
Off by default. ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
Full block journaling for ReiserFS was added to Linux 2.6.8. ↩
Off by default. ↩
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. /wiki/Installable_File_System ↩
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. ↩
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. ↩
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.[26] ↩
Available only in the "NFS" namespace. ↩
Available only in the "NFS" namespace. ↩
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. ↩
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. ↩
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.[26] ↩
These are referred to as "aliases". ↩
These are referred to as "aliases". ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
"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. http://www.osta.org/specs/pdf/udf260.pdf ↩
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. ↩
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. ↩
"zpool-features.7 - OpenZFS documentation". openzfs.github.io. Retrieved 2024-09-23. https://openzfs.github.io/openzfs-docs/man/master/7/zpool-features.7.html#embedded_data ↩
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 ↩
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. /wiki/Services_for_Unix ↩
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. ↩
"clonefile(2)". The cloned file dst shares its data blocks with the src file [..] http://www.manpagez.com/man/2/clonefile/ ↩
only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[30] /wiki/Stacker_3 ↩
only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[30] /wiki/Stacker_3 ↩
Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client. ↩
"About Data Deduplication". 31 May 2018. https://msdn.microsoft.com/en-us/library/hh769303(v=vs.85).aspx ↩
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. /wiki/FileVault ↩
"Ext4 encryption". https://lwn.net/Articles/639427/ ↩
"Red Hat: What is bitrot?". https://www.redhat.com/en/blog/what-bit-rot-and-how-can-i-detect-it-rhel ↩
"F2FS encryption". https://lwn.net/Articles/677620/ ↩
UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal. /wiki/Log-structured_file_system ↩
Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1. ↩
"mkfs.xfs(8) from xfsprogs 5.10.0-4". By default, mkfs.xfs [..] will enable the reflink [=deduplication] feature. https://manpages.debian.org/bullseye/xfsprogs/mkfs.xfs.8.en.html ↩
"Red Hat: What is bitrot?". https://www.redhat.com/en/blog/what-bit-rot-and-how-can-i-detect-it-rhel ↩
"JFS data compression". IBM. Retrieved 2020-07-26. https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/devicemanagement/jfsdatacomp.html ↩
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.[37][38][39] /wiki/OpenZFS ↩
LZJB (optimized for performance while providing decent data compression)LZ4 (faster & higher ratio than lzjb)gzip levels: 1 (fastest) to 9 (best), default is 6zstd positive: 1 (fastest) to 19 (best), default is 3zstd negative: 1(best & default)-10, 20, 30, …, 100, 500, 1000(fastest)zle: compresses runs of zeros.[40] /wiki/LZJB ↩
disabling copy-on-write (COW) to prevent fragmentation also disables data checksumming ↩
zlib levels: 1 to 9, default is 3LZO (no levels) faster than ZLIB, worse ratiozstd levels: 1 to 15, default is 3 (higher levels are not available)[41] /wiki/Zlib ↩
noneCRC-32C (default)crc64chacha20/poly1305 (When encryption is enabled. Encryption can only be specified for the entire filesystem, not per file or directory)[42] /wiki/Cyclic_redundancy_check#Standards_and_common_use ↩
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.[43] /wiki/Gzip ↩
* 3.7: Added file-level snapshot (only available in Windows Server 2022).[44] /wiki/Windows_Server_2022 ↩
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.[45] ↩
* 3.9: Added post process compression with LZ4 and ZSTD and transparent decompression. /wiki/LZ4_(compression_algorithm) ↩
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.[45] ↩
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. ↩
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. ↩
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 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. ↩
With software based on GNU Parted. /wiki/GNU_Parted ↩
With software based on GNU Parted. /wiki/GNU_Parted ↩
With software based on GNU Parted. /wiki/GNU_Parted ↩
With software based on GNU Parted. /wiki/GNU_Parted ↩
"IBM's Journaled File System (JFS) for Linux". https://www.kernel.org/doc/Documentation/filesystems/jfs.txt ↩
"Growing an XFS File System". https://docs.oracle.com/cd/E37670_01/E37355/html/ol_grow_xfs.html ↩
"Shrinking Support - xfs.org". XFS Wiki. 2022-07-17. Archived from the original on 2022-07-17. Retrieved 2022-12-18. https://web.archive.org/web/20220717073119/http://xfs.org/index.php/Shrinking_Support ↩
"Shrinking Support - xfs.org". XFS Wiki. 2022-07-17. Archived from the original on 2022-07-17. Retrieved 2022-12-18. https://web.archive.org/web/20220717073119/http://xfs.org/index.php/Shrinking_Support ↩
"Frequently Asked Questions (Old Wiki)". Retrieved 5 May 2018. http://wiki.lustre.org/Frequently_Asked_Questions_(Old_Wiki) ↩
"Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem". https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/ ↩
"ntfsresize(8)". http://linux.die.net/man/8/ntfsresize ↩
resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands https://manned.org/resize2fs.8 ↩
resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands https://manned.org/resize2fs.8 ↩
"Resizing File Systems". https://www.suse.com/documentation/sles11/stor_admin/data/biuymaa.html ↩
"Resize reiserfs". Reiserfs wiki. https://reiser4.wiki.kernel.org/index.php/Resize_reiserfs ↩
resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands https://manned.org/resize2fs.8 ↩
"Just Enough Operating System (JeOS): Technical Information | SUSE". www.suse.com. Retrieved 28 April 2018. https://www.suse.com/products/server/technical-information/ ↩
Overstreet, Kent (18 Dec 2021). "bcachefs: Principles of Operation" (PDF). Retrieved 10 May 2023. https://bcachefs.org/bcachefs-principles-of-operation.pdf ↩
"nilfs-resize(8)". http://nilfs.sourceforge.net/en/man8/nilfs-resize.8.html ↩
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". https://openzfs.github.io/openzfs-docs/man/master/8/zpool-remove.8.html ↩
"Resizing and Growing Disks". https://www.freebsd.org/doc/handbook/disks-growing.html ↩
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.) The current implementation in UFS2 is read-only. /wiki/Extent_(file_systems) ↩
"Mac users, meet APFS: macOS's new file system - ZDNet". ZDNet. https://www.zdnet.com/article/wwdc-2017-macoss-new-file-system/ ↩
"Apple File System Guide - FAQ". https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html ↩
"CVF Region: MDFAT". http://www.techhelpmanual.com/808-cvf_region__mdfat.html ↩
"DMSDOS CVF module" (dmsdoc.doc). 0.9.2.0. 1998-11-19. Archived from the original on 2016-11-02. Retrieved 2016-11-01. 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. http://cmp.felk.cvut.cz/~pisa/dmsdos/dmsdos.html ↩
"Mapping DOS FAT to MDFAT". http://www.techhelpmanual.com/814-mapping_dos_fat_to_mdfat.html ↩
"CVF Region: MDFAT". http://www.techhelpmanual.com/808-cvf_region__mdfat.html ↩
"DMSDOS CVF module" (dmsdoc.doc). 0.9.2.0. 1998-11-19. Archived from the original on 2016-11-02. Retrieved 2016-11-01. 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. http://cmp.felk.cvut.cz/~pisa/dmsdos/dmsdos.html ↩
"Mapping DOS FAT to MDFAT". http://www.techhelpmanual.com/814-mapping_dos_fat_to_mdfat.html ↩
Only for "stuffed" inodes ↩
Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations. ↩
Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations. ↩
Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations. ↩
"[base] Revision 216796". https://svnweb.freebsd.org/base?view=revision&revision=216796 ↩
"Newfs(8)". https://www.freebsd.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+8.4-RELEASE ↩
Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations. ↩
Fragments were planned, but never actually implemented on ext2 and ext3. ↩
Fragments were planned, but never actually implemented on ext2 and ext3. ↩
Fragments were planned, but never actually implemented on ext2 and ext3. ↩
Stores one largest extent in disk, and caches multiple extents in DRAM dynamically. ↩
Jaeguk Kim (2014-09-22). "[PATCH 2/3] f2fs: Introduce FITRIM in f2fs_ioctl". linux-kernel (Mailing list). https://lkml.org/lkml/2014/09/23/32 ↩
Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte. ↩
Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte. ↩
In "extents" mode. ↩
"Reiser4 discard support". Reiser4 FS Wiki. https://reiser4.wiki.kernel.org/index.php/Reiser4_discard_support ↩
"XFS Adds Shared Data Extents For Linux 4.9". https://www.phoronix.com/scan.php?page=news_item&px=XFS-Linux-4.9-Shared-Extents ↩
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. ↩
Depends on UDF implementation. ↩
ISO 9660 Level 3 only ↩
ISO 9660 Level 3 only ↩
ISO 9660 Level 3 only ↩
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.) The current implementation in UFS2 is read-only. /wiki/Extent_(file_systems) ↩
Android Kernel File System Support (Documentation). Android Open Source Project. Retrieved 2023-01-11. https://source.android.com/docs/core/architecture/android-kernel-file-system-support ↩
"GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)". GitHub. 2020-01-18. https://github.com/sgan81/apfs-fuse ↩
"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. 2019-12-14. https://github.com/eafer/linux-apfs ↩
Namjae Jeon (20 January 2020). "[PATCH v12 00/13] add the latest exfat driver". linux-kernel (Mailing list). Retrieved 18 December 2021. https://lkml.org/lkml/2020/1/20/420 ↩
"NTFS3 Pull Request acceptance". https://lkml.iu.edu/hypermail/linux/kernel/2109.0/03731.html ↩
"Paragon HFS+ for Windows 10". http://www.paragon-software.com/home/hfs-windows/download.html ↩
"Paragon HFS+ for Windows 10". http://www.paragon-software.com/home/hfs-windows/download.html ↩
"Porting an Ancient Filesystem to Modern Linux". Time To Pull The Plug. Archived from the original on 2017-06-21. Retrieved 2016-04-22. https://web.archive.org/web/20170621190933/http://time.to.pullthepl.ug/blog/2013/6/24/porting-an-ancient-filesystem-to-modern-linux/ ↩
"A port of the xiafs filesystem to modern Linux kernels". Github (cdtk). 2019-06-28. https://github.com/ctdk/modern-xiafs ↩
"Paragon ExtFS for Mac". https://www.paragon-software.com/ufsdhome/extfs-mac ↩
"Explore2fs". chrysocome.net. http://www.chrysocome.net/explore2fs ↩
"Paragon ExtFS for Windows". https://www.paragon-software.com/home/extfs-windows ↩
"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.) http://www.fs-driver.org/faq.html ↩
Branten, Bo. "Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)". Archived from the original on 2012-07-23. Retrieved 2012-07-24. https://web.archive.org/web/20120723091043/http://www.ext2fsd.com/ ↩
"Paragon ExtFS for Mac". https://www.paragon-software.com/ufsdhome/extfs-mac ↩
"Explore2fs". chrysocome.net. http://www.chrysocome.net/explore2fs ↩
"Paragon ExtFS for Windows". https://www.paragon-software.com/home/extfs-windows ↩
"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.) http://www.fs-driver.org/faq.html ↩
Branten, Bo. "Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)". Archived from the original on 2012-07-23. Retrieved 2012-07-24. https://web.archive.org/web/20120723091043/http://www.ext2fsd.com/ ↩
"FreeBSD Handbook". https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-linux.html ↩
"Paragon ExtFS for Mac". https://www.paragon-software.com/ufsdhome/extfs-mac ↩
Hanselman, Scott (2021-11-02). "WSL2 can now mount Linux ext4 disks directly". Newsletter of Wonderful Things. Retrieved 2023-10-01. https://www.hanselman.com/blog/wsl2-can-now-mount-linux-ext4-disks-directly ↩
Microsoft Corp. (2023-07-17). "Windows technical documentation: Windows development environment: Windows Subsystem for Linux". Microsoft Learn (published 2021-12-09). Archived from the original on 2021-12-27. Retrieved 2023-10-01. https://learn.microsoft.com/windows/wsl/basic-commands#mount-a-disk-or-device ↩
"FreeBSD Handbook". https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-linux.html ↩
"Lustre Wiki". http://wiki.lustre.org/index.php?title=Main_Page ↩
"FreeBSD 10.4 MAN page - reiserfs". www.freebsd.org. Retrieved 2019-08-05. https://www.freebsd.org/cgi/man.cgi?query=reiserfs&apropos=0&sektion=0&manpath=FreeBSD+10.4-RELEASE&arch=default&format=html ↩
"FreeBSD 11 and Reiserfs". www.linuxquestions.org. 2016-12-19. Retrieved 2019-08-05. https://www.linuxquestions.org/questions/%2Absd-17/freebsd-11-and-reiserfs-4175595198/ ↩
"'svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC". marc.info. Retrieved 2019-08-05. https://marc.info/?l=freebsd-commits-all&m=146349940607224&w=2 ↩
"About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide". Retrieved 2016-03-14. https://docs.oracle.com/cd/E22586_01/html/E22570/gledk.html ↩
Supported using only EVMS; not currently supported using LVM ↩
Provided in Plan 9 from User Space /wiki/Plan_9_from_User_Space ↩
Provided in Plan 9 from User Space /wiki/Plan_9_from_User_Space ↩
Provided in Plan 9 from User Space /wiki/Plan_9_from_User_Space ↩
Provided in Plan 9 from User Space /wiki/Plan_9_from_User_Space ↩
"ZFS Filesystem for FUSE/Linux". Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013. https://web.archive.org/web/20130513101601/http://www.wizy.org/wiki/ZFS_on_FUSE ↩
"ZFS on Linux". Lawrence Livermore National Laboratory. http://zfsonlinux.org/ ↩
Kim, Arnold (4 October 2007). "Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard". Mac Rumors. http://www.macrumors.com/2007/10/04/apple-seeds-zfs-read-write-developer-preview-1-1-for-leopard/ ↩
"OpenZFS on Windows". https://openzfsonwindows.org/ ↩
"WinBtrfs". Github (maharmstone). 2020-11-22. https://github.com/maharmstone/btrfs ↩
"squashfs-tools". Freshports. http://www.freshports.org/sysutils/squashfs-tools/ ↩
"fusefs-squashfuse". Freshports. http://www.freshports.org/sysutils/fusefs-squashfuse/ ↩
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. ↩
FUSE based driver available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux. ↩
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. /wiki/Installable_File_System ↩
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)). /wiki/Kibibyte ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
"Frequently Asked Questions". https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html ↩
"Volume Format Comparison". https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/VolumeFormatComparison/VolumeFormatComparison.html ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Varies wildly according to block size and fragmentation of block allocation groups. ↩
"CephFS Maximum File Sizes and Performance". https://docs.ceph.com/en/mimic/cephfs/administration/ ↩
"CephFS Directory Fragmentation". https://docs.ceph.com/en/latest/cephfs/dirfrags/ ↩
"ExFAT: File Name Directory Entry". https://www.ntfs.com/exfat-filename-dentry.htm ↩
"File System Functionality Comparison". Microsoft Docs. Microsoft. 2021-01-07. Retrieved 2022-08-14. https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits ↩
"File System Functionality Comparison". Microsoft Docs. Microsoft. 2021-01-07. Retrieved 2022-08-14. https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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)). /wiki/Kibibyte ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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)). /wiki/Kibibyte ↩
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. https://web.archive.org/web/20210228121426/https://arvimal.blog/2016/07/21/max-file-name-length-in-an-ext4-file-system/ ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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)). /wiki/Kibibyte ↩
"Interviews/EricSandeen". Fedora Project Wiki. 9 June 2008. https://fedoraproject.org/wiki/Interviews/EricSandeen ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. /wiki/FAT12 ↩
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. /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size. /wiki/Gibibyte ↩
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. /wiki/FAT12 ↩
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. /wiki/Installable_File_System ↩
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. /wiki/FAT12 ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size. /wiki/Gibibyte ↩
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. /wiki/FAT12 ↩
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. /wiki/Installable_File_System ↩
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. /wiki/FAT12 ↩
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. ↩
"File System Functionality Comparison". Microsoft Docs. Microsoft. 2021-01-07. Retrieved 2022-08-14. https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits ↩
"File System Functionality Comparison". Microsoft Docs. Microsoft. 2021-01-07. Retrieved 2022-08-14. https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits ↩
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.[104] /wiki/Partition_(computing) ↩
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. /wiki/FAT12 ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
"GEMDOS Overview". http://cd.textfiles.com/ataricompendium/BOOK/HTML/CHAP2.HTM ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). [106] ↩
Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). [107] ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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). ↩
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). ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Matthew Dillon. "HAMMER2 Design Document". we can allow filenames up to 1023 bytes long http://apollo.backplane.com/DFlyMisc/hammer2.txt ↩
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. ↩
Matthew Dillon (June 21, 2008). "The HAMMER Filesystem" (PDF). http://www.dragonflybsd.org/hammer/hammer.pdf ↩
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. ↩
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. ↩
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. /wiki/Escape_sequence ↩
"Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits". support.apple.com. July 26, 2016. Archived from the original on 2019-04-08. https://web.archive.org/web/20190408213105/https://support.apple.com/en-us/HT201711 ↩
"Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits". support.apple.com. February 20, 2012. https://support.apple.com/kb/TA21924 ↩
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. /wiki/Installable_File_System ↩
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.[122][123] /wiki/Installable_File_System ↩
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). /wiki/Installable_File_System ↩
"SFS file system". www.ibm.com. 2015-06-03. Archived from the original on 2022-09-13. Retrieved 2022-09-13. https://www.ibm.com/docs/en/cobol-aix/5.1?topic=systems-sfs-file-system ↩
ISO 9660#Restrictions /wiki/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 /wiki/Gibibyte ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
"Joliet Specification". 22 May 1995. Archived from the original on 14 April 2009. https://web.archive.org/web/20090414104421/http://bmrc.berkeley.edu/people/chaffee/jolspec.html ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Sparse files can be larger than the file system size, even though they can't contain more data. ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Sparse files can be larger than the file system size, even though they can't contain more data. ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
NSS allows files to have multiple names, in separate namespaces. ↩
Russon, Richard; Fledel, Yuval. "NTFS Documentation" (PDF). http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf ↩
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.[122][123] /wiki/Installable_File_System ↩
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. /wiki/Windows_NT ↩
"NTFS overview". Microsoft Docs. 2022-05-26. Archived from the original on 2022-05-26. Retrieved 2022-06-05. https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview ↩
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. /wiki/Windows_NT ↩
"NTFS overview". Microsoft Docs. 2022-05-26. Archived from the original on 2022-05-26. Retrieved 2022-06-05. https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview ↩
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. /wiki/8.3_filename ↩
NSS allows files to have multiple names, in separate namespaces. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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. ↩
Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS". /wiki/Steven_Sinofsky ↩
Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS". /wiki/Steven_Sinofsky ↩
Amigo (2015-04-02). "Invalid Characters in File Names". Amigo's Technical Notes. Retrieved 2020-10-20. https://amigotechnotes.wordpress.com/2015/04/02/invalid-characters-in-file-names/ ↩
Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS". /wiki/Steven_Sinofsky ↩
Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS". /wiki/Steven_Sinofsky ↩
"Resilient File System (ReFS) overview". Microsoft Docs. Retrieved 2017-11-07. https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview ↩
Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS". /wiki/Steven_Sinofsky ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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"[119] /wiki/Exbibyte ↩
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.[122][123] /wiki/Installable_File_System ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
This restriction might be lifted in newer versions. ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
"Maximum Number of UFS Subdirectories". Oracle. Retrieved 2019-02-12. https://docs.oracle.com/cd/E19120-01/open.solaris/819-2723/fsfilesysappx-5/index.html ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
"Frequently Asked Questions for FreeBSD 9.X and 10.X". FreeBSD Documentation Project. Retrieved 2016-03-20. 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. https://www.freebsd.org/doc/faq/book.html ↩
"Maximum Number of UFS Subdirectories". Oracle. Retrieved 2019-02-12. https://docs.oracle.com/cd/E19120-01/open.solaris/819-2723/fsfilesysappx-5/index.html ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. /wiki/Megabyte ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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). /wiki/BSD ↩
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. ↩
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. ↩
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. ↩
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. ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
Note that the filename can be much longer XFS#Extended attributes /wiki/XFS#Extended_attributes ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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. /wiki/Tebibyte ↩
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. /wiki/Tebibyte ↩
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. ↩
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.[122][123] /wiki/Installable_File_System ↩
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.[122][123] /wiki/Installable_File_System ↩
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. /wiki/Installable_File_System ↩
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)). /wiki/Kibibyte ↩