Jump to content

Comparison of file systems

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by AnthonySorace (talk | contribs) at 04:00, 25 November 2013 (Fix omission of Plan 9 from platform support footer.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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

General information

File system Creator Year
introduced 		Original operating system
DECtape DEC 1964 PDP-6 Monitor
Level-D DEC 1968 TOPS-10
George 2 ICT (later ICL) 1968 George 2
ODS-1 DEC 1972 RSX-11
RT-11 file system DEC 1973 RT-11
DOS (GEC) GEC 1973 Core Operating System
CP/M file system Gary Kildall 1974 CP/M
V6FS Bell Labs 1975 Version 6 Unix
OS4000 GEC 1977 OS4000
FAT (8-bit) Marc McDonald, Microsoft 1977 Microsoft Disk BASIC
DOS 3.x Apple Computer 1978 Apple DOS
Pascal Apple Computer 1978 Apple Pascal
CBM DOS Commodore 1978 Microsoft BASIC (for CBM PET)
V7FS Bell Labs 1979 Version 7 Unix
ODS-2 DEC 1979 OpenVMS
FAT12 Tim Paterson 1980 QDOS, 86-DOS
AFS Carnegie Mellon University 1982 Multiplatform MultoOS
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
ProDOS Apple Computer 1983 ProDOS 8
MFS Apple Computer 1984 Mac OS
FAT16 Microsoft 1984 MS-DOS 3.0
Elektronika BK tape format NPO "Scientific centre" (now Sitronics) 1985 Vilnius Basic, BK monitor program
HFS Apple Computer 1985 Mac OS
Amiga OFS[16] Metacomco for Commodore 1985 Amiga OS
High Sierra Ecma International 1985 MS-DOS, Mac OS
NWFS Novell 1985 NetWare 286
FAT16B Compaq 1987 Compaq MS-DOS 3.31, DR DOS 3.31
MINIX V1 FS Andrew S. Tanenbaum 1987 MINIX 1.0
Amiga FFS Commodore 1988 Amiga OS 1.3
HPFS IBM & Microsoft 1988 OS/2
ISO 9660:1988 Ecma International, Microsoft 1988 MS-DOS, Mac OS, and AmigaOS
JFS1 IBM 1990 AIX[1]
VxFS VERITAS, (now Symantec) 1991 AIX, HP-UX, Solaris, Linux
ext Rémy Card 1992 Linux
WAFL NetApp 1992 Data ONTAP
MINIX V2 FS Andrew S. Tanenbaum 1992 MINIX 1.6 and 2.0
AdvFS DEC 1993[2] Digital Unix
NTFS Version 1.0 Microsoft, Tom Miller, Gary Kimura 1993 Windows NT 3.1
LFS Margo Seltzer 1993 Berkeley Sprite
ext2 Rémy Card 1993 Linux, Hurd
UFS1 Kirk McKusick 1994 4.4BSD
XFS SGI 1994 IRIX, Linux, FreeBSD
HFS (Hierarchical File System) IBM 1994 MVS/ESA (now z/OS)
Rock Ridge Young Minds Inc. 1994 Linux, Mac OS, Amiga OS, and FreeBSD
Joliet ("CDFS") Microsoft 1995 Microsoft Windows, Linux, Mac OS, and FreeBSD
PFS Michiel Pelt 1996 AmigaOS
Romeo Adaptec 1996 Microsoft Windows
UDF ISO/ECMA/OSTA 1995 -
FAT32 Microsoft 1996 Windows 95b[3]
QFS LSC Inc, Sun Microsystems 1996 Solaris
GPFS IBM 1996 AIX, Linux, Windows
Be File System Be Inc., D. Giampaolo, C. Meurillon 1996 BeOS
HFS Plus Apple Computer 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
SFS John Hendrikx 1998 AmigaOS, AROS, MorphOS
ext3 Stephen Tweedie 1999 Linux
ISO 9660:1999 Ecma International, Microsoft 1999 Microsoft Windows, Linux, Mac OS X, FreeBSD, and AmigaOS
JFS IBM 1999 OS/2 Warp Server for e-business
GFS Sistina (Red Hat) 2000 Linux
Melio FS Sanbolic 2001 Windows
NTFS Version 3.1 Microsoft 2001 Windows XP
ReiserFS Namesys 2001 Linux
zFS IBM 2001 z/OS (backported to OS/390)
FATX Microsoft 2002 Xbox
UFS2 Kirk McKusick 2002 FreeBSD 5.0
Lustre Cluster File Systems (later Oracle Corporation) 2002 Linux
OCFS Oracle Corporation 2002 Linux
VMFS2 VMware 2002 VMware ESX Server 2.0
ext3cow Zachary Peterson 2003 Linux
Fossil Bell Labs 2003 Plan 9 from Bell Labs 4
Google File System Google 2003 Linux
PramFS MontaVista 2003 Linux
Reliance[4] Datalight 2003 Windows CE, VxWorks, custom ports
VxCFS VERITAS, (now Symantec) 2004 AIX, HP-UX, Solaris, Linux
ZFS Sun Microsystems 2004 Solaris, FreeBSD, PC-BSD, FreeNAS
Reiser4 Namesys 2004 Linux
Non-Volatile File System Palm, Inc. 2004 Palm OS Garnet
MINIX V3 FS Andrew S. Tanenbaum 2005 MINIX 3
OCFS2 Oracle Corporation 2005 Linux
NILFS NTT 2005 Linux, (ReadOnly for NetBSD)
VMFS3 VMware 2005 VMware ESX Server 3.0
GFS2 Red Hat 2006 Linux
ext4 Various 2006 Linux
exFAT Microsoft 2006, 2009 Windows CE 6.0, Windows XP SP3, Windows Vista SP1
TexFAT/TFAT Microsoft 2006 Windows CE 6.0
Btrfs Oracle Corporation 2007 Linux
Ceph Sage Weil, Inktank Storage 2007, 2012 Linux
WBFS kwiirk and Waninkoko (Wii homebrew) 2008 Nintendo WII
HAMMER Matthew Dillon 2008 Dragonfly BSD
Tux3 Various 2008 Linux
UBIFS Nokia with help of University of Szeged 2008 Linux
Oracle ACFS Oracle Corporation 2009 Linux - Red Hat Enterprise Linux 5 and Oracle Enterprise Linux 5 only
Reliance Nitro[4] Datalight 2009 Windows CE, Windows Mobile, VxWorks, Linux, custom ports
LTFS IBM 2010 Linux, Mac OS X, planned Microsoft Windows,
IlesfayFS Ilesfay Technology Group 2011 Microsoft Windows, planned Red Hat Enterprise Linux
VMFS5 VMware 2011 VMware ESXi 5.0tux 3 stats
ReFS Microsoft 2012, 2013 Windows 2012 Server
Lanyard Filesystem Dan Luedtke 2012 Linux
F2FS Samsung 2012 Linux
File system Creator Year
introduced 		Original operating system

Limits

File system Maximum filename length Allowable characters in directory entries[5] Maximum pathname length Maximum file size Maximum volume size[6]
Acorn ADFS 10 bytes Any ISO 8859-1 character except: SPACE $ & % @ \ ^ : . # * " ¦ No limit defined Template:Ntss or Template:Ntss[7] Template:Ntss or Template:Ntss[8]
Apple DOS 3.x 30 bytes Any byte except NUL Template:Ntss, no subdirectories (105 files per disk) Un­known Template:Ntss DOS 3.3 (assuming standard 35 tracks)
Template:Ntss DOS 3.1, 3.2
Apple ProDOS 15 bytes A-Z, a-z, 0-9, and period 64 B, including slashes[9][10] Template:Ntss Template:Ntss
CP/M file system 8.3 any byte except: SPACE < > . , ; : = ? * [ ] % | ( ) / \[11] 16 "user areas", no subdirectories Template:Ntss[12] Template:Ntss to 512 MB[12]
IBM SFS 8.8 Un­known Non-hierarchical[13] Un­known Un­known
DECtape 6.3 A–Z, 0–9 DTxN:FILNAM.EXT = 15 Template:Ntss (577 * 640) Template:Ntss (578 * 640)
Elektronika BK tape format 16 bytes Un­known Non-hierarchical Template:Ntss Template:Ntss (approx) per side for 90 min cassette (limited only by tape length)
MicroDOS file system 14 bytes Un­known Un­known Template:Ntss Template:Ntss
Level-D 6.3 A–Z, 0–9 DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67 Template:Ntss (34,359,738,368 words (235-1); 206,158,430,208 SIXBIT bytes) Template:Ntss (approx; 64 * 178 MB)
RT-11 6.3 A–Z, 0–9, $ Non-hierarchical Template:Ntss (65536 * 512) Template:Ntss
V6FS 14 bytes[14] Any byte except NUL and /[15] No limit defined[16] Template:Ntss[17] Template:Ntss
DOS (GEC) 8 bytes A–Z, 0–9 Non-hierarchical Template:Ntss Template:Ntss
OS4000 8 bytes A–Z, 0–9
Period is directory separator 		No limit defined[16] Template:Ntss Template:Ntss (at least)
CBM DOS 16 bytes Any byte except NUL Non-hierarchical Template:Ntss Template:Ntss
V7FS 14 bytes[14] Any byte except NUL and /[15] No limit defined[16] Template:Ntss[18] Template:Ntss
exFAT 255 characters[19] Any Unicode except NUL No limit defined Template:Ntss Template:Ntss, 512 TB recommended[20]
TexFAT 247 characters Any Unicode except NUL No limit defined Template:Ntss Template:Ntss Tested[21]
FAT12 8.3 (255 UTF-16 code units with LFN)[14] Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[14][15] No limit defined[16] Template:Ntss (Template:Ntss) Template:Ntss (Template:Ntss)
FAT16 8.3 (255 UTF-16 code units with LFN)[14] Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[14][15] No limit defined[16] Template:Ntss (Template:Ntss) Template:Ntss or 4 GB
FAT32 8.3 (255 UTF-16 code units with LFN)[14] Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[14][15] No limit defined[16] Template:Ntss ([[FAT32+|Template:Ntss]][22]) Template:Ntss[23] (Template:Ntss)
FATX 42 bytes[14] ASCII. Unicode not permitted. No limit defined[16] Template:Ntss Template:Ntss
Fossil Un­known Un­known Un­known Un­known Un­known
MFS 255 bytes Any byte except : No path (flat filesystem) Template:Ntss Template:Ntss
HFS 31 bytes Any byte except :[24] Unlimited Template:Ntss Template:Ntss
HPFS 255 bytes Any byte except NUL[25] No limit defined[16] Template:Ntss Template:Ntss[26]
NTFS 255 characters[27][28][29] Depends on namespace used[27][28][29][30] 32,767 Unicode characters with each path component (directory or filename) commonly up to 255 characters long[16] Template:Ntss[31] Template:Ntss[31]
ReFS 255 unicode characters [32] Un­known Template:Ntss Template:Ntss Template:Ntss with 16kB cluster size (264 × 16 × 210). Windows stack addressing allows 16 EB
HFS Plus 255 UTF-16 code units[33] Any valid Unicode[15][34] Unlimited Template:Ntss Template:Ntss[35][36]
FFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
UFS1 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
UFS2 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
ext2 255 bytes Any byte except NUL[15] and / No limit defined[16] Template:Ntss[6] Template:Ntss
ext3 255 bytes Any byte except NUL[15] and / No limit defined[16] Template:Ntss[6] Template:Ntss
ext3cow 255 bytes Any byte except NUL,[15] / and @ No limit defined[16] Template:Ntss[6] Template:Ntss
ext4 255 bytes Any byte except NUL[15] and / No limit defined[16] Template:Ntss[6][37] Template:Ntss[38]
Lustre 255 bytes Any byte except NUL[15] and / No limit defined[16] Template:Ntss (on ext4) Template:Ntss (55 PB tested)
GPFS 255 UTF-8 codepoints Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss (4 PB tested)
GFS 255 Any byte except NUL[15] No limit defined[16] Template:Ntss[39] Template:Ntss[39]
ReiserFS 4,032 bytes/226 characters Any byte except NUL[15] No limit defined[16] Template:Ntss[40] (v3.6), 2 GB (v3.5) Template:Ntss
NILFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
Reiser4 3,976 bytes Any byte except / and NUL No limit defined[16] Template:Ntss on x86 Un­known
OCFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
OCFS2 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
Reliance 260 bytes OS specific Template:Ntss Template:Ntss Template:Ntss
Reliance Nitro 1,024 bytes OS specific 1024 bytes Template:Ntss Template:Ntss
JFS1 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
JFS 255 bytes Any Unicode except NUL No limit defined[16] Template:Ntss Template:Ntss
QFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss[41] Template:Ntss[41]
BFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss[42] Template:Ntss
AdvFS 226 characters Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
NSS 226 characters Depends on namespace used[43] Only limited by client Template:Ntss Template:Ntss
NWFS 80 bytes[44] Depends on namespace used[43] No limit defined[16] Template:Ntss Template:Ntss
ODS-5 236 bytes[45] Un­known 4,096 bytes[46] Template:Ntss Template:Ntss
VxFS 255 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss
UDF 255 bytes Any Unicode except NUL 1,023 bytes[47] Template:Ntss Template:Ntss (hard disk), 8 TB (optical disc)[48]
MINIX V1 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL[15] No limit defined[16] Template:Ntss[49] Template:Ntss[49]
MINIX V2 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL[15] No limit defined[16] Template:Ntss[49] Template:Ntss, then 2 TB[49]
MINIX V3 FS 60 bytes Any byte except NUL[15] No limit defined[16] Template:Ntss Template:Ntss[49]
VMFS2 128 Any byte except NUL and /[15] 2,048 Template:Ntss[50] Template:Ntss
VMFS3 128 Any byte except NUL and /[15] 2,048 Template:Ntss[50] Template:Ntss
ISO 9660:1988 Level 1: 8.3,
Level 2 & 3: ~ 180 		Depends on Level[51] ~ 180 bytes? Template:Ntss (Level 1 & 2) to 8 TB (Level 3)[52] Template:Ntss[53]
Joliet ("CDFS") 64 Unicode characters All UCS-2 code except * / \ : ; and ?[54] Un­known Template:Ntss (same as ISO 9660:1988) Template:Ntss (same as ISO 9660:1988)
ISO 9660:1999 Un­known (207?) Un­known Un­known Un­known Un­known
High Sierra Un­known Un­known Un­known Un­known Un­known
HAMMER Un­known Un­known Un­known Un­known Template:Ntss
LTFS Un­known Un­known Un­known Un­known Un­known
PramFS 31 bytes Any byte except NUL Un­known Template:Ntss Template:Ntss
Lanyard Filesystem 255 bytes Any byte except NUL and /[15] No limit defined Template:Ntss Template:Ntss to Template:Ntss[55]
LEAN 4,068 bytes[56] case sensitive, in UTF-8 (any Unicode codepoint) No limit defined Template:Ntss Template:Ntss
XFS 255 bytes[57] Any byte except NUL[15] No limit defined[16] Template:Ntss[58] Template:Ntss[58]
ZFS 255 bytes Any Unicode except NUL No limit defined[16] Template:Ntss Template:Ntss
Btrfs 255 bytes Any byte except NUL Un­known Template:Ntss Template:Ntss
File system Maximum filename length Allowable characters in directory entries[5] Maximum pathname length Maximum file size Maximum volume size[6]

Metadata

File system Stores file owner POSIX file permissions Creation timestamps Last access/ read timestamps Last content modification timestamps Disk copy created Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC Max Timestamp Granularity
CBM DOS No No No No No No No No No No No No Un­known
CP/M file system No No Yes[59] No Un­known Un­known No No No No No No Un­known
DECtape No No Yes No Un­known Un­known No No No No No No Un­known
Elektronika BK tape format No No No No Un­known Un­known No No No No No Yes Un­known
Level-D Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No No No Un­known
RT-11 No No Yes No No No No No No No No No Un­known
DOS (GEC) Yes No Yes Yes Yes Un­known No No No No No No Un­known
OS4000 Yes No Yes Yes Yes Un­known No No No No No No Un­known
V6FS Yes Yes No Yes Yes Un­known Yes No No No No No Un­known
V7FS Yes Yes No Yes Yes Un­known Yes No No No No No Un­known
FAT12 No[60] No[61] Partial[62] Partial[62] Yes Yes No[63] No No No No[64] No 10 milliseconds
FAT16 No[60] No[61] Partial[62] Partial[62] Yes Yes No[63] No No No No[64] No 10 milliseconds
FAT32 No No Partial[62] Partial[62] Yes Yes No[63] No No No No No 10 milliseconds
exFAT No No Yes Yes Yes No Un­known No No Un­known Un­known Partial 10 milliseconds
HPFS Yes[65] No Yes Yes Yes Un­known No No No Un­known Yes No Un­known
NTFS Yes Yes[66] Yes Yes Yes No Yes No Yes Yes[67] Yes No 100 nanoseconds
HFS No No Yes No Yes No No Yes No No Yes No Un­known
HFS Plus Yes Yes Yes Yes Yes No Yes Yes Yes Yes[68] Yes No 1 second
FFS Yes Yes No Yes Yes Un­known Yes No No No No No Un­known
UFS1 Yes Yes No Yes Yes Un­known Yes No Yes[69] Yes[69] No[70] No Un­known
UFS2 Yes Yes Yes Yes Yes Un­known Yes No Yes[69] Yes[69] Yes No Un­known
LFS Yes Yes No Yes Yes Un­known Yes No No No No No Un­known
ext2 Yes Yes No Yes Yes Un­known Yes No Yes[71] Yes[71] Yes No 1 second
ext3 Yes Yes No Yes Yes No Yes No Yes[71] Yes[71] Yes No 1 second
ext3cow Yes Yes No Yes Yes No Yes No Yes[71] Yes[71] Yes No 1 second
ext4 Yes Yes Yes Yes Yes Un­known Yes No Yes[71] Yes[71] Yes Partial[72] 1 nanosecond
Lustre Yes Yes Partial[73] Yes Yes No Yes No Yes Yes Yes Partial[74][75] Un­known
GPFS Yes Yes Yes Yes Yes Un­known Yes No Yes Yes Yes Yes Un­known
GFS Yes Yes No Yes Un­known Un­known Yes No Yes[71] Yes[71] Yes No Un­known
NILFS Yes Yes Yes No Un­known Un­known Yes No Planned No Planned Yes Un­known
ReiserFS Yes Yes No Yes Yes No No No No No No No Un­known
Reiser4 Yes Yes No Yes Yes Un­known Yes No No No No No Un­known
OCFS No Yes No No Un­known Un­known Yes Yes No No No No Un­known
OCFS2 Yes Yes No Yes Un­known Un­known Yes No Yes No Yes Partial[76] Un­known
Reliance No No Yes No Yes No No No No No No Partial[77] Un­known
Reliance Nitro Linux port Linux port Yes Yes Yes No No No Linux port No Yes Partial[77] Un­known
XFS Yes Yes No Yes Yes Un­known Yes No Yes Yes[71] Yes Partial 1 nanosecond
JFS Yes Yes Yes Yes Yes Un­known Yes No Yes Yes Yes No Un­known
QFS Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No Yes No Un­known
BFS Yes Yes Yes No Un­known Un­known No No No No Yes No Un­known
AdvFS Yes Yes No Yes Yes Un­known Yes No Yes No Yes No Un­known
NSS Yes Yes Yes[78] Yes[78] Un­known Un­known Yes Yes[78] Yes Un­known Yes[79][80] No Un­known
NWFS Yes Un­known Yes[78] Yes[78] Un­known Un­known Yes Yes[78] Yes Un­known Yes[79][80] No Un­known
ODS-5 Yes Yes Yes Un­known Un­known Un­known Un­known Yes Yes Un­known Yes[81] No Un­known
VxFS Yes Yes Yes Yes Yes Un­known Yes No Yes Un­known Yes[71] No Un­known
UDF Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No Yes No Un­known
Fossil Yes Yes[82] No Yes Un­known Un­known Yes No No No No No Un­known
ZFS Yes Yes Yes Yes Yes Un­known Yes Yes Yes Yes[83] Yes[84] Yes Un­known
VMFS2 Yes Yes No Yes Un­known Un­known Yes No No No No No Un­known
VMFS3 Yes Yes No Yes Un­known Un­known Yes No No No No No Un­known
ISO 9660:1988 No No Yes[85] No[86] Yes[87] Un­known No No No No No No Un­known
Joliet ("CDFS") No No Yes[85] No[86] Yes[87] Un­known No No No No No No Un­known
ISO 9660:1999 No No Yes No Un­known Un­known No No No No No No Un­known
High Sierra No No Yes No Un­known Un­known No No No No No No Un­known
Btrfs Yes Yes Yes Yes Yes Un­known Yes Un­known Yes Yes Yes Yes 1 nanosecond
Lanyard Filesystem No No Yes No Yes No Yes No No No No No 1 nanosecond
PramFS Yes Yes No Yes Yes Un­known Yes No Yes Yes Yes Yes 1 second
File system Stores file owner POSIX file permissions Creation timestamps Last access/read timestamps Last content modification timestamps Disk copy created Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC Max Timestamp Granularity

Features

File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log Snapshot XIP Encryption COW Integrated LVM Data deduplication Volumes are resizeable
Lanyard Filesystem No No No No Yes Yes No No No No No No No Offline (cannot be shrunk)
CBM DOS No No No No Yes Yes No No No No No No No No
CP/M file system No No No No No No No No No No No No No Un­known
DECtape No No No No No No No No No No No No No Un­known
Level-D No No No No No No No No No No Un­known Un­known Un­known Un­known
RT-11 No No No No No No No No No No No No No Un­known
DOS (GEC) No No No No No No No No No No No No No Un­known
OS4000 No Yes[88] No No No No No No No No No No No Un­known
V6FS Yes No No No Yes Yes No No No No No No No Un­known
V7FS Yes No[89] No No Yes Yes No No No No No No No Un­known
FAT12 No No No No No Partial No No No No No No No Offline[90]
FAT16 No No No No No Partial No No No No No No No Offline[90]
FAT32 No No No No No Partial No No No No No No No Offline[90]
exFAT No No No No No Yes No Un­known Un­known No Un­known Un­known Un­known Un­known
GFS Yes Yes[91] Yes Yes[92] Yes Yes No No No No Un­known Un­known Un­known Online
GPFS Yes Yes Un­known Un­known Yes Yes Yes Yes Yes No Yes Yes No Online
HAMMER Yes Yes Un­known Un­known Yes Yes Un­known Yes Un­known Un­known Un­known Un­known On demand Un­known
HPFS No No No No No Yes No Un­known No No Un­known Un­known No Un­known
NTFS Yes Yes[93] No[94] Yes[94] Yes[95] Yes Yes Partial[96] Yes Yes Partial Un­known Yes (Windows Server 2012)[97] Online[98]
HFS No Yes[99] No No No Yes No No No No No No No Un­known
HFS Plus Yes[100] Yes No Yes[101] Partial[102] Yes Yes[103] No No Yes[104] No No No Yes[105]
FFS Yes Yes No No[106] Yes Yes No No No No No No No Offline (cannot be shrunk)[107]
UFS1 Yes Yes No No Yes Yes No No No No No No No Un­known
UFS2 Yes Yes No No[108][109] Yes Yes No Yes Un­known No No No No Offline (cannot be shrunk)[110]
LFS Yes Yes Yes[111] No Yes Yes No No No No Un­known Un­known Un­known Un­known
ext2 Yes Yes No No Yes Yes No No Yes[112] No No No No Online[113]
ext3 Yes Yes Yes[114] Yes Yes Yes No No Yes Yes[citation needed] No No No Online[113]
ext3cow Yes Yes Yes[114] Yes Yes Yes Un­known Yes Un­known Yes Yes No No Un­known
ext4 Yes Yes Yes[114] Yes Yes Yes No No Yes Yes[citation needed] No No No Online[113]
Lustre Yes Yes Yes[114] Yes Yes Yes Yes in 2.0 and later No[75] No No No[75] No[75] No[75] Online[115]
NILFS Yes Yes Yes[111] No Yes Yes Yes Yes No No Yes Un­known Un­known Online (since Linux-3.x and nilfs-utils 2.1)
ReiserFS Yes Yes No[116] Yes Yes Yes No No No No No No No Online
Reiser4 Yes Yes Yes No Yes Yes No Un­known No Yes[117] Yes No Un­known Online (can only be shrunk offline)
OCFS No Yes No No Yes Yes No No No No Un­known Un­known Un­known Un­known
OCFS2 Yes Yes Yes Yes Yes Yes No Partial[118] No No Un­known No No Online for version 1.4 and higher
Reliance No No No[119] No No Yes No No No No Yes No No Un­known
Reliance Nitro Yes Yes No[119] No Depends on OS Yes No No No No Yes No No Un­known
XFS Yes Yes Yes Yes Yes[120] Yes No No No No No No No Online (cannot be shrunk)
JFS Yes Yes No Yes Yes[121] Yes No Yes No No No Un­known Un­known Online (cannot be shrunk)[122]
QFS Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
Be File System Yes Yes No Yes Yes Yes Un­known No No No No No No Un­known
NSS Yes Yes Un­known Yes Yes[123] Yes[123] Yes[124] Yes No Yes Un­known Un­known Un­known Un­known
NWFS Yes[125] Yes[125] No No Yes[123] Yes[123] Yes[124] Un­known No No No Yes[126] Un­known Un­known
ODS-2 Yes Yes[127] No Yes No No Yes Yes No No Un­known Un­known Un­known Un­known
ODS-5 Yes Yes[127] No Yes No Yes Yes Yes Un­known No Un­known Un­known Un­known Un­known
UDF Yes Yes Yes[111] Yes[111] Yes Yes No No Yes No No No No Un­known
VxFS Yes Yes Yes No Yes Yes Yes Yes[128] Un­known No Un­known Un­known Yes Un­known
Fossil No No No No Yes Yes Yes Yes No No Un­known No Yes[129] Un­known
ZFS Yes Yes Yes[130] No[130] Yes Yes No Yes No Yes Yes Yes Yes Online (cannot be shrunk)[131]
VMFS2 Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
VMFS3 Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
Btrfs Yes Yes No No Yes Yes Yes Yes No Planned[132] Yes Yes Yes (via bedup)[133] Online
PramFS No Yes No No Yes Yes No No Yes No No No No No
File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log Snapshotting XIP Encryption COW integrated LVM Data deduplication Volumes are resizeable

Allocation and layout policies

File system Block suballocation Variable file block size[134] Extents Allocate-on-flush Sparse files Transparent compression
CBM DOS No Partial[135] No No No No
CP/M filesystem No No Yes No Yes No
DECtape No No No No No No
Level-D Yes No Yes No No No
DOS (GEC) No Yes Yes No No No
OS4000 No Yes Yes No No No
V6FS No No No No Yes No
V7FS No No No No Yes No
FAT12 No No No No No No[136]
FAT16 No No No No No No[136]
FAT32 No No No No No No
exFAT Un­known No No Un­known No No
GFS Partial[137] No No No Yes No
HPFS No No Yes No No No
NTFS Partial No Yes No Yes Partial[138]
HFS Plus No No Yes Yes No Yes
FFS 8:1[139] No No No Yes No
UFS1 8:1[139] No No No Yes No
UFS2 8:1[139] Yes No No Yes No
LFS 8:1[139] No No No Yes No
ext2 No[140] No No No Yes No[141]
ext3 No[140] No No No Yes No
ext3cow No[140] No No No Yes No
ext4 No[140] No Yes Yes Yes No
Lustre No No Yes Yes Yes No
ReiserFS Yes No No No Yes No
Reiser4 Yes No Yes[142] Yes Yes Yes[117]
OCFS No No Yes No Un­known No
OCFS2 No No Yes No Yes No
Reliance No No No No No No
Reliance Nitro No No Yes No Yes No
XFS No No Yes Yes Yes No
JFS Yes No Yes No Yes only in JFS1 on AIX[143]
QFS Yes No No No Un­known No
BFS No No Yes No Un­known No
NSS No No Yes No Un­known Yes
NWFS Yes[144] No No No Un­known Yes
ODS-5 No No Yes No Un­known No
VxFS Un­known No Yes No Yes No
UDF No No Yes Depends[145] No No
Fossil No No No No Un­known Yes
VMFS2 Yes No No No Yes No
VMFS3 Yes No Yes No Yes No
PramFS No No No No Yes No
ZFS Partial[146] Yes No Yes Yes Yes
NILFS No No Planned Yes Yes No
BTRFS Partial[147] No Yes Yes Yes Yes
File system Block suballocation Variable file block size[134] Extents Allocate-on-flush Sparse files Transparent compression

Supporting operating systems

File system DOS Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2 Windows CE Windows Mobile VxWorks HP-UX Plan 9
FAT12 Yes Yes Yes Yes Yes Yes Yes Yes No Partial on diskettes only, through dos* commands Un­known Yes Yes[148] Un­known Yes[149] Un­known Yes
FAT16 Yes since DOS 3.0, FAT16B since DOS 3.31 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known Yes Yes[148] Yes Yes[149] Un­known Yes
FAT32 Yes since DOS 7.1[150] Yes since Windows 95 OSR2 Yes since Windows 2000 Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known with third-party app[151] Yes[148] Yes Yes[149] Un­known Yes
exFAT No Partial read-only with third party driver Yes : Win7, Vista SP1, can be added to XP SP2 with third party driver No Yes 10.6.5+ No No Yes No No No Yes No Un­known Un­known Un­known
NTFS with third-party driver with third-party driver[152] Yes Yes Kernel 2.2 or newer, or with NTFS-3G or ntfsprogs with NTFS-3G or MacFUSE partial read-only in kernel, read-write with NTFS-3G with NTFS-3G with NTFS-3G with NTFS-3G on Opensolaris Un­known Un­known Partial read-only third-party driver[153] with 3rd-party driver[154] No Un­known Un­known Un­known
HFS No with third-party app[155] with third-party app[155] Yes Yes Partial: read-only since OSX 10.6[156] with third-party app[157][158] Un­known Un­known Un­known No with third-party app[159] No No No Un­known No
HFS Plus No with third-party app[155] with third-party app[155] Partial - write support occurs if journal is empty, but requires a force mount. Yes since Mac OS 8.1 Yes Partial read-only third-party app[160] Un­known Un­known Un­known No with third-party app No No No Un­known No
HPFS with third-party driver Partial read-only third-party driver[161] included until v3.51, third-party driver until 4.0[162] Yes No Un­known Yes Un­known Un­known Un­known Un­known Yes No Un­known Un­known Un­known No
FFS No Un­known Un­known Yes[163] No Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
UFS1 No Un­known Un­known Partial - read only No Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known No Un­known Un­known
UFS2 No Un­known Un­known Partial - read only No No Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known No Un­known Un­known
ext2 Un­known Un­known with Ext2Fsd (complete)[164] or Ext2 IFS (partial, no large inodes)[165] or Ext2Read (read-only, also on LVM2)[166] Yes since kernel 0.99 No with fuse-ext2,[167] ExtFS[168] and ext2fsx[169] Yes Un­known Un­known Un­known Un­known third-party app[170] with 3rd-party app[171] with 3rd-party app[171] Un­known Un­known Yes
ext3 Un­known Un­known with Ext2Fsd (complete)[164] or Ext2 IFS (partial, no large inodes)[165] or Ext2Read (read-only, also on LVM2)[166] Yes since kernel 2.4.15 No with fuse-ext2[167] and ExtFS[168] Yes Un­known Yes Un­known Un­known Un­known with 3rd-party app[171] with 3rd-party app[171] Un­known Un­known No
ext3cow Un­known Un­known Un­known Yes Kernel 2.6.20 Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
ext4 No No Partial with Ext2Fsd (partial, extents limited)[164] or Ext2Read (read-only, also on LVM2)[166] Yes since kernel 2.6.28 No with fuse-ext2 (partial),[167] ext4fuse (read-only)[172] and ExtFS (full read/write)[168] Partial with ext4fuse (read-only)[172] Un­known Un­known Un­known Un­known Un­known No Un­known Un­known Un­known No
Btrfs No No No Yes since kernel 2.6.29 No No No No No No No No No No Un­known Un­known No
ZFS No No No with 3rd Party kernel module[173] or FUSE[174] No with free 3rd-party software[175] Yes No Yes No No No Un­known Un­known Un­known Un­known No
Lustre No No Partial - under development[176] Yes[177] No Partial - via FUSE Partial - via FUSE No Partial - under development[178] No No No No No Un­known Un­known No
GFS No Un­known Un­known Yes since kernel 2.6.19 No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
NILFS No Un­known Un­known Yes since kernel 2.6.30 No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
ReiserFS No Un­known Partial with third-party app Yes since kernel 2.4.1 No No Partial - read only Un­known Un­known Un­known Un­known Un­known with 3rd-party app[171] with 3rd-party app[171] Un­known Un­known No
Reiser4 No Un­known Un­known with a kernel patch No No No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
OCFS No Un­known Un­known Yes No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
OCFS2 No Un­known Un­known Yes No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
Reliance No No No No No No No No No No No No Yes No Yes Un­known No
Reliance Nitro No No No Yes No No No No No No No No Yes Yes Yes Un­known No
XFS No Un­known Un­known Yes since kernel 2.4 No Un­known Partial: read-only Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
JFS No Un­known Un­known Yes No No No Un­known Un­known Yes Un­known Yes No No Un­known No
QFS No Un­known Un­known via client software[179] No Un­known No Un­known Yes Un­known Un­known Un­known No No Un­known Un­known No
BFS No Un­known Un­known Partial - read-only No Un­known No Yes Un­known Un­known Un­known Un­known No No Un­known Un­known No
NSS Un­known Un­known Un­known with Novell OES2[citation needed] No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
NWFS Un­known Un­known Un­known via ncpfs client software[180] No Un­known Yes Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
UDF Un­known Partial read-only support of UDF 1.02 since Win98 and WinME Yes[181] Yes Yes since Mac OS 9 Yes Yes Un­known Yes Un­known Un­known Un­known Yes Un­known Un­known Un­known No
VxFS No Un­known Un­known Yes No Un­known No Un­known Yes Yes Un­known Un­known No No Un­known Yes No
Fossil No No No No No No No No No No No No No No No Un­known Yes
IBM HFS No No No No No No No No No No Yes No Un­known Un­known Un­known Un­known No
IBM zFS No No No No No No No No No No Yes No Un­known Un­known Un­known Un­known No
IBM GPFS[182] No No Yes Yes since 2001 No No No No No Yes No No Un­known Un­known Un­known Un­known No
VMFS2 Un­known Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
VMFS3 No Un­known Un­known Partial read-only with vmfs[183] Un­known Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
DECtape No Un­known Un­known with AncientFS[184] No with AncientFS[184] with AncientFS[184] Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known No
Level-D No Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
RT-11 No Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known No No Yes Un­known No
ODS-2 No Un­known Un­known Partial read-only with tool or kernel module[185] No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
ODS-5 No Un­known Un­known Partial read-only with kernel module[185] No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known No
LFS No Un­known Un­known with logfs[186] and others No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known Un­known
LTFS No Un­known Un­known Yes No Yes No No No No No No No No Un­known Un­known No
PramFS No No No Yes No No No No No No No No No No No No No
File system DOS Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2 Windows CE Windows Mobile VxWorks HP-UX Plan 9

See also

Notes

  1. ^ IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, ported from OS/2 to AIX and Linux, was first shipped in OS/2 Warp Server for e-Business in 1999. It was released as JFS2 on AIX 5L.
  2. ^ "Polycenter File System — HELP", Tru64 Unix managers, ORNL
  3. ^ Microsoft first introduced FAT32 in 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.
  4. ^ a b Specifications for the Reliance file systems are available here [1].
  5. ^ a b 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; and particular and operating systems may also place restrictions of their own, across all filesystems. MS-DOS, Microsoft Windows, and OS/2 disallow the characters \ / : ? * " > < | and NUL in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
  6. ^ a b c d e f 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 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 kB).
  7. ^ While the on-disk filesystem structure uses a 4-byte file length, which allows files up to 4G, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum file size to 512M.
  8. ^ While the on-disk filesystem structure uses a 3-byte sector number, which allows access to 4G of disk space, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum disk size to 512M.
  9. ^ "ProDOS 8 Technical Reference Manual". Retrieved 31 May 2013.
  10. ^ Beneath Apple ProDOS (PDF). Quality Software. 1985. pp. 2–8. ISBN 0-912985-05-4.
  11. ^ The CP/M filesystem itself does have limitations in regard to the allowed filename characters to be used, but officially the following characters are not allowed: SPACE < > . , ; : = ? * [ ] % | ( ) / \. CCP reserves the following characters for special purposes: SPACE , = _ . : ;, PIP additionally reserves: < > [ ].
  12. ^ a b "Maximum CP/M-80 2.2 volume size?", comp.os.cpm, Google Groups, retrieved 2009-10-09
  13. ^ "SFS file system". Publib.boulder.ibm.com. Retrieved 2013-02-05.
  14. ^ a b c d e f g h i Depends on whether the FAT12, FAT16, and FAT32 implementation has support for long filenames (LFNs). Where it does not, as in OS/2, MS-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 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 do not normally contain lowercase letters. Also note that a few special names (CON, NUL, LPT1) should be avoided, as some operating systems (notably DOS and windows) effectively reserve them.
  15. ^ 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 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.
  16. ^ 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 The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. MS-DOS/PC DOS do not support full pathnames longer than 66 bytes for FAT12, FAT16 and FAT32 volumes. This limit exists because these operating systems were designed around a fixed-length internal data structure named Current Directory Structure, which holds the absolute paths of the current working directories of all volumes. The FAT12/FAT16 file system implementation under Concurrent DOS and DR DOS 3.31 to 6.0 (prior to 1992 updates) did not impose any such limits on the directory depth due to their internal representation of current working directories as dynamically updated chain of double-linked relative directories. The introduction of a DOS-like CDS (instead of only an emulation thereof) for compatibility purposes with BDOS 7.0 in 1992 imposed the same length limits on PalmDOS, DR DOS 6.0 (since 1992 update), Novell DOS, OpenDOS, etc. as known from MS-DOS/PC DOS. Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Most Windows programs will fail when full path exceeds 255 characters (including Explorer and CMD.EXE). Linux has a pathname limit of 4,096.
  17. ^ See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html
  18. ^ 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 GB.
  19. ^ Table "Limits" states a maximum of 255 Unicode characters for the filename [2]
  20. ^ "KB955704". 2009-01-27. Description of the exFAT file system driver update package [for 32-bit XP]
  21. ^ "msdn TexFAT File Naming Limitations". 2009-10-14.
  22. ^ Udo Kuhnt, Luchezar Georgiev, Jeremy Davis (2007). FAT+. FATPLUS.TXT, draft revision 2 ([3], [4]).
  23. ^ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 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. [5]
  24. ^ As Mac OS X is a Unix-like system, which supports : in file names, and which uses / as a pathname component separator, : in file names is represented on disk in HFS and HFS+ as /.
  25. ^ 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.
  26. ^ 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 GB.
  27. ^ a b NTFS allows files to have multiple names, in separate namespaces: Win32, DOS, Win32&DOS, and Posix. Windows APIs create files with Win32 "long" names (1–255 characters), sometimes with an additional "short"/"alias" DOS name in the "8.3" format (12 characters).
  28. ^ a b Richard Russon and Yuval Fledel. "NTFS Documentation" (PDF). Retrieved 2011-06-26.
  29. ^ a b "Naming Files, Paths, and Namespaces (MSDN Library article)". NB: This article includes discussion of the NT & Win32 namespaces used by Windows APIs; these are distinct from the NTFS filename namespaces.
  30. ^ In the Win32 namespace, any UTF-16 code unit (case insensitive) except NUL and \ / : * ? " < > | is allowed; in the Posix namespace, any UTF-16 code unit (case sensitive) except NUL and / is allowed; in the DOS namespace, any character in the U+0021–U+007E range except \ / : * ? " < > | is allowed. Windows APIs require Win32 namespace compatibility, which prevents access to folders & files having only Posix names containing Win32-incompatible characters.
  31. ^ 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 TB and the file size to 16 TB respectively."How NTFS Works".
  32. ^ "MSDN Blogs - Resilient File System, Windows 8 RC's filename length reduced (from 32K to 255) with Windows 8 RTM for NTFS compatibility". Blogs.msdn.com. 2012-01-16. Retrieved 2013-02-05.
  33. ^ The 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.
  34. ^ 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.
  35. ^ Docs, Apple
  36. ^ Docs
  37. ^ "Interviews/EricSandeen". FedoraProject. 2008-06-09. Retrieved 2009-10-09.
  38. ^ ext4 1.42 "This release of e2fsprogs has support for file systems > 16 TB"
  39. ^ a b Depends on kernel version and arch. For 2.4 kernels the max is 2 TB. For 32-bit 2.6 kernels it is 16 TB. For 64-bit 2.6 kernels it is 8 EB.
  40. ^ ReiserFS has a theoretical maximum file size of 1 EB, but "page cache limits this to 8TB on architectures with 32 bit int"[6]
  41. ^ 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.
  42. ^ Varies wildly according to block size and fragmentation of block allocation groups.
  43. ^ a b NSS allows files to have multiple names, in separate namespaces.
  44. ^ 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.
  45. ^ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  46. ^ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  47. ^ This restriction might be lifted in newer versions.
  48. ^ 232 × block size
  49. ^ a b c d e "File, file system, and memory size limits in Minix". Minix1.woodhull.com. Retrieved 2013-02-05.
  50. ^ 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.
  51. ^ ISO 9660#Restrictions
  52. ^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GB in size. See ISO 9660#The 2/4 GB file size limit
  53. ^ 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.
  54. ^ Joliet Specification
  55. ^ https://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt
  56. ^ "LEAN file system". Freedos-32.sourceforge.net. Retrieved 2013-02-05.
  57. ^ Note that the filename can be much longer XFS#Extended_attributes
  58. ^ a b XFS has a limitation under Linux 2.4 of 64 TB file size, but Linux 2.4 only supports a maximum block size of 2 TB. This limitation is not present under IRIX.
  59. ^ Implemented in later versions as an extension
  60. ^ a b Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store file owner information in reserved fields of directory entries on FAT12 and FAT16 volumes, if the optional multi-user security module is loaded. If loaded, most external commands invoke support for special /U:owner/group command line options to deal with this extra information.
  61. ^ a b Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, DR DOS, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store read/write/delete/execute access permissions and file/directory passwords in reserved fields of directory entries on FAT12 and FAT16 volumes. This is an integral part of the design, therefore passwords can be appended to file or directory names with semicolon (for example: dirname;dirpwd\filename;filepwd), the PASSWORD command can be used to control permissions and some commands support a special /P:pwd option to deal with this feature.
  62. ^ a b c d e f File creation and file access timestamps are supported only by DOS 7.0 and higher, and typically only when explicitly enabled.
  63. ^ a b c 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.
  64. ^ a b 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.
  65. ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  66. ^ 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.
  67. ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [7]
  68. ^ "As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See". Trustedbsd.org. Retrieved 2013-02-05.
  69. ^ a b c d Access-control lists and MAC labels are layered on top of extended attributes.
  70. ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  71. ^ a b c d e f g h i j k l 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.
  72. ^ ext4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming
  73. ^ Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
  74. ^ Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
  75. ^ a b c d e Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
  76. ^ ocfs2 computes and validates checksums of metadata objects like inodes and directories. It also stores an error correction code capable to fixing single-bite errors.
  77. ^ a b CRCs are employed for certain types of metadata.
  78. ^ a b c d e f The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
  79. ^ 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.
  80. ^ 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.
  81. ^ Record Management Services (RMS) attributes include record type and size, among many others.
  82. ^ 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.
  83. ^ MAC/Sensitivity labels are per filesystem. A label per file are not out of the question as a future compatible change but aren't part of any available version of ZFS.
  84. ^ Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS. ZFS also has "system attributes" used for storing MS-DOS/NTFS compatible attributes for use by CIFS; as well as some attributes ported from FreeBSD
  85. ^ a b Time the file was recorded on the volume always available; "File Creation Date and Time" available only if the file has an Extended Attribute block.
  86. ^ a b Not applicable to file systems on a read-only medium.
  87. ^ a b Available only if the file has an Extended Attribute block.
  88. ^ Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
  89. ^ 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.
  90. ^ a b c "6", Parted manual, GNU
  91. ^ 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
  92. ^ Optional journaling of data
  93. ^ As of Windows Vista, NTFS fully supports soft links. See this Microsoft article on Vista kernel improvements. NTFS 5.0 (Windows 2000) and higher can create junctions, which allow any valid local directory (but not individual files) ("target" of junction) to be mapped to an NTFS version thereof ("source" = location of junction). The source directory must lie on an NTFS 5+ partition, but the target directory can lie on any valid local partition and needn't be NTFS. Junctions are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.
  94. ^ a b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  95. ^ 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.
  96. ^ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
  97. ^ Rick Vanover. "Windows Server 8 data deduplication". Retrieved 2011-12-02.
  98. ^ "How to Shrink and Extend NTFS Volumes in Windows". Bleepingcomputer.com. Retrieved 2013-02-05.
  99. ^ Mac OS System 7 introduced the 'alias', analogous to the POSIX symbolic link but with some notable differences. Not only could they cross file systems but they could point to entirely different file servers, and recorded enough information to allow the remote file system to be mounted on demand. It had its own API that application software had to use to gain their benefits-- this is the opposite approach from POSIX which introduced specific APIs to avoid the symbolic link nature of the link. The Finder displayed their file names in an italic font (at least in Roman scripts), but otherwise they behaved identically to their referent.
  100. ^ "Hard Links on HFS". Developer.apple.com. Retrieved 2013-02-05.
  101. ^ Metadata-only journaling was introduced in the Mac OS 10.2.2 HFS Plus driver; journaling is enabled by default on Mac OS 10.3 and later.
  102. ^ Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS 10.3 on the command newfs_hfs -s will create a case-sensitive new file system. 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. See Apple's File System Comparisons (which hasn't been updated to discuss HFSX) and Technical Note TN1150: HFS Plus Volume Format (which provides a very technical overview of HFS Plus and HFSX).
  103. ^ Mac OS 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). See fslogger.
  104. ^ As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.
  105. ^ Since Mac OS X Snow Leopard, online resizing is supported."How to resize a live partition in Snow Leopard and Lion".
  106. ^ "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.
  107. ^ "OpenBSD growfs(8) manpage". Openbsd.org. 2008-11-28. Retrieved 2013-02-05.
  108. ^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
  109. ^ Block level journals can be added by using gjournal module in FreeBSD.
  110. ^ "FreeBSD growfs(8) manpage". Freebsd.org. 2012-04-30. Retrieved 2013-02-05.
  111. ^ a b c d UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  112. ^ Linux kernel versions 2.6.12 and newer.
  113. ^ a b c Offline growing/shrinking as well as online growing: "Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)".
  114. ^ a b c d Off by default.
  115. ^ Can be shrunk online by migrating files off an OST and removing the OST, or offline with ext3/4 backing filesystems by shrinking the OST filesystem
  116. ^ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.[why?]
  117. ^ a b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  118. ^ OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
  119. ^ a b File system implements reliability via atomic transactions.
  120. ^ Optionally no on IRIX.
  121. ^ 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.
  122. ^ [8][dead link]
  123. ^ 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.
  124. ^ 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. (Filesystem Events tracked by NSure)
  125. ^ a b Available only in the "NFS" namespace.
  126. ^ Limited capability. Volumes can span physical disks (volume segment)
  127. ^ a b These are referred to as "aliases".
  128. ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  129. ^ When used with venti.
  130. ^ 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.
  131. ^ "How to resize ZFS".
  132. ^ McPherson, Amanda (2009-06-22), A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, retrieved 2009-09-01
  133. ^ Wiki, BTRFS, Deduplication
  134. ^ 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.
  135. ^ only for .REL (record structured) files, up to 254 bytes/record
  136. ^ a b SuperStor in DR DOS 6.0 and PC DOS 6.1, DoubleSpace in MS-DOS 6.0, DriveSpace in MS-DOS 6.22, Windows 95 and Windows 98, and Stacker in Novell DOS 7, OpenDOS 7.01, DR-DOS 7.02/7.03 and PC DOS 7.0/2000 were data compression schemes for FAT.
  137. ^ Only for "stuffed" inodes
  138. ^ Only if formatted with 4kB-sized clusters or smaller
  139. ^ a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  140. ^ a b c d Fragments were planned, but never actually implemented on ext2 and ext3.
  141. ^ e2compr, a set of patches providing block-based compression for ext2, has been available since 1997, but has never been merged into the mainline Linux kernel.
  142. ^ In "extents" mode.
  143. ^ "AIX documentation: JFS data compression". IBM.
  144. ^ 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.
  145. ^ Depends on UDF implementation.
  146. ^ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  147. ^ Btrfs can only inline files smaller than 3916B with its metadata"Mailing list discussion".
  148. ^ a b c Files, Databases, and Persistent Storage. MSDN.
  149. ^ a b c Via dosFs.
  150. ^ Native FAT32 support with MS-DOS 7.10 and 8.0. Loadable FAT32 support for any DOS since 3.31 with DRFAT32 redirector driver. Native FAT32 support since OEM DR-DOS 7.04, bootable FAT32 support since OEM DR-DOS 7.06. Native FAT32 support with OEM PC DOS 7.10.
  151. ^ "OS/2 and eComstation FAT32 Driver". Hobbes.nmsu.edu. Retrieved 2013-02-05.
  152. ^ "NTFS for Windows 98". Download.chip.eu. Retrieved 2013-02-05.
  153. ^ "OS/2 NTFS Driver". Hobbes.nmsu.edu. Retrieved 2013-02-05.
  154. ^ Tuxera NTFS for Windows CE. See "article". Archived from the original on 18 Sep 2012. and announcement.
  155. ^ a b c d Cross-platform Drive Solutions. "Sharing Disks - Windows Products". Macwindows.com. Retrieved 2013-02-05.
  156. ^ Gagne, Ken (2009-08-31). "Losing legacy data to Snow Leopard". Computerworld. Retrieved 2009-09-07.
  157. ^ "hfsutils at FreshPorts". Freshports.org. Retrieved 2013-02-05.
  158. ^ "hfs at FreshPorts". Freshports.org. Retrieved 2013-02-05.
  159. ^ "OS/2 HFS Driver". Hobbes.nmsu.edu. Retrieved 2013-02-05.
  160. ^ "Catacombae HFSExplorer". Hem.bredband.net. Retrieved 2013-02-05.
  161. ^ "DOS/Win 9x HPFS Driver". Hobbes.nmsu.edu. Retrieved 2013-02-05.
  162. ^ Win NT 4.0 HPFS Driver
  163. ^ "How to mount FFS partition under Linux - NetBSD Wiki". Wiki.netbsd.se. Archived from the original on March 19, 2008. Retrieved 2009-10-09.
  164. ^ a b c Ext2Fsd is an open source ext2/ext3/ext4 kernel-level file system driver for Windows systems (NT/2K/XP/VISTA/7, X86/AMD64) that provides both read/write access to the file system. Currently, does not fully support extents (no size truncating/extending, no file deletion), a default feature of ext4. [9]
  165. ^ a b Ext2 IFS for Windows provides kernel-level read/write access to ext2 and ext3 volumes in Windows NT4, 2000, XP, Vista and Windows 2008. Does not support inodes size above 128 bytes and does not support ext4.[10]
  166. ^ a b c Ext2Read is an explorer-like utility to explore ext2/ext3/ext4 file systems that provides read-only access to the file system. It supports extents, large inodes, and LVM2 volumes.Ext2Read
  167. ^ a b c Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[11]
  168. ^ a b c Paragon ExtFS for Mac is a low-level file system driver specially developed to bridge file system incompatibility between Linux and Mac by providing full read/write access to the Ext2, Ext3 and Ext4 file systems under Mac OS X.[12]
  169. ^ Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[13]
  170. ^ OS/2 ext2 Driver
  171. ^ a b c d e f See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
  172. ^ a b ext4fuse is a free software multi OS FUSE module to mount ext4 file system devices and/or images with read-only support. [14]
  173. ^ Native ZFS for Linux
  174. ^ ZFS on FUSE
  175. ^ Mac ZFS
  176. ^ http://wiki.lustre.org/index.php/Windows_Native_Client
  177. ^ http://wiki.lustre.org/index.php?title=Main_Page
  178. ^ http://wiki.lustre.org/index.php/FAQ_-_OS_Support
  179. ^ Using SAM-QFS on Linux Clients
  180. ^ ncpfs
  181. ^ "Understanding the difference between the Live File System and Mastered disc formats". Which CD or DVD format should I use?. Microsoft. Retrieved 2008-11-22.
  182. ^ [15]
  183. ^ vmfs
  184. ^ a b c AncientFS
  185. ^ a b VMS2Linux
  186. ^ logfs
Retrieved from "https://en.wikipedia.org/w/index.php?title=Comparison_of_file_systems&oldid=583187062"