Comparison of file systems

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

General informationEdit

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

LimitsEdit

File system Maximum filename length Allowable characters in directory entries[c] Maximum pathname length Maximum file size Maximum volume size[d] Max number of files
BeeGFS 255 bytes Any byte except NUL[e] No limit defined[f] 16 EiB 16 EiB ?
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 512 MiB ?
IBM SFS 8.8 ? ? Non-hierarchical[8] ? ?
DECtape 6.3 A–Z, 0–9 DTxN:FILNAM.EXT = 15 369,280 bytes (577 * 640) 369,920 bytes (578 * 640) ?
Elektronika BK tape format 16 bytes ? No directory hierarchy 64 KiB Not limited. Approx. 800KB (one side) for 90 min cassette ?
MicroDOS file system 14 bytes ? ? 16 MiB 32 MiB ?
Level-D 6.3 A–Z, 0–9 DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67 34,359,738,368 words (2**35-1); 206,158,430,208 SIXBIT bytes Approx 12 GB (64 * 178 MB) ?
RT-11 6.3 A–Z, 0–9, $ 0 (no directory hierarchy) 33,554,432 bytes (65536 * 512) 33,554,432 bytes ?
Version 6 Unix file system (V6FS) 14 bytes Any byte except NUL and /[e] No limit defined[f] 16 MiB[g] 32 MiB ?
Disk Operating System (GEC DOS) ? ? ? ? at least 131,072 bytes ? ?
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 ? ?
CBM DOS 16 bytes Any byte except NUL 0 (no directory hierarchy) 16 MiB 16 MiB ?
Version 7 Unix file system (V7FS) 14 bytes Any byte except NUL or /[e] No limit defined[f] 1 GiB[h] 2 TiB ?
exFAT 255 UTF-16 characters ? 32,760 Unicode characters with each path component no more than 255 characters[11] 16 EiB[11] 64 ZiB (276 bytes) ?
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)[i] SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [c][e] No limit defined[f] 32 MiB (4 GiB)[j] 1 MiB to 32 MiB ?
FAT16B/FAT16X 8.3 (255 UCS-2 characters with LFN)[i] SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [c][i][e] No limit defined[f] 2 (4) GiB[j] 16 MiB to 2 (4) GiB ?
FAT32/FAT32X 8.3 (255 UCS-2 characters with LFN)[i] SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [c][i][e] 32,760 Unicode characters with each path component no more than 255 characters[11] 4 GiB[11] 512 MiB to 16 TiB[k] ?
FATX 42 bytes[i] ASCII. Unicode not permitted. No limit defined[f] 2 GiB 16 MiB to 2 GiB ?
Fossil ? ? ? ? ? ?
GEMDOS 8.3 A-Z, a-z, 0-9 ! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > | [ ] ( ) _[13] ? ? ? ?
APFS 255 UTF-8 characters Unicode 9.0 encoded in UTF-8 [14] ? 8 EiB ? 263 [15]
F2FS 255 bytes Any byte except NUL, /[e] No limit defined[f] 3.94 TiB 16 TiB ?
MFS 255 bytes Any byte except : No path (flat filesystem) 256 MiB 256 MiB ?
HFS 31 bytes Any byte except : Unlimited 2 GiB 2 TiB ?
HPFS 255 bytes Any byte except NUL[l] No limit defined[f] 2 GiB 2 TiB[m] ?
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[16]

32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[f] 16 EiB[n] 16 EiB[n] 232
ReFS 255 UTF-16 characters[17] 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[17][18]

