You broke the rules. With our unique approach to crawling we index shared files withing hours after Upload. As an file sharing search engine DownloadJoy finds 2002 aventura we broke the rules nyxgzuck zip files matching your search criteria among the files that has been seen recently in uploading sites by our search spider. When you search for files (video, music, software, documents etc), you will always find high-quality 2002 aventura we broke the rules nyxgzuck zip files recently uploaded on DownloadJoy or other most popular shared hosts.

1. Hierarchical File Systems
2. Unix Hierarchical File System

Remo Recover (Windows) Pro is the best Windows hard. During file system. You have installed Remo Recover (Windows) Pro Edition software and then. Red Hat Enterprise Linux uses the Filesystem Hierarchy Standard (FHS) file system structure, which defines the names, locations, and permissions for many file types and directories. It needs to be safe from being overwritten when the system software is updated. Stack Exchange network consists of 174 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange.

Jump to navigationJump to search

Bat for lashes two suns 320 rar. The following tables compare general and technical information for a number of file systems.

• 4Features

General information[edit]

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 2	ICT (later ICL)	1968	George 2
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
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 MicroMOS
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	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, Windows via Samba
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

Limits[edit]

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[7]	?	?
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[8]	16 EiB[8]	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[8]	4 GiB[8]	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 ! @ # $ % ^ & ( ) + - = ~ ` ; ' ' , < > [ ] ( ) _[10]	?	?	?	?
APFS	255 UTF-8 characters	Unicode 9.0 encoded in UTF-8[11]	?	8 EiB	?	263[12]
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 Abc malayalam movie free download. In POSIX namespace: any UTF-16 code unit (case-sensitive) except / as well as NUL[13]	32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[f]	16 EiB[n]	16 EiB[n]	?
ReFS	255 UTF-16 characters[14]	Any Unicode except NUL, /[14]	32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[14]	16 EiB[14][15]	1 YiB[14]	?
HFS Plus	255 UTF-16 characters[o]	Any valid Unicode[e][p]	Unlimited	slightly less than 8 EiB	slightly less than 8 EiB[16][17]	?
FFS	255 bytes	Any byte except NUL[e]	No limit defined[f]	4 GiB	256 TiB	?
HAMMER	255 bytes[18]	Any byte except NUL[e]	?	?	1 EiB[19]	?
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[20]
UFS2	255 bytes	Any byte except NUL[e]	No limit defined[f]	512 GiB to 32 PiB	512 ZiB[21] (279 bytes)	Subdirectory per directory is 32,767[20]
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[22]	Any byte except NUL, /[e]	No limit defined[f]	16 GiB to 16 TiB[d][23]	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	?
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 ?[25]	?	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	?	?	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

Metadata[edit]

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[26]	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	Yes	Yes	Yes	No	No	No
RT-11[27]	No	No	Yes (date only)	No	No	No	No	No	No	Yes
Version 6 Unix file system (V6FS)[28]	Yes	Yes	No	Yes	No	No	No	No	No	No
Version 7 Unix file system (V7FS)[29]	Yes	Yes	No	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	No
ReFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes[am]	Yes[an]
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[ao]	Yes[ao]	No[ap]	No
UFS2	Yes	Yes	Yes	Yes	Yes	No	Yes[ao]	Yes[ao]	Yes	No
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[aq]	Yes[aq]	Yes	No
ext3	Yes	Yes	No	Yes	Yes	No	Yes[aq]	Yes[aq]	Yes	No
ext4	Yes	Yes	Yes	Yes	Yes	No	Yes[aq]	Yes[aq]	Yes	Partial[ar]
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[aq]	Yes[aq]	Yes	No
GPFS	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes
GFS	Yes	Yes	No	Yes	Yes	No	Yes[aq]	Yes[aq]	Yes	No
NILFS	Yes	Yes	Yes	No	Yes	No	No	No	No	Yes
ReiserFS	Yes	Yes	No	Yes	Yes	No	Yes[aq]	Yes[aq]	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[as]	Yes	Yes	No	Yes	Yes[aq]	Yes	Partial[at]
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[au]	Yes[au]	Yes	Yes[au]	Yes	?	Yes[av][aw]	No
NWFS	Yes	?	Yes[au]	Yes[au]	Yes	Yes[au]	Yes	?	Yes[av][aw]	No
ODS-5	Yes	Yes	Yes	?	?	Yes	Yes	?	Yes[ax]	No
APFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	?	Yes	Partial
VxFS	Yes	Yes	Yes	Yes	Yes	No	Yes	?	Yes[aq]	No
UDF	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	No
Fossil	Yes	Yes[ay]	No	Yes	Yes	No	No	No	No	No
ZFS	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes[az]	Yes[ba]	Yes
Btrfs	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes[bb]
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[bc]	Yes	No	No[bd]	No[be]	No[be]	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	Yes	Yes	Yes	No	Yes	No	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

