文件系统的对比

下列表格对比了一系列文件系统的一般和技术资料，文件系统的具体信息参见链接文章。

一般资料

文件系统	开发者	发布年份	原操作系统	许可
DECtape	DEC	1964	PDP-6 Monitor
Level-D	DEC	1968	TOPS-10
George3	ICT (即之后的 ICL)	1968	George 3
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	蓋瑞·基爾多	1974	CP/M
V6FS	Bell Labs	1975	Version 6 Unix
OS4000	GEC	1977	OS4000
FAT (8-bit)	Marc McDonald, Microsoft	1977	Microsoft Standalone Disk BASIC-80
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
DOS 1.0	Atari Corporation	1979	Atari 8-bit family
ODS-2	DEC	1979	OpenVMS
FAT12	Tim Paterson, Seattle Computer Products	1980	QDOS, 86-DOS
DOMAIN file system	Apollo Computer	1981	Domain/OS (Aegis, Domain)
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, IBM	1984	PC DOS 3.0/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[12]	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	为 Unix System Laboratories、HP-UX[2] 开发
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[3]	Digital Unix
NTFS Version 1.0	Microsoft, Tom Miller, Gary Kimura	1993	Windows NT 3.1	proprietary
LFS	Margo Seltzer	1993	Berkeley Sprite
ext2	Rémy Card	1993	Linux, Hurd
UFS1	Kirk McKusick	1994	4.4BSD
XFS	SGI	1994	IRIX
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[4]
QFS	LSC Inc, Sun Microsystems	1996	Solaris
IBM Spectrum Scale	IBM	1998	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	proprietary
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, 4th Edition	LPL
Google File System	Google	2003	Linux
PramFS	MontaVista	2003	Linux
Reliance[5]	Datalight	2003	Windows CE, VxWorks, custom ports
VxCFS	VERITAS, (now Symantec)	2004	AIX, HP-UX, Solaris, Linux
ZFS	Sun Microsystems	2004	Solaris	CDDL
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
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	proprietary
TexFAT/TFAT	Microsoft	2006	Windows CE 6.0
Btrfs	Oracle Corporation	2007	Linux	GPL
Ceph	Sage Weil, Inktank Storage, Red Hat	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[5]	Datalight	2009	Windows CE, Windows Mobile, VxWorks, Linux, custom ports	proprietary
LTFS	IBM	2010	Linux, Mac OS X, planned Microsoft Windows,	LGPL
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	proprietary
Lanyard Filesystem	Dan Luedtke	2012	Linux
F2FS	Samsung	2012	Linux	GPLv2
File system	Creator	Year introduced	Original operating system	License

限制