32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[17] 16 EiB[17][19] 1 YiB[17] ?
HFS Plus 255 UTF-16 characters[o] Any valid Unicode[e][p] Unlimited slightly less than 8 EiB slightly less than 8 EiB[20][21] ?
FFS 255 bytes Any byte except NUL[e] No limit defined[f] 4 GiB 256 TiB ?
HAMMER 255 bytes[22] Any byte except NUL[e] ? ? 1 EiB[23] ?
UFS1 255 bytes Any byte except NUL[e] No limit defined[f] 16 GiB to 256 TiB 16 EiB Subdirectory per directory is 32,767[24]
UFS2 255 bytes Any byte except NUL[e] No limit defined[f] 512 GiB to 32 PiB 512 ZiB[25] (279 bytes) Subdirectory per directory is 32,767[24]
ext 255 bytes Any byte except NUL[e] No limit defined[f] 2 GiB 2 GiB ?
Xiafs 248 bytes Any byte except NUL[e] No limit defined[f] 64 MiB 2 GiB ?
ext2 255 bytes Any byte except NUL, /[e] No limit defined[f] 16 GiB to 2 TiB[d] 2 TiB to 32 TiB ?
ext3 255 bytes Any byte except NUL, /[e] No limit defined[f] 16 GiB to 2 TiB[d] 2 TiB to 32 TiB ?
ext4 255 bytes[26] Any byte except NUL, /[e] No limit defined[f] 16 GiB to 16 TiB[d][27] 1 EiB 232
NOVA 255 bytes Any byte except NUL, /[e] No limit defined[f] 16 EiB 16 EiB ?
Lustre 255 bytes Any byte except NUL[e] No limit defined[f] 16 EiB on ZFS 16 EiB ?
GPFS 255 UTF-8 codepoints Any byte except NUL[e] No limit defined[f] No limit found 299 bytes (2 PiB tested) ?
GFS 255 bytes Any byte except NUL[e] No limit defined[f] 2 TiB to 8 EiB[q] 2 TiB to 8 EiB[q] ?
NILFS 255 bytes Any byte except NUL[e] No limit defined[f] 8 EiB 8 EiB ?
ReiserFS 4,032 bytes/255 characters Any byte except NUL or '/'[e] No limit defined[f] 8 TiB[r] (v3.6), 4 GiB (v3.5) 16 TiB ?
Reiser4 3,976 bytes Any byte except / and NUL No limit defined[f] 8 TiB on x86 ? ?
OCFS 255 bytes Any byte except NUL[e] No limit defined[f] 8 TiB 8 TiB ?
OCFS2 255 bytes Any byte except NUL[e] No limit defined[f] 4 PiB 4 PiB ?
XFS 255 bytes[s] Any byte except NUL[e] No limit defined[f] 8 EiB[t] 8 EiB[t] ?
JFS1 255 bytes Any byte except NUL[e] No limit defined[f] 8 EiB 512 TiB to 4 PiB ?
JFS 255 bytes Any Unicode except NUL No limit defined[f] 4 PiB 32 PiB ?
QFS 255 bytes Any byte except NUL[e] No limit defined[f] 16 EiB[u] 4 PiB[u] ?
BFS 255 bytes Any byte except NUL[e] No limit defined[f] 12,288 bytes to 260 GiB[v] 256 PiB to 2 EiB Unlimited
AdvFS 255 characters Any byte except NUL[e] No limit defined[f] 16 TiB 16 TiB ?
NSS 256 characters Depends on namespace used[w] Only limited by client 8 TiB 8 TiB ?
NWFS 80 bytes[x] Depends on namespace used[w] No limit defined[f] 4 GiB 1 TiB ?
ODS-5 236 bytes[y] ? 4,096 bytes[z] 1 TiB 1 TiB ?
VxFS 255 bytes Any byte except NUL[e] No limit defined[f] 16 EiB ? ?
UDF 255 bytes Any Unicode except NUL 1,023 bytes[aa] 16 EiB 512 MiB to 16 TiB ?
ZFS 255 bytes Any Unicode except NUL No limit defined[f] 16 EiB 256 ZiB (278 bytes) 2128
Btrfs 255 bytes Any byte except '/' and NUL No limit defined 16 EiB 16 EiB 264
Minix V1 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL[e] No limit defined[f] 256.5 MiB [ab] 64 MiB ?
Minix V2 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL[e] No limit defined[f] 2 GiB [ab] 1 GiB ?
Minix V3 FS 60 bytes Any byte except NUL[e] No limit defined[f] 2 GiB 4 GiB ?
VMFS2 128 Any byte except NUL or /[e] 2,048 4 TiB[ac] 64 TiB ?
VMFS3 128 Any byte except NUL or /[e] 2,048 2 TiB[ac] 64 TiB ?
ISO 9660:1988 Level 1: 8.3,
Level 2 & 3: ~ 180
Depends on Level[ad] ~ 180 bytes? 4 GiB (Level 1 & 2) to 8 TiB (Level 3)[ae] 8 TiB[af] ?
Joliet ("CDFS") 64 Unicode characters All UCS-2 code except *, /, \, :, ;, and ?[29] ? same as ISO 9660:1988 same as ISO 9660:1988 ?
Rock Ridge 255 bytes Any byte except NUL or /[e] No limit defined[f] same as ISO 9660:1988 same as ISO 9660:1988 ?
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
ISO 9660:1999 ? ? ? ? ? ?
High Sierra Format ? ? ? ? ? ?
SquashFS 256 bytes ? No limit defined 16 EiB 16 EiB ?
File system Maximum filename length Allowable characters in directory entries[c] Maximum pathname length Maximum file size Maximum volume size[d] Max number of files

MetadataEdit