Features[edit]

File capabilities[edit]

File system	Hard links	Symbolic links	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	Internal snapshotting / branching	XIP	Filesystem-level encryption	Data deduplication	Data checksums
DECtape	No	No	No	No	No	No	No	No	No	No	No	No
BeeGFS	Yes	Yes	Yes	Yes	Yes	Yes	No	No	No	No	Yes	No
Level-D	No	No	No	No	No	No	No	No	No	No	No	No
RT-11	No	No	No	No	No	No	No	No	No	No	No	No
APFS	Yes	Yes	?	?	Partial	Yes	?	Yes	?	Yes	Partial	No
Version 6 Unix file system (V6FS)	Yes	No	No	No	Yes	Yes	No	No	No	No	No	No
Version 7 Unix file system (V7FS)	Yes	No[bf]	No	No	Yes	Yes	No	No	No	No	No	No
FAT12	No	No	No	Partial (with TFAT12 only)	No	Partial (with VFAT LFNs only)	No	No	No	Partial (DR-DOS with SECURITY only)	No	No
FAT16 / FAT16B / FAT16X	No	No	No	Partial (with TFAT16 only)	No	Partial (with VFAT LFNs only)	No	No	No	Partial (DR-DOS with SECURITY only)	No	No
FAT32 / FAT32X	No	No	No?	Partial (with TFAT32 only)	No	Partial (with VFAT LFNs only)	No	No	No	No	No	No
GFS	Yes	Yes[bg]	Yes	Yes[bh]	Yes	Yes	No	No	No	No	?	No
HPFS	No	No	No	No	No	Yes	No	?	No	No	?	No
NTFS	Yes	Yes[bi]	No[bj]	Yes[bj] (2000)	Yes[bk]	Yes	Yes	Partial[bl]	?	Yes	Yes[bm][33]	No
HFS Plus	Yes[34]	Yes	No	Yes[bn]	Partial[bo]	Yes	Yes[bp]	No	No	No[bq]	No	No
FFS	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
UFS1	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
UFS2	Yes	Yes	No	Yes[br][39][bs]	Yes	Yes	No	Yes	?	No	No	No
HAMMER	Yes	Yes	Yes	Yes	Yes	Yes	?	Yes	No	No	Yes	Yes
LFS	Yes	Yes	Yes[bt]	No	Yes	Yes	No	Yes	No	No	No	No
ext	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
Xiafs	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
ext2	Yes	Yes	No	No	Yes	Yes	No	No	Yes[bu]	No	No	No
ext3	Yes	Yes	Yes (2001) [bv]	Yes (2001)	Yes	Yes	No	No	Yes	No	No	No
ext4	Yes	Yes	Yes[bv]	Yes	Yes	Yes	No	No	Yes	Yes, experimental [42]	No	No
NOVA	Yes	Yes	No	Yes	Yes	Yes	No	Yes	Yes	No	No	Yes
F2FS	Yes	Yes	Yes[bt]	No	Yes	Yes	No	No	No	Yes, experimental [43]	No	No
Lustre	Yes	Yes	Yes[bv]	Yes	Yes	Yes	No	No	No	No	No	No
NILFS	Yes	Yes	Yes[bt]	No	Yes	Yes	No	Yes	No	No	No	Yes
ReiserFS	Yes	Yes	Yes[bw]	Yes	Yes	Yes	No	No	?	No	No	No
Reiser4	Yes	Yes	Yes	No	Yes	Yes	No	?	?	Yes[bx]	?	No
OCFS	No	Yes	No	No	Yes	Yes	No	No	No	No	No	No
OCFS2	Yes	Yes	Yes	Yes	Yes	Yes	No	No	No	No	No	No
XFS	Yes	Yes	Yes	Yes	Yes[by]	Yes	Yes	No	?	No	Yes, experimental [44]	No
JFS	Yes	Yes	Yes	Yes (1990)	Yes[bz]	Yes	No	?	?	No	?	No
QFS	Yes	Yes	No	Yes	Yes	Yes	No	No	No	No	No	No
BFS	Yes	Yes	No	Yes	Yes	Yes	?	No	No	No	No	No
NSS	Yes	Yes	?	Yes	Yes[ca]	Yes[ca]	Yes[cb]	Yes	No	Yes	?	No
NWFS	Yes[cc]	Yes[cc]	No	No	Yes[ca]	Yes[ca]	Yes[cb]	?	No	No	?	No
ODS-2	Yes	Yes[cd]	No	Yes	No	No	Yes	Yes	No	No	No	No
ODS-5	Yes	Yes[cd]	No	Yes	No	Yes	Yes	Yes	?	No	No	No
UDF	Yes	Yes	Yes[bt]	Yes[bt]	Yes	Yes	No	No	Yes	No	No	No
VxFS	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes[ce]	?	No	Yes	No
Fossil	No	No	No	No	Yes	Yes	Yes	Yes	No	No	Yes	No
ZFS	Yes	Yes	Yes[cf]	No[cf]	Yes	Yes	No	Yes	No	Yes[cg]	Yes	Yes
Btrfs	Yes	Yes	Yes	Yes	Yes	Yes	?	Yes	?	No, planned, not being developed (Nov, 2015)[48]	Yes	Yes
Minix V1	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
Minix V2	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
Minix V3	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No	No
VMFS2	Yes	Yes	No	Yes	Yes	Yes	No	No	No	No	No	No
VMFS3	Yes	Yes	No	Yes	Yes	Yes	No	No	No	No	No	No
ReFS	No	Yes	?	?	Yes[bk]	Yes	?	?	?	No	Yes	Yes
ISO 9660	No	No	No	No	No	No	No	No	No	No	No[ch]	No
Rock Ridge	Yes	Yes	No	No	Yes	Yes	No	No	No	No	No[ch]	No
Joliet ('CDFS')	No	No	No	No	No	Yes	No	No	No	No	No[ch]	No
SquashFS	Yes	Yes	No	No	Yes	Yes	No	No	No	No	Yes	Yes
File system	Hard links	Symbolic links	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	Internal snapshotting / branching	XIP	Filesystem-level encryption	Data deduplication	Data checksums