文件系统	最大文件名称长度	路径字符限制[6]	最大路径名长度	最大文件大小	最大卷大小[7]
Acorn ADFS	10 bytes	Any ISO 8859-1 character except: SPACE $ & % @ \ ^ : . # * " ¦	No limit defined	7009409600000000000♠512 MB or 7010320000000000000♠4 GB[8]	7009409600000000000♠512 MB or 7010320000000000000♠4 GB[9]
AdvFS	226 characters	Any byte except NUL[10]	No limit defined[11]	7014128000000000000♠16 TB	7014128000000000000♠16 TB
Apple DOS 3.x	30 bytes	Any byte except NUL	7001300000000000000♠30 B, no subdirectories (105 files per disk)	未知	7006112000000000000♠140 kB DOS 3.3 (assuming standard 35 tracks) 7005910000000000000♠113.75 kB DOS 3.1, 3.2
Apple ProDOS	15 bytes	A-Z, a-z, 0-9, and period	64 B, including slashes[12][13]	7008128000000000000♠16 MB	7008256000000000000♠32 MB
BFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7012208000000000000♠260 GB[14]	7000200000000000000♠2 EB
Btrfs	255 bytes	Any byte except NUL	未知	7001160000000000000♠16 EB	7001160000000000000♠16 EB
CBM DOS	16 bytes	Any byte except NUL	Non-hierarchical	7008128000000000000♠16 MB	7008128000000000000♠16 MB
CP/M file system	8.3	any byte except: SPACE < > . , ; : = ? * [ ] % | ( ) / \[15]	16 "user areas", no subdirectories	7007640000000000000♠8 MB[16]	7007640000000000000♠8 MB to 512 MB[16]
DECtape	6.3	A–Z, 0–9	DTxN:FILNAM.EXT = 15	7005369280000000000♠369280 B (577 * 640)	7005369920000000000♠369920 B (578 * 640)
DOS (GEC)	8 bytes	A–Z, 0–9	Non-hierarchical	7008512000000000000♠64 MB	7008512000000000000♠64 MB
Elektronika BK tape format	16 bytes	未知	Non-hierarchical	7005512000000000000♠64 kB	7006640000000000000♠800 kB (approx) per side for 90 min cassette (limited only by tape length)
exFAT	255 characters[17]	Any Unicode except NUL	No limit defined	7002127000000000000♠127 PB	7001640000000000000♠64 ZB, 512 TB recommended[18]
ext2	255 bytes	Any byte except NUL[10] and /	No limit defined[11]	7013160000000000000♠2 TB[7]	7014256000000000000♠32 TB
ext3	255 bytes	Any byte except NUL[10] and /	No limit defined[11]	7013160000000000000♠2 TB[7]	7014256000000000000♠32 TB
ext3cow	255 bytes	Any byte except NUL,[10] / and @	No limit defined[11]	7013160000000000000♠2 TB[7]	7014256000000000000♠32 TB
ext4	255 bytes	Any byte except NUL[10] and /	No limit defined[11]	7014128000000000000♠16 TB[7][19]	7000100000000000000♠1 EB[20]
TexFAT	247 characters	Any Unicode except NUL	No limit defined	7010160000000000000♠2 GB	7012400000000000000♠500 GB Tested[21]
F2FS	255 bytes	未知	未知	7013315200000000000♠3.94 TB	7014128000000000000♠16 TB
FAT12	8.3 (255 UCS-2 code units with VFAT LFNs)[22]	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[10][22]	No limit defined[11]	7008256000000000000♠32 MB (7009204800000000000♠256 MB)	7008256000000000000♠32 MB (7009204800000000000♠256 MB with 4K sectors and 64 KB clusters)
FAT16	8.3 (255 UCS-2 code units with VFAT LFNs)[22]	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[10][22]	No limit defined[11]	7010160000000000000♠2 GB (7010320000000000000♠4 GB with LFS)	7010160000000000000♠2 GB or 4 GB
FAT32	8.3 (255 UCS-2 code units with VFAT LFNs)[22]	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[10][22]	No limit defined[11]	7010160000000000000♠2 GB (7010320000000000000♠4 GB with LFS)	7013160000000000000♠2 TB[23] (7014128000000000000♠16 TB)
FATX	42 bytes[22]	ASCII. Unicode not permitted.	No limit defined[11]	7010160000000000000♠2 GB	7010160000000000000♠2 GB
FFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7000800000000000000♠8 ZB	7000800000000000000♠8 ZB
Fossil	65535 bytes of UTF-8 characters	Any Unicode except 0-31	No limit defined	8 EB	未知
GFS	255	Any byte except NUL[10]	No limit defined[11]	7000800000000000000♠8 EB[24]	7000800000000000000♠8 EB[24]
IBM Spectrum Scale	255 UTF-8 codepoints	Any byte except NUL[10] and /	No limit defined[11]	7000800000000000000♠8 EB	7000800000000000000♠8 YB (18 PB tested)
HAMMER	未知	未知	未知	未知	7000100000000000000♠1 EB
HFS	31 bytes	Any byte except :[25]	Unlimited	7010160000000000000♠2 GB	7013160000000000000♠2 TB
HFS Plus	255 UTF-16 code units[26]	Any valid Unicode[10][27]	Unlimited	7000800000000000000♠8 EB	7000800000000000000♠8 EB[28][29]
High Sierra	未知	未知	未知	未知	未知|-
HPFS	255 bytes	Any byte except NUL[30]	No limit defined[11]	7010160000000000000♠2 GB	7013160000000000000♠2 TB[31]
ISO 9660:1988	Level 1: 8.3, Level 2 & 3: ~ 180	Depends on Level[32]	~ 180 bytes?	7010320000000000000♠4 GB (Level 1 & 2) to 8 TB (Level 3)[33]	7013640000000000000♠8 TB[34]
ISO 9660:1999	未知 (207?)	未知	未知	未知	未知	未知
Joliet ("CDFS")	64 Unicode characters	All UCS-2 code except * / \ : ; and ?[35]	未知	7010320000000000000♠4 GB (same as ISO 9660:1988)	7013640000000000000♠8 TB (same as ISO 9660:1988)
Lanyard Filesystem	255 bytes	Any byte except NUL and /[10]	No limit defined	7001640000000000000♠64 ZB	7006102400000000000♠128 kB to 7001640000000000000♠64 ZB[36]
LEAN	4,068 bytes[37]	case sensitive, in UTF-8 (any Unicode codepoint)	No limit defined	7000800000000000000♠8 EB	7000800000000000000♠8 EB
Level-D	6.3	A–Z, 0–9	DEVICE:FILNAM.EXT[PROJECT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67	7011192000000000000♠24 GB (34,359,738,368 words (235-1); 206,158,430,208 SIXBIT bytes)	7010960000000000000♠12 GB (approx; 64 * 178 MB)
LTFS	未知	未知	未知	未知	未知
Lustre	255 bytes	Any byte except NUL[10] and /	No limit defined[11]	7001320000000000000♠32 PB (on ext4)	7000100000000000000♠1 YB (55 PB tested)
JFS1	255 bytes	Any byte except NUL[10]	No limit defined[11]	7000800000000000000♠8 EB	7000400000000000000♠4 PB
JFS	255 bytes	Any Unicode except NUL	No limit defined[11]	7000400000000000000♠4 PB	7001320000000000000♠32 PB
MFS	255 bytes	Any byte except :	No path (flat filesystem)	7009180800000000000♠226 MB	7009180800000000000♠226 MB
MicroDOS file system	14 bytes	未知	未知	7008128000000000000♠16 MB	7008256000000000000♠32 MB
MINIX V1 FS	14 or 30 bytes, set at filesystem creation time	Any byte except NUL[10]	No limit defined[11]	7008512000000000000♠64 MB[38]	7008512000000000000♠64 MB[38]
MINIX V2 FS	14 or 30 bytes, set at filesystem creation time	Any byte except NUL[10]	No limit defined[11]	7010320000000000000♠4 GB[38]	7009800000000000000♠1 GB, then 2 TB[38]
MINIX V3 FS	60 bytes	Any byte except NUL[10]	No limit defined[11]	7010320000000000000♠4 GB	7014128000000000000♠16 TB[38]
NILFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7000800000000000000♠8 EB	7000800000000000000♠8 EB
NSS	226 characters	Depends on namespace used[39]	Only limited by client	7013640000000000000♠8 TB	7013640000000000000♠8 TB
NTFS	255 characters[40][41][42]	Depends on namespace used[40][41][42][43]	32,767 Unicode characters with each path component (directory or filename) commonly up to 255 characters long[11]	7001160000000000000♠16 EB[44]	7001160000000000000♠16 EB[44]
NWFS	80 bytes[45]	Depends on namespace used[39]	No limit defined[11]	7010320000000000000♠4 GB	7012800000000000000♠1 TB
OCFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7013640000000000000♠8 TB	7013640000000000000♠8 TB
OCFS2	255 bytes	Any byte except NUL[10]	No limit defined[11]	7000400000000000000♠4 PB	7000400000000000000♠4 PB
ODS-5	236 bytes[46]	未知	4,096 bytes[47]	7013160000000000000♠2 TB	7013160000000000000♠2 TB
OS4000	8 bytes	A–Z, 0–9 Period is directory separator	No limit defined[11]	7010160000000000000♠2 GB	7009800000000000000♠1 GB (at least)
PramFS	31 bytes	Any byte except NUL	未知	7009800000000000000♠1 GB	7000800000000000000♠8 EB
QFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7001160000000000000♠16 EB[48]	7000400000000000000♠4 PB[48]
ReFS	32,767 Unicode characters (255 Unicode characters in Windows 8/8.1)[49]	未知	32,767 Unicode characters in each path component	7001160000000000000♠16 EB	7000100000000000000♠1 YB with 64 kB cluster size (264 × 64 × 210). Windows stack addressing allows 16 EB
ReiserFS	4,032 bytes/226 characters	Any byte except NUL[10]	No limit defined[11]	7013640000000000000♠8 TB[50] (v3.6), 2 GB (v3.5)	7014128000000000000♠16 TB
Reiser4	3,976 bytes	Any byte except / and NUL	No limit defined[11]	7013640000000000000♠8 TB on x86	未知
Reliance	260 bytes	OS specific	7002260000000000000♠260 B	7010320000000000000♠4 GB	7013160000000000000♠2 TB
Reliance Nitro	1,024 bytes	OS specific	1024 bytes	7014256000000000000♠32 TB	7014256000000000000♠32 TB
RT-11	6.3	A–Z, 0–9, $	Non-hierarchical	7008256000000000000♠32 MB (65536 * 512)	7008256000000000000♠32 MB
IBM SFS	8.8	未知	Non-hierarchical[51]	未知	未知
UDF	255 bytes	Any Unicode except NUL	1,023 bytes[52]	7001160000000000000♠16 EB	7013160000000000000♠2 TB (hard disk), 8 TB (optical disc)[53][54]
UFS1	255 bytes	Any byte except NUL[10]	No limit defined[11]	7015180800000000000♠226 TB	7015180800000000000♠226 TB
UFS2	255 bytes	Any byte except NUL[10]	No limit defined[11]	7001320000000000000♠32 PB	7000100000000000000♠1 YB
V6FS	14 bytes[55]	Any byte except NUL and /[10]	No limit defined[11]	7008128000000000000♠16 MB[56]	7013160000000000000♠2 TB
V7FS	14 bytes[57]	Any byte except NUL and /[10]	No limit defined[11]	7009800000000000000♠1 GB[58]	7013160000000000000♠2 TB
VxFS	255 bytes	Any byte except NUL[10]	No limit defined[11]	7015204800000000000♠256 TB	7015204800000000000♠256 TB
VMFS2	128	Any byte except NUL and /[10]	2,048	7013320000000000000♠4 TB[59]	7014512000000000000♠64 TB
VMFS3	128	Any byte except NUL and /[10]	2,048	7013160000000000000♠2 TB[59]	7014512000000000000♠64 TB
XFS	255 bytes[60]	Any byte except NUL[10]	No limit defined[11]	7000800000000000000♠8 EB[61]	7000800000000000000♠8 EB[61]
ZFS	255 bytes	Any Unicode except NUL	No limit defined[11]	7001160000000000000♠16 EB	7002256000000000000♠256 ZB
File system	Maximum filename length	Allowable characters in directory entries[6]	Maximum pathname length	Maximum file size	Maximum volume size[7]

元数据

文件系统	存储文件所有者	POSIX 文件权限	创建时间戳	上次访问/读取时间戳	上次修改时间戳	Disk copy created	上次元数据更改时间戳	上次存档时间戳	访问控制表	安全/MAC 标签	Extended attributes/ Alternate data streams/ forks	元数据校验和/ECC	最大时间戳分辨率
AdvFS	是	是	否	是	是	未知	是	否	是	否	是	否	未知
Be File System	是	是	是	否	未知	未知	否	否	否	否	是	否	未知
Btrfs	是	是	是	是	是	未知	是	未知	是	是	是	是	1 nanosecond
CBM DOS	否	否	否	否	否	否	否	否	否	否	否	否	未知
CP/M file system	否	否	是[62]	否	未知	未知	否	否	否	否	否	否	未知
DECtape	否	否	是	否	未知	未知	否	否	否	否	否	否	未知
DOS (GEC)	是	否	是	是	是	未知	否	否	否	否	否	否	未知
Elektronika BK tape format	否	否	否	否	未知	未知	否	否	否	否	否	是	未知
ext2	是	是	否	是	是	未知	是	否	是[63]	是[63]	是	否	1 second
ext3	是	是	否	是	是	否	是	否	是[63]	是[63]	是	否	1 second
ext3cow	是	是	否	是	是	否	是	否	是[63]	是[63]	是	否	1 second
ext4	是	是	是	是	是	未知	是	否	是[63]	是[63]	是	部份[64]	1 nanosecond
exFAT	否	否	是	是	是	否	未知	否	否	未知	未知	部份	10 milliseconds
FAT12	否[65]	否[66]	部份[67]	部份[67]	是	是	否[68]	否	否	否	否[69]	否	10 milliseconds
FAT16	否[65]	否[66]	部份[67]	部份[67]	是	是	否[68]	否	否	否	否[69]	否	10 milliseconds
FAT32	否	否	部份[67]	部份[67]	是	是	否[68]	否	否	否	否	否	10 milliseconds
FFS	是	是	否	是	是	未知	是	否	否	否	否	否	未知
Fossil	是	是[70]	否	是	是	未知	是	否	否	否	否	否	1 second
GPFS	是	是	是	是	是	未知	是	否	是	是	是	是	1 nanosecond
GFS	是	是	否	是	未知	未知	是	否	是[63]	是[63]	是	否	未知
HFS	否	否	是	否	是	否	否	是	否	否	是	否	未知
HFS Plus	是	是	是	是	是	否	是	是	是	是[71]	是	否	1 second
HPFS	是[72]	否	是	是	是	未知	否	否	否	未知	是	否	未知
High Sierra	否	否	是	否	未知	未知	否	否	否	否	否	否	未知
ISO 9660:1988	否	否	是[73]	否[74]	是[75]	未知	否	否	否	否	否	否	未知
ISO 9660:1999	否	否	是	否	未知	未知	否	否	否	否	否	否	未知
JFS	是	是	是	是	是	未知	是	否	是	是	是	否	1 second
Joliet ("CDFS")	否	否	是[73]	否[74]	是[75]	未知	否	否	否	否	否	否	未知
Lanyard Filesystem	否	否	是	否	是	否	是	否	否	否	否	否	1 nanosecond
Level-D	是	是	是	是	未知	未知	是	是	是	否	否	否	未知
LFS	是	是	否	是	是	未知	是	否	否	否	否	否	未知
Lustre	是	是	部份[76]	是	是	否	是	否	是	是	是	部份[77][78]	未知
NILFS	是	是	是	否	未知	未知	是	否	Planned	否	Planned	是	未知
NTFS	是	是[79]	是	是	是	否	是	否	是	是[80]	是	否	100 nanoseconds
NSS	是	是	是[81]	是[81]	未知	未知	是	是[81]	是	未知	是[82][83]	否	未知
NWFS	是	未知	是[81]	是[81]	未知	未知	是	是[81]	是	未知	是[82][83]	否	未知
OCFS	否	是	否	否	未知	未知	是	是	否	否	否	否	未知
OCFS2	是	是	否	是	未知	未知	是	否	是	否	是	部份[84]	未知
ODS-5	是	是	是	未知	未知	未知	未知	是	是	未知	是[85]	否	未知
OS4000	是	否	是	是	是	未知	否	否	否	否	否	否	未知
PramFS	是	是	否	是	是	未知	是	否	是	是	是	是	1 second
QFS	是	是	是	是	未知	未知	是	是	是	否	是	否	未知
ReiserFS	是	是	否	是	是	否	否	否	否	否	否	否	未知
Reiser4	是	是	否	是	是	未知	是	否	否	否	否	否	未知
Reliance	否	否	是	否	是	否	否	否	否	否	否	部份[86]	未知
Reliance Nitro	Linux port	Linux port	是	是	是	否	否	否	Linux port	否	是	部份[86]	未知
UDF	是	是	是	是	未知	未知	是	是	是	否	是	否	未知
UFS1	是	是	否	是	是	未知	是	否	是[87]	是[87]	否[88]	否	未知
UFS2	是	是	是	是	是	未知	是	否	是[87]	是[87]	是	否	未知
V6FS	是	是	否	是	是	未知	是	否	否	否	否	否	未知
V7FS	是	是	否	是	是	未知	是	否	否	否	否	否	未知
VMFS2	是	是	否	是	未知	未知	是	否	否	否	否	否	未知
VMFS3	是	是	否	是	未知	未知	是	否	否	否	否	否	未知
VxFS	是	是	是	是	是	未知	是	否	是	未知	是[63]	否	未知
XFS	是	是	否	是	是	未知	是	否	是	是[63]	是	部份	1 nanosecond
ZFS	是	是	是	是	是	未知	是	是	是	是[89]	是[90]	是	1 nanosecond
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 Resolution

特点

文件系统	硬链接	符号链接	Block journaling	Metadata-only journaling	大小写敏感	保留大小写	文件更改日志	Snapshot	XIP	文件系统加密（英语：Filesystem-level_encryption）	写时复制	Integrated LVM	Data deduplication	卷可调整大小
Be File System	否	是	否	是	是	是	未知	否	否	否	否	否	否	未知
Btrfs	是	是	否	否	是	是	是	是	否	Planned[91]	是	是	是 (via bedup)[92]	Online
CBM DOS	否	否	否	否	是	是	否	否	否	否	否	否	否	否
CP/M file system	否	否	否	否	否	否	否	否	否	否	否	否	否	未知
DECtape	否	否	否	否	否	否	否	否	否	否	否	否	否	未知
DOS (GEC)	否	否	否	否	否	否	否	否	否	否	否	否	否	未知
ext2	是	是	否	否	是	是	否	否	是[93]	否	否	否	否	Offline[94]
ext3	是	是	是[95]	是	是	是	否	否	是	是[來源請求]	否	否	否	Online (can only be shrunk offline)[94]
ext3cow	是	是	是[95]	是	是	是	未知	是	未知	是	是	否	否	未知
ext4	是	是	是[95]	是	是	是	否	否	是	是[來源請求]	否	否	否	Online (can only be shrunk offline)[94]
exFAT	否	否	否	否	否	是	否	未知	未知	否	未知	未知	未知	未知
FAT12	否	否	否	否	否	部份	否	否	否	否	否	否	否	Offline[96]
FAT16	否	否	否	否	否	部份	否	否	否	否	否	否	否	Offline[96]
FAT32	否	否	否	否	否	部份	否	否	否	否	否	否	否	Offline[96]
FFS	是	是	否	否[97]	是	是	否	否	否	否	否	否	否	Offline (cannot be shrunk)[98]
Fossil	否	否	否	否	是	是	是	是	否	否	是[99]	否	是[99]	Offline[99]
GFS	是	是[100]	是	是[101]	是	是	否	否	否	否	未知	未知	未知	Online
GPFS	是	是	否	是	是	是	是	是	是	是	是	是	否	Online
HAMMER	是	是	未知	未知	是	是	未知	是	未知	未知	未知	未知	On demand	未知
HFS	否	是[102]	否	否	否	是	否	否	否	否	否	否	否	未知
HFS Plus	是[103]	是	否	是[104]	部份[105]	是	是[106]	否	否	是[107]	否	否	否	是[108]
HPFS	否	否	否	否	否	是	否	未知	否	否	未知	未知	否	未知
JFS	是	是	否	是	是[109]	是	否	是	否	否	否	未知	未知	Online (cannot be shrunk)[110]
Lanyard Filesystem	否	否	否	否	是	是	否	否	否	否	否	否	否	Offline (cannot be shrunk)
Level-D	否	否	否	否	否	否	否	否	否	否	未知	未知	未知	未知
LFS	是	是	是[111]	否	是	是	否	否	否	否	未知	未知	未知	未知
Lustre	是	是	是[95]	是	是	是	是 in 2.0 and later	否[78]	否	否	否[78]	否[78]	否[78]	Online[112]
NILFS	是	是	是[111]	否	是	是	是	是	否	否	是	未知	未知	Online (since Linux-3.x and nilfs-utils 2.1)
NSS	是	是	未知	是	是[113]	是[113]	是[114]	是	否	是	未知	未知	未知	未知
NTFS	是	是[115]	否[116]	是[116]	是[117]	是	是	部份[118]	是	是	部份	否	是 (Windows Server 2012)[119]	Online[120]
NWFS	是[121]	是[121]	否	否	是[113]	是[113]	是[114]	未知	否	否	否	是[122]	未知	未知
OCFS	否	是	否	否	是	是	否	否	否	否	未知	未知	未知	未知
OCFS2	是	是	是	是	是	是	否	部份[123]	否	否	未知	否	否	Online for version 1.4 and higher
ODS-2	是	是[124]	否	是	否	否	是	是	否	否	未知	未知	未知	未知
ODS-5	是	是[124]	否	是	否	是	是	是	未知	否	未知	未知	未知	未知
OS4000	否	是[125]	否	否	否	否	否	否	否	否	否	否	否	未知
PramFS	否	是	否	否	是	是	否	否	是	否	否	否	否	否
QFS	是	是	否	是	是	是	否	否	否	否	未知	未知	未知	未知
ReiserFS	是	是	否[126]	是	是	是	否	否	否	否	否	否	否	Online
Reiser4	是	是	是	否	是	是	否	未知	否	是[127]	是	否	未知	Online (can only be shrunk offline)
Reliance	否	否	否[128]	否	否	是	否	否	否	否	是	否	否	未知
Reliance Nitro	是	是	否[128]	否	依情況 on OS	是	否	否	否	否	是	否	否	未知
RT-11	否	否	否	否	否	否	否	否	否	否	否	否	否	未知
UDF	是	是	是[111]	是[111]	是	是	否	否	是	否	否	否	否	未知
UFS1	是	是	否	否	是	是	否	否	否	否	否	否	否	未知
UFS2	是	是	否	否[129][130][131]	是	是	否	是	未知	否	否	否	否	Offline (cannot be shrunk)[132]
V6FS	是	否	否	否	是	是	否	否	否	否	否	否	否	未知
V7FS	是	否[133]	否	否	是	是	否	否	否	否	否	否	否	未知
VxFS	是	是	是	否	是	是	是	是[134]	未知	否	未知	未知	是	未知
VMFS2	是	是	否	是	是	是	否	否	否	否	未知	未知	未知	未知
VMFS3	是	是	否	是	是	是	否	否	否	否	未知	未知	未知	未知
XFS	是	是	是	是	是[135]	是	否	否	否	否	否	否	否	Online (cannot be shrunk)
ZFS	是	是	是[136]	否[136]	是	是	否	是	否	是	是	是	是	Online (cannot be shrunk)[137]
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

文件系统	Block suballocation	Variable file block size[138]	Extents	Allocate-on-flush	稀疏文件	Transparent compression
Be File System	否	否	是	否	未知	否
Btrfs	部份[139]	否	是	是	是	是
CBM DOS	否	部份[140]	否	否	否	否
CP/M filesystem	否	否	是	否	是	否
DECtape	否	否	否	否	否	否
DOS (GEC)	否	是	是	否	否	否
ext2	否[141]	否	否	否	是	否[142]
ext3	否[141]	否	否	否	是	否
ext3cow	否[141]	否	否	否	是	否
ext4	否[141]	否	是	是	是	否
exFAT	未知	否	否	未知	否	否
FAT12	否	否	否	否	否	否[143]
FAT16	否	否	否	否	否	否[143]
FAT32	否	否	否	否	否	否
FFS	8:1[144]	否	否	否	是	否
Fossil	否	否	否	否	否	是[99]
GFS	部份[145]	否	否	否	是	否
GPFS	是	是	否	否	是	否
HFS Plus	否	否	是	是	否	是
HPFS	否	否	是	否	否	否
JFS	是	否	是	否	是	only in JFS1 on AIX[146]
Level-D	是	否	是	否	否	否
LFS	8:1[144]	否	否	否	是	否
Lustre	否	否	是	是	是	否
NSS	否	否	是	否	未知	是
NILFS	否	否	Planned	是	是	否
NTFS	部份	否	是	否	是	部份[147]
NWFS	是[148]	否	否	否	未知	是
OCFS	否	否	是	否	未知	否
OCFS2	否	否	是	否	是	否
ODS-5	否	否	是	否	未知	否
OS4000	否	是	是	否	否	否
PramFS	否	否	否	否	是	否
QFS	是	否	否	否	未知	否
ReiserFS	是	否	否	否	是	否
Reiser4	是	否	是[149]	是	是	是[127]
Reliance	否	否	否	否	否	否
Reliance Nitro	否	否	是	否	是	否
UDF	否	否	是	依情況[150]	否	否
UFS1	8:1[144]	否	否	否	是	否
UFS2	8:1[144]	是	否	否	是	否
V6FS	否	否	否	否	是	否
V7FS	否	否	否	否	是	否
VMFS2	是	否	否	否	是	否
VMFS3	是	否	是	否	是	否
VxFS	未知	否	是	否	是	否
XFS	否	否	是	是	是	否
ZFS	部份[151]	是	否	是	是	是
File system	Block suballocation	Variable file block size[138]	Extents	Allocate-on-flush	Sparse files	Transparent compression

支持的操作系统

文件系统	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
BFS	否	部份 - 需使用第三方驅動程式，只讀	部份 - 需使用第三方驅動程式，只讀	部份 - 只讀	否	未知	否	是	未知	未知	未知	未知	否	否	未知	未知	否
Btrfs	否	否	With WinBtrfs	是: 內核版本 2.6.29 至 3.9 不穩定; 內核版本 3.10 後穩定	否	否	否	否	否	否	否	否	否	否	未知	未知	否
DECtape	否	未知	未知	with AncientFS[152]	否	with AncientFS[152]	with AncientFS[152]	未知	未知	未知	未知	未知	否	否	未知	未知	否
exFAT	否	部份 需使用第三方驅動程式，只讀	是 : Win7, Vista SP1, can be added to XP SP2, SP3	是 since kernel 5.4	否	部份 10.6.5+, 限制簇大小為 1024 位元組	否	否	是	否	否	否	是	否	未知	未知	未知
ext2	未知	未知	with Ext2Fsd (complete)[153] or Ext2 IFS (partial, no large inodes)[154] or Ext2Read (read-only, also on LVM2)[155]	是 since kernel 0.99	否	with ExtFS,[156] fuse-ext2,[157] and ext2fsx[158]	是	只讀	未知	未知	未知	third-party app[159]	with 3rd-party app[160]	with 3rd-party app[160]	未知	未知	是
ext3	未知	未知	with Ext2Fsd (complete)[153] or Ext2 IFS (partial, no large inodes)[154] or Ext2Read (read-only, also on LVM2)[155]	是 since kernel 2.4.15	否	with ExtFS[156] and fuse-ext2[157]	部份 read-only[161]	未知	是	未知	未知	未知	with 3rd-party app[160]	with 3rd-party app[160]	未知	未知	否
ext3cow	未知	未知	未知	是 Kernel 2.6.20	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
ext4	否	否	部份 with Ext2Fsd (partial, extents limited)[153] or Ext2Read (read-only, also on LVM2)[155]	是 since kernel 2.6.28	否	with ExtFS (full read/write), [156] fuse-ext2 (partial),[157] and ext4fuse (read-only)[162]	部份 support in kernel since version 10.1 (read-only)[161] or with ext4fuse (read-only)[162]	未知	未知	未知	未知	未知	否	未知	未知	未知	否
FAT12	是	是	是	是	是	是	是	是	否	部份 on diskettes only, through dos* commands	未知	是	是[163]	未知	是[164]	未知	是
FAT16	是 since DOS 3.0, FAT16B since DOS 3.31	是	是	是	是	是	是	是	是	部份 on diskettes only, through dos* commands	未知	是	是[163]	是	是[164]	未知	是
FAT32	是 since DOS 7.1[165]	是 since Windows 95 OSR2	是 since Windows 2000	是	是	是	是	是	是	部份 on diskettes only, through dos* commands	未知	with third-party app[166]	是[163]	是	是[164]	未知	是
FFS	否	未知	未知	是[167]	否	是	是	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知
Fossil	否	否	否	with 3rd-party software[168]	否	with 3rd-party software[168]	with 3rd-party software[168]	否	with 3rd-party software[168]	否	否	否	否	否	否	否	是
GFS	否	未知	未知	是 since kernel 2.6.19	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	否
HFS	否	with third-party app[169]	with third-party app[169][170]	是	是	部份: read-only since OSX 10.6[171]	with third-party app[172][173]	未知	未知	未知	否	with third-party app[174]	否	否	否	未知	否
HFS Plus	否	with third-party app[169]	with third-party app[169][170]	部份 - write support occurs if journal is empty, but requires a force mount.	是 since Mac OS 8.1	是	部份 read-only third-party app[175]	未知	未知	未知	否	with third-party app	否	否	否	未知	否
HPFS	with third-party driver	部份 read-only third-party driver[176]	included until v3.51, third-party driver until 4.0[177]	是	否	未知	是	未知	未知	未知	未知	是	否	未知	未知	未知	否
IBM Spectrum Scale[178]	否	否	是	是 since 2001	否	否	否	否	否	是	否	否	否	否	否	否	否
IBM HFS	否	否	否	否	否	否	否	否	否	否	是	否	未知	未知	未知	未知	否
IBM zFS	否	否	否	否	否	否	否	否	否	否	是	否	未知	未知	未知	未知	否
JFS	否	未知	未知	是	否	否	否	未知	未知	是	未知	是	否	否	未知	否	否
Level-D	否	未知	未知	未知	否	未知	否	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
LFS	否	未知	未知	with logfs[179] and others	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	未知
LTFS	否	未知	未知	是	否	是	否	否	否	否	否	否	否	否	未知	未知	否
Lustre	否	否	部份 - under development[180]	是[181]	否	部份 - via FUSE	部份 - via FUSE	否	部份 - under development[182]	否	否	否	否	否	未知	未知	否
NILFS	否	未知	未知	是 since kernel 2.6.30	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	否
NSS	未知	未知	未知	with Novell OES2[來源請求]	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	否
NTFS	with third-party driver	with third-party driver[183]	是	是 Kernel 2.2 or newer, or with NTFS-3G or ntfsprogs	with NTFS-3G or MacFUSE	with NTFS-3G or partial read-only in kernel	with NTFS-3G	read-only	with NTFS-3G on Opensolaris	未知	未知	部份 read-only third-party driver[184]	with 3rd-party driver[185]	否	未知	未知	未知
NWFS	未知	未知	未知	via ncpfs client software[186]	否	未知	是	未知	未知	未知	未知	未知	否	否	未知	未知	否
OCFS	否	未知	未知	是	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	否
OCFS2	否	未知	未知	是	否	未知	否	未知	未知	未知	未知	未知	否	否	未知	未知	否
ODS-2	否	未知	未知	部份 read-only with tool or kernel module[187]	否	未知	否	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
ODS-5	否	未知	未知	部份 read-only with kernel module[187]	否	未知	否	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
PramFS	否	否	否	是	否	否	否	否	否	否	否	否	否	否	否	否	否
QFS	否	未知	未知	via client software[188]	否	未知	否	未知	是	未知	未知	未知	否	否	未知	未知	否
ReFS	否	否	是 since Windows Server 2012 and Windows 8.1	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知	未知
Reiser4	否	未知	部份 with DiskInternals Linux Reader[170] (read-only)	with a kernel patch	否	否	否	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
ReiserFS	否	未知	部份 with DiskInternals Linux Reader[170] (read-only)	是 since kernel 2.4.1	否	否	部份 - read only	部份 - read only	未知	未知	未知	未知	with 3rd-party app[160]	with 3rd-party app[160]	未知	未知	否
Reliance	否	否	否	否	否	否	否	否	否	否	否	否	是	否	是	未知	否
Reliance Nitro	否	否	否	是	否	否	否	否	否	否	否	否	是	是	是	未知	否
RT-11	否	未知	未知	未知	否	未知	否	未知	未知	未知	未知	未知	否	否	是	未知	否
UDF	未知	部份 read-only support of UDF 1.02 since Win95 OSR2	是[189]	是	是 since Mac OS 9	是	是	部份	是	未知	未知	未知	是	未知	未知	未知	否
UFS1	否	未知	未知	部份 - read only	否	是	是	未知	未知	未知	未知	未知	未知	未知	否	未知	未知
UFS2	否	未知	部份 - with DiskInternals Linux Reader[170] (read-only)	部份 - read only	否	否	是	未知	未知	未知	未知	未知	未知	未知	否	未知	未知
VMFS2	未知	未知	未知	未知	否	未知	否	未知	未知	未知	未知	未知	未知	未知	未知	否	否
VMFS3	否	未知	未知	部份 read-only with vmfs[190]	未知	未知	否	未知	未知	未知	未知	未知	未知	未知	未知	未知	否
VxFS	否	未知	未知	是	否	未知	否	未知	是	是	未知	未知	否	否	未知	是	否
XFS	否	未知	未知	是 since kernel 2.4	否	未知	部份: read-only	未知	未知	未知	未知	未知	否	否	未知	未知	否
ZFS	否	否	否	with 3rd Party kernel module[191] or FUSE[192]	否	with free 3rd-party software[193]	是	否	是	否	否	否	未知	未知	未知	未知	否
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

参见

• 压缩文件格式列表
• 压缩软件比较
• 压缩软件列表
• 文件系统列表

注释

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. through OEM agreement
3. Polycenter File System — HELP, Tru64 Unix managers, ORNL, （原始内容存档于2012年3月9日）
4. 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.
5. Specifications for the Reliance file systems are available here [1]^{[失效連結]}.
6. 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.
7. 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).
8. 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.
9. 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.
10. 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.
11. 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.
12. ProDOS 8 Technical Reference Manual. [31 May 2013]. （原始内容存档于2021-02-11）.
13. Beneath Apple ProDOS (PDF). Quality Software. 1985: 2–8 [2015-05-31]. ISBN 0-912985-05-4. （原始内容存档 (PDF)于2020-12-03）.
14. Varies wildly according to block size and fragmentation of block allocation groups.
15. 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: < > [ ].
16. Maximum CP/M-80 2.2 volume size?, comp.os.cpm, Google Groups, [2009-10-09]^{[失效連結]}
17. Table "Limits" states a maximum of 255 Unicode characters for the filename [2] （页面存档备份，存于互联网档案馆）
18. KB955704. 2009-01-27 [2015-05-31]. （原始内容存档于2011-05-24）. Description of the exFAT file system driver update package [for 32-bit XP]
19. Interviews/EricSandeen. FedoraProject. 2008-06-09 [2009-10-09]. （原始内容存档于2018-12-15）.
20. ext4 1.42 （页面存档备份，存于互联网档案馆） "This release of e2fsprogs has support for file systems > 16 TB"
21. msdn TexFAT File Naming Limitations. 2009-10-14 [2015-05-31]. （原始内容存档于2016-05-10）.
22. Depends on whether the FAT12, FAT16 or 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). Short names also do not normally contain lowercase letters. Also note that a few special device names should be avoided, as some operating systems (notably DOS and Windows) effectively reserve them.
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. [3] （页面存档备份，存于互联网档案馆）
24. 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.
25. 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 /.
26. 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.
27. 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.
28. Docs, Apple, [2015-05-31], （原始内容存档于2008-03-17）
29. Docs, [2015-05-31], （原始内容存档于2012-06-05）
30. 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.
31. 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.
32. ISO 9660#Restrictions
33. 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
34. 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.
35. Joliet Specification 互联网档案馆的存檔，存档日期2009-04-14.
36. https://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt
37. LEAN file system. Freedos-32.sourceforge.net. [2013-02-05]. （原始内容存档于2021-03-02）.
38. File, file system, and memory size limits in Minix. Minix1.woodhull.com. [2013-02-05]. （原始内容存档于2020-02-12）.
39. NSS allows files to have multiple names, in separate namespaces.
40. 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).
41. Richard Russon and Yuval Fledel. NTFS Documentation (PDF). [2011-06-26]. （原始内容存档 (PDF)于2020-07-04）.
42. Naming Files, Paths, and Namespaces (MSDN Library article). [2015-05-31]. （原始内容存档于2018-06-01）. NB: This article includes discussion of the NT & Win32 namespaces used by Windows APIs; these are distinct from the NTFS filename namespaces.
43. 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.
44. 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. [2015-05-31]. （原始内容存档于2017-07-07）.
45. 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.
46. Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
47. Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
48. 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.
49. 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 [2013-02-05]. （原始内容存档于2013-05-15）.
50. ReiserFS has a theoretical maximum file size of 1 EB, but "page cache limits this to 8TB on architectures with 32 bit int"[4] （页面存档备份，存于互联网档案馆）
51. SFS file system. Publib.boulder.ibm.com. [2013-02-05].^{[永久失效連結]}
52. This restriction might be lifted in newer versions.
53. 2³² × block size
54. Wenguang's Introduction to Universal Disk Format (UDF). Google Sites. Section 5.1 Highlight of the UDF Format. 1 February 2009 [17 July 2014]. （原始内容存档于2021-03-08）.
55. See manual 存档副本. [2015-05-31]. （原始内容存档于2016-03-07）.
56. See manual 存档副本. [2015-05-31]. （原始内容存档于2016-03-04）.
57. See "dir (5)" in Volume 1 of the manual 存档副本. [2004-08-26]. （原始内容存档于2004-08-26）.
58. 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.
59. 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.
60. Note that the filename can be much longer XFS#Extended attributes
61. 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.
62. Implemented in later versions as an extension
63. 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.
64. ext4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming
65. 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.
66. 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.
67. File creation and file access timestamps are supported only by DOS 7.0 and higher, and typically only when explicitly enabled.
68. 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.
69. 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.
70. 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.
71. As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See. Trustedbsd.org. [2013-02-05]. （原始内容存档于2010-01-23）.
72. The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
73. 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.
74. Not applicable to file systems on a read-only medium.
75. Available only if the file has an Extended Attribute block.
76. Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
77. Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
78. Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
79. 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.
80. As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [5] （页面存档备份，存于互联网档案馆）
81. The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
82. 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.
83. 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.
84. 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.
85. Record Management Services (RMS) attributes include record type and size, among many others.
86. CRCs are employed for certain types of metadata.
87. Access-control lists and MAC labels are layered on top of extended attributes.
88. Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
89. 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.
90. 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
91. McPherson, Amanda, A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, 2009-06-22 [2009-09-01], （原始内容存档于2012-06-24）
92. Wiki, BTRFS, Deduplication, [2015-05-31], （原始内容存档于2021-03-13）
93. Linux kernel versions 2.6.12 and newer.
94. Offline growing/shrinking as well as online growing: Linux man page for resize2fs(8) (from e2fsprogs 1.41.9). [2015-05-31]. （原始内容存档于2023-03-25）.
95. Off by default.
96. 6, Parted manual, GNU, [2015-05-31], （原始内容存档于2020-02-25）
97. "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.
98. OpenBSD growfs(8) manpage. Openbsd.org. 2008-11-28 [2013-02-05].
99. When used with venti.
100. 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
101. Optional journaling of data
102. 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.
103. Hard Links on HFS. Developer.apple.com. [2013-02-05]. （原始内容存档于2009-07-01）.
104. 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.
105. 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 互联网档案馆的存檔，存档日期2008-10-06. (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).
106. 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 （页面存档备份，存于互联网档案馆）.
107. As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.
108. Since Mac OS X Snow Leopard, online resizing is supported.How to resize a live partition in Snow Leopard and Lion. [2015-05-31]. （原始内容存档于2013-09-22）.
109. 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.
110. 存档副本. [2015-05-31]. （原始内容存档于2010-02-02）.
111. UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
112. 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
113. 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.
114. 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 （页面存档备份，存于互联网档案馆）)
115. 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.
116. NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
117. 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.
118. NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
119. Rick Vanover. Windows Server 8 data deduplication. [2011-12-02]. （原始内容存档于2012-07-04）.
120. How to Shrink and Extend NTFS Volumes in Windows. Bleepingcomputer.com. [2013-02-05]. （原始内容存档于2011-09-03）.
121. Available only in the "NFS" namespace.
122. Limited capability. Volumes can span physical disks (volume segment)
123. OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
124. These are referred to as "aliases".
125. Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
126. Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.^[為何？]
127. Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
128. File system implements reliability via atomic transactions.
129. "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
130. Block level journals can be added by using gjournal module in FreeBSD.
131. 存档副本. [2015-05-31]. （原始内容存档于2017-05-30）.
132. FreeBSD growfs(8) manpage. Freebsd.org. 2012-04-30 [2013-02-05]. （原始内容存档于2016-03-04）.
133. 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.
134. VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
135. Optionally no on IRIX and Linux.
136. 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.
137. How to resize ZFS. [2015-05-31]. （原始内容存档于2020-02-16）.
138. 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.
139. Btrfs can only inline files smaller than 3916B with its metadataMailing list discussion. [2015-05-31]. （原始内容存档于2015-06-27）.
140. only for .REL (record structured) files, up to 254 bytes/record
141. Fragments were planned, but never actually implemented on ext2 and ext3.
142. 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.
143. 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.
144. Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
145. Only for "stuffed" inodes
146. AIX documentation: JFS data compression. IBM. [2015-05-31]. （原始内容存档于2020-04-18）.
147. Only if formatted with 4kB-sized clusters or smaller
148. 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.
149. In "extents" mode.
150. Depends on UDF implementation.
151. When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
152. AncientFS. [2015-05-31]. （原始内容存档于2015-02-02）.
153. 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. [6] （页面存档备份，存于互联网档案馆）
154. 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.[7] （页面存档备份，存于互联网档案馆）
155. 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 （页面存档备份，存于互联网档案馆）
156. 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.[8] （页面存档备份，存于互联网档案馆）
157. Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[9]^{[失效連結]}
158. Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[10] （页面存档备份，存于互联网档案馆）
159. OS/2 ext2 Driver. [2020-01-31]. （原始内容存档于2016-03-04）.
160. See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
161. 存档副本. [2015-05-31]. （原始内容存档于2019-01-18）.
162. ext4fuse is a free software multi OS FUSE module to mount ext4 file system devices and/or images with read-only support. [11] （页面存档备份，存于互联网档案馆）
163. Files, Databases, and Persistent Storage （页面存档备份，存于互联网档案馆）. MSDN.
164. Via dosFs.
165. 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.
166. OS/2 and eComstation FAT32 Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）.
167. How to mount FFS partition under Linux - NetBSD Wiki. Wiki.netbsd.se. [2009-10-09]. （原始内容存档于2008年3月19日）.
168. Via Plan 9 from User Space; initial checkin fossil: import from plan 9. [2013-11-24]. （原始内容存档于2013-12-03）.
169. Cross-platform Drive Solutions. Sharing Disks - Windows Products. Macwindows.com. [2013-02-05]. （原始内容存档于2011-06-20）.
170. DiskInternals Linux Reader （页面存档备份，存于互联网档案馆） is an application for Windows NT that allows reading of Ext2/3/4, ReiserFS, Reiser4, HFS/HFS+, FAT/exFAT, NTFS, ReFS, and UFS2 filesystems.
171. Gagne, Ken. Losing legacy data to Snow Leopard. Computerworld. 2009-08-31 [2009-09-07]. （原始内容存档于2009-09-03）.
172. hfsutils at FreshPorts. Freshports.org. [2013-02-05]. （原始内容存档于2018-02-18）.
173. hfs at FreshPorts. Freshports.org. [2013-02-05]. （原始内容存档于2019-01-18）.
174. OS/2 HFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）.
175. Catacombae HFSExplorer. Hem.bredband.net. [2013-02-05]. （原始内容存档于2013-02-02）.
176. DOS/Win 9x HPFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）.
177. Win NT 4.0 HPFS Driver. [2020-01-31]. （原始内容存档于2016-03-04）.
178. IBM GPFS Product Page. [2015-05-31]. （原始内容存档于2014-04-30）.
179. logfs. [2015-05-31]. （原始内容存档于2021-03-22）.
180. 存档副本. [2015-05-31]. （原始内容存档于2011-03-14）.
181. 存档副本. [2015-05-31]. （原始内容存档于2018-12-15）.
182. 存档副本. [2015-05-31]. （原始内容存档于2011-07-27）.
183. NTFS for Windows 98. Download.chip.eu. [2013-02-05]. （原始内容存档于2016-03-04）.
184. OS/2 NTFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-08-07）.
185. Tuxera NTFS for Windows CE. See article. [2015-05-31]. （原始内容存档于2012-09-18）. and announcement 互联网档案馆的存檔，存档日期2011-05-22..
186. ncpfs. [2015-05-31]. （原始内容存档于2008-05-15）.
187. VMS2Linux. [2015-05-31]. （原始内容存档于2021-01-18）.
188. Using SAM-QFS on Linux Clients 互联网档案馆的存檔，存档日期2011-10-02.
189. Understanding the difference between the Live File System and Mastered disc formats. Which CD or DVD format should I use?. Microsoft. [2008-11-22]. （原始内容存档于2016-03-02）.
190. vmfs. [2015-05-31]. （原始内容存档于2009-03-02）.
191. Native ZFS for Linux. [2015-05-31]. （原始内容存档于2019-05-22）.
192. ZFS on FUSE 互联网档案馆的存檔，存档日期2013-05-13.
193. Mac ZFS. [2015-05-31]. （原始内容存档于2014-02-11）.

外部链接

• A speed comparison of filesystems on Linux 2.4.5 (archived)
• Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch （页面存档备份，存于互联网档案馆） (April 23, 2006)