File system Stores file owner POSIX file permissions Creation timestamps Last access/ read timestamps Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC
BeeGFS Yes Yes No Yes Yes No Yes ? Yes Yes
CP/M file system No No Yes[ag] No No No No No No No
DECtape[30] 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[31] No No Yes (date only) No No No No No No Yes
Version 6 Unix file system (V6FS)[32] Yes Yes No Yes No No No No No No
Version 7 Unix file system (V7FS)[33] 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[ah] No No No No[ai] No
HPFS Yes[aj] No Yes Yes No No No ? Yes No
NTFS Yes Yes[ak] Yes Yes Yes No Yes Yes[al] Yes Yes[am]
ReFS Yes Yes Yes Yes Yes No Yes ? Yes[an] Yes[ao]
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[ap] Yes[ap] No[aq] No
UFS2 Yes Yes Yes Yes Yes No Yes[ap] Yes[ap] 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[ar] Yes[ar] Yes No
ext3 Yes Yes No Yes Yes No Yes[ar] Yes[ar] Yes No
ext4 Yes Yes Yes Yes Yes No Yes[ar] Yes[ar] Yes Partial[as]
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[ar] Yes[ar] Yes No
GPFS Yes Yes Yes Yes Yes No Yes Yes Yes Yes
GFS Yes Yes No Yes Yes No Yes[ar] Yes[ar] Yes No
NILFS Yes Yes Yes No Yes No No No No Yes
ReiserFS Yes Yes No Yes Yes No Yes[ar] Yes[ar] 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 Partial[at] Yes Yes No Yes Yes[ar] Yes Partial[au]
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[av] Yes[av] Yes Yes[av] Yes ? Yes[aw][ax] No
NWFS Yes ? Yes[av] Yes[av] Yes Yes[av] Yes ? Yes[aw][ax] No
ODS-5 Yes Yes Yes ? ? Yes Yes ? Yes[ay] No
APFS Yes Yes Yes Yes Yes Yes Yes ? Yes Partial
VxFS Yes Yes Yes Yes Yes No Yes ? Yes[ar] No
UDF Yes Yes Yes Yes Yes Yes Yes No Yes No
Fossil Yes Yes[az] No Yes Yes No No No No No
ZFS Yes Yes Yes Yes Yes Yes Yes Yes[ba] Yes[bb] Yes
Btrfs Yes Yes Yes Yes Yes No Yes Yes Yes Yes[bc]
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[bd] Yes No No[be] No[bf] No[bf] 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
File system Stores file owner POSIX file permissions Creation timestamps Last access/read timestamps Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC

FeaturesEdit

File capabilitiesEdit

File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log XIP
DECtape No No No No No No No No
BeeGFS Yes 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 ? ? Partial Yes ? ?
Version 6 Unix file system (V6FS) Yes No No No Yes Yes No No
Version 7 Unix file system (V7FS) Yes No[bg] No No Yes Yes No No
exFAT No No No Partial (with TexFAT only) No Yes No No
FAT12 No No No Partial (with TFAT12 only) No Partial (with VFAT LFNs only) No No
FAT16 / FAT16B / FAT16X No No No Partial (with TFAT16 only) No Partial (with VFAT LFNs only) No No
FAT32 / FAT32X No No No? Partial (with TFAT32 only) No Partial (with VFAT LFNs only) No No
GFS Yes Yes[bh] Yes Yes[bi] Yes Yes No No
HPFS No No No No No Yes No No
NTFS Yes Yes[bj] No[bk] Yes[bk] (2000) Yes[bl] Yes Yes ?
HFS Plus Yes[38] Yes No Yes[bm] Partial[bn] Yes Yes[bo] No
FFS Yes Yes No No Yes Yes No No
UFS1 Yes Yes No No Yes Yes No No
UFS2 Yes Yes No Yes[bp] [43] [bq] Yes Yes No ?
HAMMER Yes Yes Yes Yes Yes Yes ? No
LFS Yes Yes Yes[br] 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[bs]
ext3 Yes Yes Yes (2001) [bt] Yes (2001) Yes Yes No Yes
ext4 Yes Yes Yes[bt] Yes Yes, optional [46] Yes No Yes
NOVA Yes Yes No Yes Yes Yes No Yes
F2FS Yes Yes Yes[br] No Yes Yes No No
Lustre Yes Yes Yes[bt] Yes Yes Yes Yes No
NILFS Yes Yes Yes[br] No Yes Yes No No
ReiserFS Yes Yes Yes[bu] 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[bv] Yes Yes ?
JFS Yes Yes Yes Yes (1990) Yes[bw] Yes No ?
QFS Yes Yes No Yes Yes Yes No No
BFS Yes Yes No Yes Yes Yes ? No
NSS Yes Yes ? Yes Yes[bx] Yes[bx] Yes[by] No
NWFS Yes[bz] Yes[bz] No No Yes[bx] Yes[bx] Yes[by] No
ODS-2 Yes Yes[ca] No Yes No No Yes No
ODS-5 Yes Yes[ca] No Yes No Yes Yes ?
UDF Yes Yes Yes[br] Yes[br] Yes Yes No Yes
VxFS Yes Yes Yes No Yes Yes Yes ?
Fossil No No No No Yes Yes Yes No
ZFS Yes Yes Yes[cb] No[cb] Yes Yes No No
Btrfs Yes Yes Yes Yes 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 No Yes ? ? Yes[bl] 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
File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log XIP