Resize capabilities[edit]

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

Allocation and layout policies[edit]

File system	Tail packing	Transparent compression	Block suballocation	Allocate-on-flush	Extents	Variable file block size[ci]	Sparse files	Copy on write	Trim support
DECtape	No	No	No	No	No	No	No	No	No
BeeGFS	No	Yes	No	Yes	Yes	Yes	Yes	Yes	?
Level-D	No	No	No	No	Yes	No	No	No	?
APFS	?	No	?	Yes	Yes	?	Yes	Yes	Yes[61][62]
Version 6 Unix file system (V6FS)	No	No	No	No	No	No	Yes	?	No
Version 7 Unix file system (V7FS)	No	No	No	No	No	No	Yes	?	No
FAT12	No	Partial[cj]	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[63])	No	Partial (only inside of compressed volumes)[64]	No	Partial (only inside of compressed volumes)[65]	No	Yes (Linux)
FAT16 / FAT16B / FAT16X	No	Partial[cj]	Partial (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[63])	No	Partial (only inside of compressed volumes)[64]	No	Partial (only inside of compressed volumes)[65]	No	Yes (Linux)
FAT32 / FAT32X	No	No	No	No	No	No	No	No	Yes (Linux)
GFS	Partial[ck]	No	No	No	No	No	Yes	?	Yes
HPFS	No	No	No	No	Yes	No	No	?	No
NTFS	No	Yes	Partial	No	Yes	No	Yes	?	Yes (NT 6.1 + newer)
HFS Plus	No	No	No	No	Yes	No	No	?	Yes (macOS)
FFS	No	No	8:1[cl]	No	No	No	Yes	?	No
UFS1	No	No	8:1[cl]	No	No	No	Yes	?	No
UFS2	No	No	8:1[cl]	No	No	Yes	Yes	?	Yes[66][67]
LFS	No	No	8:1[cl]	No	No	No	Yes	Yes	?
ext	No	No	No	No	No	No	Yes	No	No
Xiafs	No	No	No	No	No	No	Yes	?	?
ext2	No	No[cm]	No[cn]	No	No	No	Yes	No	Yes
ext3	No	No	No[cn]	No	No	No	Yes	No	Yes
ext4	No	No	No[cn]	Yes	Yes	No	Yes	No	Yes
NOVA	No	No	No	No	Yes	No	Yes	Yes	?
F2FS	No	No	No	Yes	Partial[co]	No	Yes	Yes	Yes[68]
Lustre	No	No	No	Yes	Yes	No	Yes	?	?
NILFS	No	No	No	Yes	No	No	Yes	Yes	?
ReiserFS	Yes	No	Yes[cp]	No	No	No	Yes	?	?
Reiser4	Yes	Yes[bx]	Yes[cp]	Yes	Yes[cq]	No	Yes	?	?
OCFS	No	No	No	No	Yes	No	?	?	?
OCFS2	No	No	No	No	Yes	No	Yes	?	?
XFS	No	No	No	Yes	Yes	No	Yes	Yes, on request[69]	Yes (Linux)
JFS	No	only in JFS1 on AIX[70]	Yes	No	Yes	No	Yes	?	Yes (Linux)
QFS	No	No	Yes	No	No	No	?	?	?
BFS	No	No	No	No	Yes	No	?	?	Yes (Haiku)
NSS	No	Yes	No	No	Yes	No	?	?	?
NWFS	No	Yes	Yes[cr]	No	No	No	?	?	?
ODS-5	No	No	No	No	Yes	No	?	?	?
VxFS	No	No	?	No	Yes	No	Yes	?	?
UDF	No	No	No	?[cs]	Yes	No	No	?	No
Fossil	No	Yes	No	No	No	No	?	?	?
ZFS	No	Yes	Yes	Yes	No	Yes	Yes	Yes	Yes (FreeBSD, illumos)
Btrfs	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
VMFS2	No	No	Yes	No	No	No	Yes	?	?
VMFS3	No	No	Yes	No	No	No	Yes	?	?
ReFS	?	No	?	?	?	No	Yes	Yes	?
ISO 9660	No	No[ct]	No	No	Yes[cu]	No	No	No	No
Rock Ridge	No	No[ct]	No	No	Yes[cu]	No	No	No	No
Joliet ('CDFS')	No	No[ct]	No	No	Yes[cu]	No	No	No	No
SquashFS	No	Yes	No	No	No	No	Yes	No	No
File system	Tail packing	Transparent compression	Block suballocation	Allocate-on-flush	Extents	Variable file block size[ci]	Sparse files	Copy on write	Trim support