Block capabilitiesEdit

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 Checksum Persistent Cache Multiple Devices compression
DECtape No No No No No No No
BeeGFS No No Yes No No No Yes
Level-D No No No No No No No
RT-11 No No No No No No No
APFS Yes Yes No No No No Yes
Version 6 Unix file system (V6FS) No No No No No No No
Version 7 Unix file system (V7FS) No No No No No No No
exFAT No No No No No No No
FAT12 No No No No No No Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[48])
FAT16 / FAT16B / FAT16X No No No No No No Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[48])
FAT32 / FAT32X No No No No No No No
GFS No No ? No No No No
HPFS ? No ? No No No No
NTFS No Yes Yes[cc][49] No No No Yes
HFS Plus No No[cd] No No No No No
FFS No No No No No No No
UFS1 No No No No No No No
UFS2 Yes No No No No No No
HAMMER Yes No Yes Yes No No No
LFS Yes No No No No No No
ext No No No No No No No
Xiafs No No No No No No No
ext2 No No No No No No No
ext3 No No No No No No No
ext4 No Yes, experimental [50] No No No No No
NOVA Yes No No Yes No No No
F2FS No Yes, experimental [51] No No No No Yes
Lustre No No No No Yes Yes No
NILFS Yes, continuous[br] No No Yes No No No
ReiserFS No No No No No No No
Reiser4 ? Yes[ce] ? No No No Yes
OCFS No No No No No No No
OCFS2 No No No No No No No
XFS No No Yes, experimental [52] No No No No
JFS ? No ? No No No only in JFS1 on AIX[53]
QFS No No No No No No No
BFS No No No No No No No
NSS Yes Yes ? No No No Yes
NWFS ? No ? No No No Yes
ODS-2 Yes No No No No No No
ODS-5 Yes No No No No No
UDF No No No No No No No
VxFS Yes[cf] No Yes No No No No
Fossil Yes No Yes No No No Yes
ZFS Yes Yes[cg] Yes Yes Yes Yes Yes
Btrfs Yes No Yes Yes No Yes Yes
Minix V1 No No No No No No No
Minix V2 No No No No No No No
Minix V3 No No No No No No No
VMFS2 No No No No No No No
VMFS3 No No No No No No No
ReFS ? No Yes Yes No No No
ISO 9660 No No No[ch] No No No No
Rock Ridge No No No[ch] No No No No
Joliet ("CDFS") No No No[ch] No No No No
SquashFS No No Yes Yes No No Yes
File system Internal snapshotting / branching Filesystem-level encryption Data deduplication Data checksums Persistent Cache Multiple Devices compression

Resize capabilitiesEdit

File system Host OS Offline grow Online grow Offline shrink Online shrink add and remove physical volumes
FAT16 / FAT16B / FAT16X misc. Yes[57] No Yes[57] No No
FAT32 / FAT32X misc. Yes[57] No Yes[57] No No
exFAT misc. No No No No No
NTFS Windows Yes Yes Yes Yes No
ReFS Windows ? Yes ? No No
HFS+ macOS No Yes No Yes No
APFS macOS ? ? ? ? ?
HFS+ Linux No No No No No
SquashFS Linux No No No No No
NOVA Linux No No No No No
JFS[58] Linux Yes No No No No
XFS[59] Linux No Yes No No No
Lustre[60] Linux ? Yes No No Yes
F2FS[61] Linux Yes No No No No
NTFS[62] Linux Yes No Yes No No
ext2[63] Linux Yes No Yes No No
ext3[63] Linux Yes Yes Yes No No
ReiserFS[64] Linux Yes Yes Yes No No
Reiser4[65] Linux Yes Yes Yes No No
ext4[63] Linux Yes Yes Yes No No
Btrfs[66] Linux Yes Yes Yes Yes Yes
NILFS[67] Linux No Yes No Yes No
ZFS misc. No Yes No Partial[68] Yes
JFS2 AIX ? Yes ? Yes No
UFS2[69] FreeBSD Yes Yes (FreeBSD 10.0-RELEASE or later) No No No
HAMMER DragonflyBSD ? ? ? ? ?

Allocation and layout policiesEdit

File system Sparse files Block suballocation Tail packing Extents Variable file block size[ci] 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[70][71]
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
FAT12 Partial (only inside of compressed volumes)[72] Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[48]) No Partial (only inside of compressed volumes)[73] No No No Yes (Linux)
FAT16 / FAT16B / FAT16X Partial (only inside of compressed volumes)[72] Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[48]) No Partial (only inside of compressed volumes)[73] No No No Yes (Linux)
FAT32 / FAT32X No No No No No No No Yes (Linux)
GFS Yes No Partial[cj] No No No ? Yes
HPFS No No No Yes No No ? No
NTFS Yes Partial No Yes No No ? Yes (NT 6.1 + newer)
HFS Plus No No No Yes No No ? Yes (macOS)
FFS Yes 8:1[ck] No No No No ? No
UFS1 Yes 8:1[ck] No No No No ? No
UFS2 Yes 8:1[ck] No No Yes No ? Yes[74][75]
LFS Yes 8:1[ck] No No No No Yes ?
ext Yes No No No No No No No
Xiafs Yes No No No No No ? ?
ext2 Yes No[cl] No No No No No Yes
ext3 Yes No[cl] No No No No No Yes
ext4 Yes No[cl] No Yes No Yes No Yes
NOVA Yes No No Yes No No Yes ?
F2FS Yes No No Partial[cm] No Yes Yes Yes[76]
Lustre Yes No No Yes No Yes ? ?
NILFS Yes No No No No Yes Yes ?
ReiserFS Yes Yes[cn] Yes No No No ? ?
Reiser4 Yes Yes[cn] Yes Yes[co] No Yes ? ?
OCFS ? No No Yes No No ? ?
OCFS2 Yes No No Yes No No ? ?
XFS Yes No No Yes No Yes Yes, on request[77] 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[cp] No No No No ? ?
ODS-5 ? No No Yes No No ? ?
VxFS Yes ? No Yes No No ? ?
UDF Yes No No Yes No ?[cq] Yes, for write once read many media No
Fossil ? No No No No No ? ?
ZFS Yes Yes No No Yes Yes Yes Yes (FreeBSD, illumos)
Btrfs Yes Yes Yes Yes Yes Yes Yes Yes
VMFS2 Yes Yes No No No No ? ?
VMFS3 Yes Yes No No No No ? ?
ReFS Yes ? ? ? No ? Yes ?
ISO 9660 No No No Yes[cr] No No No No
Rock Ridge No No No Yes[cr] No No No No
Joliet ("CDFS") No No No Yes[cr] No No No No
SquashFS Yes No Yes No No No No No
File system Sparse files Block suballocation Tail packing Extents Variable file block size[ci] Allocate-on-flush Copy on write Trim support