OS support[edit]

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[71] or linux-apfs[72])	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	?	?	?	?
Version 7 Unix file system (V7FS)	No	No	No	Yes	No	?	No	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 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+ [73]	Yes	Yes	Yes	No	?	Yes	No	?	No
Apple HFS Plus	No	No	Yes with Paragon HFS+ [73]	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 [74][75]	No	No	No	No	No	No	No	No
ext2	No	No	Yes with Paragon ExtFS [76] or partial with Ext2 IFS[77] or ext2fsd[78]	Yes	No	Yes with Paragon ExtFS [79] or ext2fsx	Yes	No	Yes	?	?	?
ext3	No	No	Yes with Paragon ExtFS [76] or partial with Ext2 IFS[77] or ext2fsd[78]	Yes	Partial (read only)[citation needed]	Yes with Paragon ExtFS [79] or partial with ext2fsx (journal not updated on writing)	Partial (read-only)[80][81]	No	with addon	?	Yes	?
ext4	No	No	Yes with Paragon ExtFS [76] or partial with Ext2 IFS[77] or ext2fsd[78]	Yes	?	Yes with Paragon ExtFS [79]	Partial support in kernel since version 10.1 (read-only)[80][81]	No	with addon	?	?	?
NOVA	No	No	No	Yes	No	No	No	No	No	No	No	No
Lustre	No	No	No	Yes[82]	?	?	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	?	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[83]	?	?	No	No	?	?	Yes	?
Be File System	No	No	No	Partial - read-only	?	?	No	No	Yes	?	?	?
NSS	No	No	No	Yes via EVMS[cv]	?	?	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[cw]	No	Yes[cw]	Yes[cw]	No	No	No	Yes[cw]	?
ZFS	No	No	No	Yes with FUSE[84] or as an external kernel module[85]	?	Yes with Read/Write Developer Preview[86]	Yes	?	?	?	Yes	?
Btrfs	No	No	Partial with WinBtrfs[87]	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.[88][89])	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 also[edit]