OS supportEdit

File system DOS Windows 9x Windows NT Linux "classic" Mac OS macOS FreeBSD OS/2 BeOS Minix Solaris z/OS
APFS No No No Partial (read-only with apfs-fuse[78] or linux-apfs[79]) No Yes
(Since macOS Sierra)
No No No No No No
BeeGFS No No No Yes No ? No No ? ? ? No
DECtape No No No No No No No No No No No No
Level-D No No No ? No ? No No No No ? ?
RT-11 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
Version 7 Unix file system (V7FS) No No No Yes No ? No No ? ? ? ?
exFAT No No Yes (installable drivers for Windows XP, 2003. Included with Windows Vista SP1 and newer.) Yes (available as a kernel module or FUSE driver) No Yes Yes (available as a FUSE driver) No No No Yes (available as a FUSE driver) No
FAT12 Yes Yes Yes Yes Yes Yes Yes Yes Yes Partial (via dosdir, dosread, doswrite) 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 ?
FAT32 / FAT32X Yes (from DOS 7.10) Yes (from Windows 95 OSR2) Yes (from Windows 2000) Yes Yes? Yes Yes Yes Yes No Yes ?
GFS No No No Yes No ? No ? ? ? ? ?
HPFS Partial (with third-party drivers) No Partial (with NT 3.1 to 4.0 only) Yes ? ? Yes Yes (from OS/2 1.2) ? No ? ?
NTFS Partial (with third-party drivers) Yes (with 3rd-party drivers like Paragon NTFS for Win98, DiskInternals NTFS Reader) Yes Yes with the Paragon NTFS kernel driver or ntfs-3g No Yes natively read only, write support with Paragon NTFS or ntfs-3g Yes with ntfs-3g ? Yes with ntfs-3g No Yes with ntfs-3g ?
Apple HFS No No Yes with Paragon HFS+ [80] Yes Yes No write support since Mac OS X 10.6 and no support at all since macOS 10.15 No ? Yes No ? No
Apple HFS Plus No No Yes with Paragon HFS+ [80] Partial - writing support only to unjournalled FS Yes from Mac OS 8.1 Yes No ? with addon No ? No
FFS No No ? ? ? Yes Yes ? ? ? ? ?
UFS1 No No Partial (with ufs2tools, read only) Partial - read only ? Yes Yes No ? ? Yes ?
UFS2 No No Partial (with ufs2tools, read only) Yes ? Yes Yes No ? ? ? ?
LFS No No No ? ? ? No No ? ? ? ?
ext No No No Yes - until 2.1.20 No No No No No No No No
Xiafs No No No Yes - until 2.1.20

Experimental port available to 2.6.32 and later [81][82]

No No No No No No No No
ext2 No No Yes with Paragon ExtFS [83] or partial with Ext2 IFS[84] or ext2fsd[85] Yes No Yes with Paragon ExtFS [86] or ext2fsx Yes No Yes ? ? ?
ext3 No No Yes with Paragon ExtFS [83] or partial with Ext2 IFS[84] or ext2fsd[85] Yes Partial (read only)[citation needed] Yes with Paragon ExtFS [86] or partial with ext2fsx (journal not updated on writing) Yes[87] No with addon ? Yes ?
ext4 No No Yes with Paragon ExtFS [83] or partial with Ext2 IFS[84] or ext2fsd[85] Yes ? Yes with Paragon ExtFS [86] Yes since FreeBSD 12.0[87] No with addon ? ? ?
NOVA No No No Yes No No No No No No No No
Lustre No No No Yes[88] ? ? No ? ? ? Yes ?
NILFS No No ? Yes as an external kernel module ? ? No ? ? ? ? ?
F2FS No No No Yes No No No No No No No No
ReiserFS No No No Yes ? ? Partial - Read Only from 6.0 to 10.x[89] and dropped in 11.0[90][91] ? with addon ? ? ?
Reiser4 No No No Yes with a kernel patch ? ? No ? ? ? ? ?
SpadFS No No No Yes No No ? No No No No No
OCFS No No No Yes ? ? No No ? ? ? ?
OCFS2 No No No Yes ? ? No No ? ? ? ?
XFS No No No Yes ? ? Partial ? with addon (read only) ? ? ?
JFS No No No Yes ? ? No Yes ? ? ? ?
QFS No No No Partial - client only[92] ? ? No No ? ? Yes ?
Be File System No No No Partial - read-only ? ? No No Yes ? ? ?
NSS No No No Yes via EVMS[cs] ? ? No No ? ? ? ?
NWFS Partial (with Novell drivers) No No ? ? ? Yes No ? ? ? ?
ODS-2 No No No ? ? ? No No ? ? ? ?
ODS-5 No No No ? ? ? No No ? ? ? ?
UDF No ? Yes Yes ? Yes Yes ? ? ? Yes ?
VxFS No No No Yes ? ? No No ? ? Yes ?
Fossil No No No Yes[ct] No Yes[ct] Yes[ct] No No No Yes[ct] ?
ZFS No No Yes[93] Yes with FUSE[94] or as an external kernel module[95] No Yes with Read/Write Developer Preview[96] Yes No No No Yes No
Btrfs No No Partial with WinBtrfs[97] Yes ? ? ? ? ? ? ? ?
VMFS2 No No No ? ? ? No No ? ? ? ?
VMFS3 No No No ? ? ? No No ? ? ? ?
IBM HFS No No No No No No No No No No No Yes
IBM zFS No No No No No No No No No No No Yes
ReFS No No Yes (from Windows Server 2012 and from Windows 8.1) Partial - with Paragon ReFS for Linux ? ? ? ? ? ? ? ?
ISO 9660 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Rock Ridge No No No Yes No Yes Yes No No Yes Yes ?
Joliet ("CDFS") No Yes Yes Yes ? Yes Yes Yes Yes ? Yes ?
SquashFS No No Partial (There are ports of unsquashfs and mksquashfs.) Yes No Partial (There are ports of unsquashfs and mksquashfs.) Partial (There are ports of unsquashfs and mksquashfs and fusefs-port.[98][99]) No No No No No
File system DOS Windows 9x Windows NT Linux "classic" Mac OS macOS FreeBSD OS/2 BeOS Minix Solaris z/OS

See alsoEdit

NotesEdit

  1. ^ 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.
  2. ^ 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.
  3. ^ a b c d e These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; operating systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
  4. ^ a b c d e For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 KiB 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).
  5. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak 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.
  6. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am 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. [9][10]
  7. ^ 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 MiB.
  8. ^ 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.
  9. ^ a b c d e f Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit OEM characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also must not contain lowercase letters. A few special device names (CON, NUL, AUX, PRN, LPT1, COM1, etc.) should be avoided, as some operating systems (notably DOS, OS/2 and Windows) reserve them.
  10. ^ a b On-disk structures would support up to 4 GiB, but practical file size is limited by volume size.
  11. ^ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB. 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.[12]
  12. ^ 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.
  13. ^ This is the limit of the on-disk structures. The HPFS Installable File System driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64 GiB.
  14. ^ a b This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TiB and the file size to 16 TiB respectively; in Windows 10 version 1709, the limit is 8 PiB when using 2 MiB cluster size.
  15. ^ 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.
  16. ^ 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.
  17. ^ a b Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB. For 32-bit 2.6 kernels it is 16 TiB. For 64-bit 2.6 kernels it is 8 EiB.
  18. ^ ReiserFS has a theoretical maximum file size of 1 EiB, but "page cache limits this to 8 Ti on architectures with 32 bit int"[28]
  19. ^ Note that the filename can be much longer XFS#Extended attributes
  20. ^ a b XFS has a limitation under Linux 2.4 of 64 TiB file size, but Linux 2.4 only supports a maximum block size of 2 TiB. This limitation is not present under IRIX.
  21. ^ a b QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.
  22. ^ Varies wildly according to block size and fragmentation of block allocation groups.
  23. ^ a b NSS allows files to have multiple names, in separate namespaces.
  24. ^ 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.
  25. ^ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  26. ^ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  27. ^ This restriction might be lifted in newer versions.
  28. ^ a b Sparse files can be larger than the file system size, even though they can't contain more data.
  29. ^ a b Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.
  30. ^ ISO 9660#Restrictions
  31. ^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB in size. See ISO 9660#The 2 GiB (or 4 GiB depending on implementation) file size limit
  32. ^ 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.
  33. ^ Implemented in later versions as an extension
  34. ^ 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.
  35. ^ 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.
  36. ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  37. ^ 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.
  38. ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.[34]
  39. ^ Windows can run the checksum to even restore data or fix a corrupt file on hdd and also repair any bad sectors if any. Windows Error Checking tool can do most of these tasks as on from Windows 7 onwards.[35]
  40. ^ Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS
  41. ^ Data checksums not enabled by default
  42. ^ a b c d Access-control lists and MAC labels are layered on top of extended attributes.
  43. ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  44. ^ a b c d e f g h i j k l m n 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.
  45. ^ Journal and metadata only[36]
  46. ^ Creation time stored since June 2015, xfsprogs version 3.2.3
  47. ^ Metadata checksums stored since June 2015, xfsprogs version 3.2.3
  48. ^ a b c d e f The local time, time zone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
  49. ^ a b Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.
  50. ^ a b Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.
  51. ^ Record Management Services (RMS) attributes include record type and size, among many others.
  52. ^ 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.
  53. ^ Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.
  54. ^ Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.
  55. ^ disabling copy-on-write (COW) to prevent fragmentation also disables checksumming
  56. ^ Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.
  57. ^ libburnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.
  58. ^ a b libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.
  59. ^ 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.
  60. ^ 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
  61. ^ Optional journaling of data
  62. ^ As of Windows Vista, NTFS fully supports symbolic links.[37] 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.
  63. ^ a b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  64. ^ a b While NTFS itself supports case sensitivity, the Win32 environment subsystem cannot create files whose names differ only by case for compatibility reasons. When a file is opened for writing, if there is any existing file whose name is a case-insensitive match for the new file, the existing file is truncated and opened for writing instead of a new file with a different name being created. Other subsystems like e. g. Services for Unix, that operate directly above the kernel and not on top of Win32 can have case-sensitivity.
  65. ^ 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.
  66. ^ 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.[39] 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.[40][41]
  67. ^ 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).[42]
  68. ^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling)
  69. ^ Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE [44][45]
  70. ^ a b c d e f UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  71. ^ Linux kernel versions 2.6.12 and newer.
  72. ^ a b c Off by default.
  73. ^ Full block journaling for ReiserFS was added to Linux 2.6.8.
  74. ^ Optionally no on IRIX and Linux.
  75. ^ 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.
  76. ^ a b c d Case-sensitivity/Preservation depends on client. Windows, DOS, and OS/2 clients don't see/keep case differences, whereas clients accessing via NFS or AFP may.
  77. ^ a b The file change logs, last entry change timestamps, and other filesystem metadata, are all part of the extensive suite of auditing capabilities built into NDS/eDirectory called NSure Audit.[47]
  78. ^ a b Available only in the "NFS" namespace.
  79. ^ a b These are referred to as "aliases".
  80. ^ a b ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.
  81. ^ Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.
  82. ^ 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.
  83. ^ Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  84. ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  85. ^ Applies to proprietary ZFS release 30 and ZFS On Linux. Encryption support is not yet available in all OpenZFS ports.[54][55][56]
  86. ^ a b c Some file system creation implementations reuse block references and support deduplication this way. This is not supported by the standard, but usually works well due to the file system's read-only nature.
  87. ^ a b Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.
  88. ^ Only for "stuffed" inodes
  89. ^ a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  90. ^ a b c Fragments were planned, but never actually implemented on ext2 and ext3.
  91. ^ Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.
  92. ^ a b Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.
  93. ^ In "extents" mode.
  94. ^ 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.
  95. ^ Depends on UDF implementation.
  96. ^ a b c ISO 9660 Level 3 only
  97. ^ Supported using only EVMS; not currently supported using LVM
  98. ^ a b c d Provided in Plan 9 from User Space