Notes[edit]

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. ^ ^abcdeThese 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-2Unicode 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. ^ ^abcdeFor 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. ^ ^{abcdefghijklmnopqrstuvwxyzaaabacadaeafagahaiajak}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. ^ ^{abcdefghijklmnopqrstuvwxyzaaabacadaeafagahaiajakalam}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. Linux has a pathname limit of 4,096.
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. ^ ^abcdefDepends on whether the FAT12, FAT16, and FAT32implementation 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. ^ ^abOn-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.^[9]
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. ^ ^abThis 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. ^ ^abDepends 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'^[24]
19. ^Note that the filename can be much longer XFS#Extended attributes
20. ^ ^abXFS 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. ^ ^abQFS 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. ^ ^abNSS 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. ^ ^abSparse files can be larger than the file system size, even though they can't contain more data.
29. ^ ^abMaximum 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.^[30]
39. ^Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS
40. ^Data checksums not enabled by default
41. ^ ^abcdAccess-control lists and MAC labels are layered on top of extended attributes.
42. ^Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
43. ^ ^{abcdefghijklmn}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.
44. ^ Journal and metadata only^[31]
45. ^Creation time stored since June 2015, xfsprogs version 3.2.3
46. ^Metadata checksums stored since June 2015, xfsprogs version 3.2.3
47. ^ ^abcdefThe local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
48. ^ ^abNovell 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.
49. ^ ^abSome 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.
50. ^Record Management Services (RMS) attributes include record type and size, among many others.
51. ^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.
52. ^Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.
53. ^Solaris 'extended attributes' are really full-blown alternate data streams, in both the Solaris UFS and ZFS.
54. ^ disabling copy-on-write (COW) to prevent fragmentation also disables checksumming
55. ^Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.
56. ^libburnia can backup and restore ACLs with file system creation and extraction programs, but no kernel support exists.
57. ^ ^ablibburnia can backup and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.
58. ^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.
59. ^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
60. ^Optional journaling of data
61. ^As of Windows Vista, NTFS fully supports symbolic links.^[32] 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.
62. ^ ^abNTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
63. ^ ^abWhile 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.
64. ^NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
65. ^Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.
66. ^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.
67. ^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.^[35] 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.^[36][37]
68. ^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).^[38]
69. ^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.
70. ^'Soft dependencies' (softdep) in NetBSD, called 'soft updates' in FreeBSD provide meta-data consistency at all times without double writes (journaling)
71. ^Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE ^[40][41]
72. ^ ^abcdeUDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
73. ^Linux kernel versions 2.6.12 and newer.
74. ^ ^abcOff by default.
75. ^Full block journaling for ReiserFS was added to Linux 2.6.8.
76. ^ ^abReiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
77. ^Optionally no on IRIX.
78. ^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.
79. ^ ^abcdCase-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.
80. ^ ^abThe 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.^[45]
81. ^ ^abAvailable only in the 'NFS' namespace.
82. ^ ^abThese are referred to as 'aliases'.
83. ^VxFS provides an optional feature called 'Storage Checkpoints' which allows for advanced file system snapshots.
84. ^ ^abZFS 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.
85. ^Applies only to proprietary ZFS release and ZFS On Linux. Encryption support is not yet available in whole OpenZFS.^[46][47]
86. ^ ^abcSome 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. ^ ^abVariable 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. ^ ^abSuperStor in DR DOS 6.0, PalmDOS 1.0, PC DOS 6.1 and 6.3, Stacker in Novell DOS 7, OpenDOS 7.01, DR-DOS 7.02 (and higher), and PC DOS 7.0 (and higher), DoubleSpace in MS-DOS 6.0 and 6.20, and DriveSpace in MS-DOS 6.22 and Windows 95, 98 and Me are disk compression schemes for FAT, but are not supported for other operating systems.
89. ^Only for 'stuffed' inodes
90. ^ ^abcdOther block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
91. ^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.
92. ^ ^abcFragments were planned, but never actually implemented on ext2 and ext3.
93. ^ Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.
94. ^ ^abTail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.
95. ^In 'extents' mode.
96. ^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.
97. ^Depends on UDF implementation.
98. ^ ^abcLinux supports the zisofs extension that allows per-file compression, and file system creation tools may support creating such images. zisofs images are incompatible on non-Linux OSes.
99. ^ ^abcISO 9660 Level 3 only
100. ^Supported using only EVMS; not currently supported using LVM
101. ^ ^abcdProvided in Plan 9 from User Space

References[edit]

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.
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. ^'SFS file system'. IBM Knowledge Center.
8. ^ ^abcd'File System Functionality Comparison'. Microsoft Developer Network. Microsoft. Retrieved 4 November 2017.
9. ^'Limitations of the FAT32 File System in Windows XP'. Microsoft.
10. ^'GEMDOS Overview'.
11. ^https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html
12. ^https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/VolumeFormatComparison/VolumeFormatComparison.html
13. ^http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf
14. ^ ^abcdeSteven Sinofsky (January 16, 2012). 'Building the next generation file system for Windows: ReFS'.
15. ^'Resilient File System (ReFS) overview'. docs.microsoft.com. Retrieved 2017-11-07.
16. ^'Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits'. support.apple.com. July 26, 2016.
17. ^'Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits'. support.apple.com. February 20, 2012.
18. ^Matthew Dillon. 'HAMMER2 Design Document'.
19. ^Matthew Dillon (June 21, 2008). 'The HAMMER Filesystem'(PDF).
20. ^ ^ab'Maximum Number of UFS Subdirectories'. Oracle. Retrieved 2019-02-12.
21. ^'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.
22. ^Vimal A.R (16 July 2016). 'Max file-name length in an EXT4 file system'. arvimal.blog.
23. ^'Interviews/EricSandeen'. Fedora Project Wiki. 9 June 2008.
24. ^'FAQ'. namesys. 15 October 2003. Archived from the original on 19 July 2006.
25. ^'Joliet Specification'. 22 May 1995. Archived from the original on 14 April 2009.
26. ^'RT–11 Volume and File Formats Manual'(PDF). Digital Equipment Corporation. August 1991. p. 1-26 . 1-32.
27. ^'RT–11 Volume and File Formats Manual'(PDF). Digital Equipment Corporation. August 1991. p. 1-4 . 1-12.
28. ^'Format of the Unix 6 file system'(PDF). Retrieved 2016-02-21.
29. ^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.
30. ^'Mandatory Integrity Control'. Microsoft Developer Network.
31. ^'Ext4 Metadata Checksums - Ext4'. ext4.wiki.kernel.org.
32. ^Mark Russinovich (February 2007). 'Windows Administration: Inside the Windows Vista Kernel: Part 1'. TechNet.
33. ^'About Data Deduplication'.
34. ^Siracusa, John. '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.
35. ^newfs_hfs(8) – Darwin and macOS System Manager's Manual
36. ^'File System Comparisons'. Apple. (hasn't been updated to discuss HFSX)
37. ^'Technical Note TN1150: HFS Plus Volume Format'. Apple. (Very technical overview of HFS Plus and HFSX.)
38. ^fslogger
39. ^https://www.mckusick.com/softdep/suj.pdf
40. ^https://wiki.freebsd.org/NewFAQs
41. ^https://www.freebsd.org/releases/9.0R/announce.html
42. ^'Ext4 encryption'.
43. ^'F2FS encryption'.
44. ^'XFS, Reflinks and Deduplication'.
45. ^Filesystem Events tracked by NSure
46. ^'How to Manage ZFS Data Encryption'.
47. ^https://github.com/zfsonlinux/zfs/pull/5769
48. ^'Btrfs FAQ'. Btrfs Wiki.
49. ^'Just Enough Operating System (JeOS): Technical Information SUSE'. www.suse.com. Retrieved 28 April 2018.
50. ^ ^abcresize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands
51. ^ ^abcdWith software based on GNU Parted
52. ^https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/
53. ^'IBM's Journaled File System (JFS) for Linux'.
54. ^'Frequently Asked Questions (Old Wiki)'. Retrieved 5 May 2018.
55. ^'nilfs-resize(8)'.
56. ^'ntfsresize(8)'.
57. ^'Resize reiserfs'. Reiserfs wiki.
58. ^'Resizing File Systems'.
59. ^'Growing an XFS File System'.
60. ^'Resizing and Growing Disks'.
61. ^'Mac users, meet APFS: macOS's new file system - ZDNet'.
62. ^'Apple File System Guide - FAQ'.
63. ^ ^ab'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.
64. ^ ^ab'Mapping DOS FAT to MDFAT'.
65. ^ ^ab'CVF Region: MDFAT'.
66. ^https://svnweb.freebsd.org/base?view=revision&revision=216796
67. ^https://www.freebsd.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+8.4-RELEASE
68. ^Jaeguk Kim (2014-09-22). 'F2FS: Introduce FITRIM in f2fs_ioctl'.
69. ^'XFS Adds Shared Data Extents For Linux 4.9'.
70. ^'AIX documentation: JFS data compression'. IBM.
71. ^https://github.com/sgan81/apfs-fuse
72. ^https://github.com/eafer/linux-apfs
73. ^ ^ab'Paragon HFS+ for Windows 10'.
74. ^'Porting an Ancient Filesystem to Modern Linux'. Time To Pull The Plug.
75. ^'A port of the xiafs filesystem to modern Linux kernels'. Github (cdtk).
76. ^ ^abc'Paragon ExtFS for Windows'.
77. ^ ^abc'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.)
78. ^ ^abcBranten, Bo. 'Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)'.
79. ^ ^abc'Paragon ExtFS for Mac'.
80. ^ ^ab'FreeBSD Handbook'.
81. ^ ^ab'Debian GNU/kFreeBSD'.
82. ^'Lustre Wiki'.
83. ^'About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide'. Retrieved 2016-03-14.
84. ^'ZFS Filesystem for FUSE/Linux'. Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013.
85. ^'ZFS on Linux'. Lawrence Livermore National Laboratory.
86. ^Kim, Arnold (4 October 2007). 'Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard'. Mac Rumors.
87. ^'WinBtrfs'. Github (maharmstone).
88. ^'squashfs-tools'. Freshports.
89. ^'fusefs-squashfuse'. Freshports.

• Linux kernel file systems via Wikia:en.howto:Wikihowto

External links[edit]

• A speed comparison of filesystems on Linux 2.4.5 (archived)
• Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (April 23, 2006)

Hierarchical File Systems

I agree. Maybe we need a hierarchical system that is dynamic. We need to organize information and in the real world we are constrained, but with computers we are not.

E.g if I need to organize my books, I could move it only to a given position, not another one, I could add labels to my books like 'history', or 'Initials of the author', but I could only group one way, like all my science papers on one place, if I want to group all the books that talk about sex, or crime, I will have to destroy the other group.

With computers you could create multiple directories trees with links instead of data, so I don't need to multiply the data each new tree. The tech is there(inodes).

Unix Hierarchical File System

Imagine if you study countries according to their population, so you create a hierarchy 'most populated', 'less populated', 'no populated at all', then inside most populated you have 'the most populated', 'the less populated', and so on.

Then you could have another directory according to the extension in squared kilometers. Another according to their capital coordinates, and so on.