ReferencesEdit

  1. ^ Shustek, Len (2016-08-02). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.
  2. ^ 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. Cite journal requires |journal= (help)
  3. ^ Mace, Scott (1986-09-22). "Extensions to MS-DOS Run CD-ROM". InfoWorld. 8 (38): 1, 8. Retrieved 2016-11-09.
  4. ^ Warren, David (20 October 1993). "Polycenter File System - - HELP". Archived from the original on 9 March 2012.
  5. ^ "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.
  6. ^ Matthew Dillon (2018-12-09). "hammer2/DESIGN". BSD Cross Reference. DragonFly BSD. Retrieved 2019-03-06.
  7. ^ "Huawei announces the EROFS Linux file system intended for Android devices". XDA Developer. June 1, 2018.
  8. ^ "SFS file system". IBM Knowledge Center.
  9. ^ "PATH_MAX Is Tricky". Evan Klitzke’s web log.
  10. ^ "PATH_MAX simply isn't". Insane Coding. 2007-11-03.
  11. ^ a b c d "File System Functionality Comparison". Microsoft Developer Network. Microsoft. Retrieved 4 November 2017.
  12. ^ "Limitations of the FAT32 File System in Windows XP". Microsoft.
  13. ^ "GEMDOS Overview".
  14. ^ "Frequently Asked Questions".
  15. ^ "Volume Format Comparison".
  16. ^ http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf
  17. ^ a b c d e Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS".
  18. ^ Amigo (2015-04-02). "Invalid Characters in File Names". Amigo's Technical Notes. Retrieved 2020-10-20.
  19. ^ "Resilient File System (ReFS) overview". docs.microsoft.com. Retrieved 2017-11-07.
  20. ^ "Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits". support.apple.com. July 26, 2016.
  21. ^ "Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits". support.apple.com. February 20, 2012.
  22. ^ Matthew Dillon. "HAMMER2 Design Document".
  23. ^ Matthew Dillon (June 21, 2008). "The HAMMER Filesystem" (PDF).
  24. ^ a b "Maximum Number of UFS Subdirectories". Oracle. Retrieved 2019-02-12.
  25. ^ "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 KB => 16 Exa * 32 KB => 512 ZettaBytes.
  26. ^ Vimal A.R (16 July 2016). "Max file-name length in an EXT4 file system". arvimal.blog.
  27. ^ "Interviews/EricSandeen". Fedora Project Wiki. 9 June 2008.
  28. ^ "FAQ". namesys. 15 October 2003. Archived from the original on 19 July 2006.
  29. ^ "Joliet Specification". 22 May 1995. Archived from the original on 14 April 2009.
  30. ^ "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. p. 1–26 .. 1–32.
  31. ^ "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. p. 1–4 .. 1–12.
  32. ^ "Format of the Unix 6 file system" (PDF). Retrieved 2016-02-21.
  33. ^ 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.
  34. ^ "Mandatory Integrity Control". Microsoft Developer Network.
  35. ^ "NTFS Error Check Tool". Diskpart Hardrive Help.
  36. ^ "Ext4 Metadata Checksums - Ext4". ext4.wiki.kernel.org.
  37. ^ Mark Russinovich (February 2007). "Windows Administration: Inside the Windows Vista Kernel: Part 1". TechNet.
  38. ^ 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.
  39. ^ newfs_hfs(8) – Darwin and macOS System Manager's Manual
  40. ^ "File System Comparisons". Apple. (hasn't been updated to discuss HFSX)
  41. ^ "Technical Note TN1150: HFS Plus Volume Format". Apple. (Very technical overview of HFS Plus and HFSX.)
  42. ^ "fslogger". Archived from the original on 2008-09-18. Retrieved 2006-08-03.
  43. ^ https://www.mckusick.com/softdep/suj.pdf
  44. ^ "NewFAQs - FreeBSD Wiki".
  45. ^ "FreeBSD 9.0-RELEASE Announcement".
  46. ^ "EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2".
  47. ^ Filesystem Events tracked by NSure
  48. ^ a b c d "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.
  49. ^ "About Data Deduplication".
  50. ^ "Ext4 encryption".
  51. ^ "F2FS encryption".
  52. ^ "XFS, Reflinks and Deduplication".
  53. ^ "JFS data compression". IBM. Retrieved 2020-07-26.
  54. ^ "How to Manage ZFS Data Encryption".
  55. ^ "Release zfs-0.8.0". 2020-01-21.
  56. ^ "Feature Flags - OpenZFS".
  57. ^ a b c d With software based on GNU Parted
  58. ^ "IBM's Journaled File System (JFS) for Linux".
  59. ^ "Growing an XFS File System".
  60. ^ "Frequently Asked Questions (Old Wiki)". Retrieved 5 May 2018.
  61. ^ "Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem".
  62. ^ "ntfsresize(8)".
  63. ^ a b c resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands
  64. ^ "Resizing File Systems".
  65. ^ "Resize reiserfs". Reiserfs wiki.
  66. ^ "Just Enough Operating System (JeOS): Technical Information | SUSE". www.suse.com. Retrieved 28 April 2018.
  67. ^ "nilfs-resize(8)".
  68. ^ Mirror and single-disk vdevs can be wholly removed from a pool, but not RAID-Z vdevs. "OpenZFS 7614 - zfs device evacuation/removal".
  69. ^ "Resizing and Growing Disks".
  70. ^ "Mac users, meet APFS: macOS's new file system - ZDNet".
  71. ^ "Apple File System Guide - FAQ".
  72. ^ a b "CVF Region: MDFAT".
  73. ^ a b "Mapping DOS FAT to MDFAT".
  74. ^ "[base] Revision 216796".
  75. ^ "Newfs(8)".
  76. ^ Jaeguk Kim (2014-09-22). "F2FS: Introduce FITRIM in f2fs_ioctl".
  77. ^ "XFS Adds Shared Data Extents For Linux 4.9".
  78. ^ "GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)". 2020-01-18.
  79. ^ "APFS module for linux, with experimental write support. This tree is just for development, please use linux-apfs-oot instead.: Linux-apfs/Linux-apfs". 2019-12-14.
  80. ^ a b "Paragon HFS+ for Windows 10".
  81. ^ "Porting an Ancient Filesystem to Modern Linux". Time To Pull The Plug. Archived from the original on 2017-06-21. Retrieved 2016-04-22.
  82. ^ "A port of the xiafs filesystem to modern Linux kernels". Github (cdtk). 2019-06-28.
  83. ^ a b c "Paragon ExtFS for Windows".
  84. ^ a b c "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.)
  85. ^ a b c 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.
  86. ^ a b c "Paragon ExtFS for Mac".
  87. ^ a b "FreeBSD Handbook".
  88. ^ "Lustre Wiki".
  89. ^ "FreeBSD 10.4 MAN page - reiserfs". www.freebsd.org. Retrieved 2019-08-05.
  90. ^ "FreeBSD 11 and Reiserfs". www.linuxquestions.org. 2016-12-19. Retrieved 2019-08-05.
  91. ^ "'svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC". marc.info. Retrieved 2019-08-05.
  92. ^ "About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide". Retrieved 2016-03-14.
  93. ^ "OpenZFS on Windows".
  94. ^ "ZFS Filesystem for FUSE/Linux". Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013.
  95. ^ "ZFS on Linux". Lawrence Livermore National Laboratory.
  96. ^ Kim, Arnold (4 October 2007). "Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard". Mac Rumors.
  97. ^ "WinBtrfs". Github (maharmstone). 2020-01-19.
  98. ^ "squashfs-tools". Freshports.
  99. ^ "fusefs-squashfuse". Freshports.

External linksEdit