Anexo:Comparación de sistemas de archivos

Las siguientes tablas comparan información general y técnica de varios sistemas de archivos.

Información general

Sistema de archivos	Creador	Año de presentación	Sistema operativo originario
DECtape	DEC	1964	PDP-6 Monitor
Level-D	DEC	1968	TOPS-10
George 2	ICT (posteriormente ICL)	1968	George 2
ODS-1	DEC	1972	RSX-11
RT-11 file system	DEC	1973	RT-11
DOS (GEC)	GEC	1973	Core Operating System
CP/M file system	Gary Kildall	1974	CP/M
V6FS	Bell Labs	1975	Version 6 Unix
OS4000	GEC	1977	OS4000
FAT (8-bit)	Marc McDonald, Microsoft	1977	Microsoft Disk BASIC
DOS 3.x	Apple Computer	1978	Apple DOS
Pascal	Apple Computer	1978	Apple Pascal
CBM DOS	Commodore	1978	Microsoft BASIC (para CBM PET)
V7FS	Bell Labs	1979	UNIX Versión 7
ODS-2	DEC	1979	OpenVMS
FAT12	Tim Paterson	1980	QDOS, 86-DOS
AFS	Carnegie Mellon University	1982	Multiplatforma, multi-sistema operativo
DFS	Acorn Computers Ltd	1982	Acorn BBC Micro MOS
ADFS	Acorn Computers Ltd	1983	Acorn Electron (posteriormente Arthur RISC OS)
FFS	Kirk McKusick	1983	4.2BSD
ProDOS	Apple Computer	1983	ProDOS 8
MFS	Apple Computer	1984	Mac OS
FAT16	Microsoft	1984	MS-DOS 3.0
Elektronika BK tape format	NPO "Scientific centre" (ahora Sitronics)	1985	Vilnius Basic, BK monitor program
HFS	Apple Computer	1985	Mac OS
Amiga OFS	Metacomco para 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 y Microsoft	1988	OS/2
ISO 9660:1988	Ecma International, Microsoft	1988	MS-DOS, Mac OS, y AmigaOS
JFS1	IBM	1990	AIX^{[n 1]}
VxFS	VERITAS, (ahora Symantec)	1991	AIX, HP-UX, Solaris, Linux
ext	Rémy Card	1992	Linux
WAFL	NetApp	1992	Data ONTAP
MINIX V2 FS	Andrew S. Tanenbaum	1992	MINIX 1.6 and 2.0
AdvFS	DEC	1993^[1]	Digital Unix
NTFS Version 1.0	Microsoft, Tom Miller, Gary Kimura	1993	Windows NT 3.1
LFS	Margo Seltzer	1993	Berkeley Sprite
ext2	Rémy Card	1993	Linux, Hurd
UFS1	Kirk McKusick	1994	4.4BSD
XFS	SGI	1994	IRIX, Linux, FreeBSD
HFS (Hierarchical File System)	IBM	1994	MVS/ESA (ahora z/OS)
Rock Ridge	Young Minds Inc.	1994	Linux, Mac OS, Amiga OS, y FreeBSD
Joliet ("CDFS")	Microsoft	1995	Microsoft Windows, Linux, Mac OS, y FreeBSD
PFS	Michiel Pelt	1996	AmigaOS
Romeo	Adaptec	1996	Microsoft Windows
UDF	ISO/ECMA/OSTA	1995	-
FAT32	Microsoft	1996	Windows 95b^{[n 2]}
QFS	LSC Inc, Sun Microsystems	1996	Solaris
GPFS	IBM	1996	AIX, Linux, Windows
Be File System	Be Incorporated, 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, y AmigaOS
JFS	IBM	1999	OS/2 Warp Server para e-business
GFS	Sistina (Red Hat)	2000	Linux
Melio FS	Sanbolic	2001	Windows
NTFS Version 3.1	Microsoft	2001	Windows XP
ReiserFS	Namesys	2001	Linux
zFS	IBM	2001	z/OS (portado a OS/390)
FATX	Microsoft	2002	Xbox
UFS2	Kirk McKusick	2002	FreeBSD 5.0
Lustre	Cluster File Systems (posteriormente Oracle Corporation)	2002	Linux
OCFS	Oracle Corporation	2002	Linux
VMFS2	VMware	2002	VMware ESX 2.0
ext3cow	Zachary Peterson	2003	Linux
Fossil	Bell Labs	2003	Plan 9 from Bell Labs 4
Google File System	Google	2003	Linux
PramFS	MontaVista	2003	Linux
Reliance^[2]	Datalight	2003	Windows CE, VxWorks, puertos personalizados
VxCFS	VERITAS, (ahora Symantec)	2004	AIX, HP-UX, Solaris, Linux
ZFS	Sun Microsystems	2004	Solaris, FreeBSD, PC-BSD, FreeNAS
Reiser4	Namesys	2004	Linux
Non-Volatile File System	Palm, Inc.	2004	Palm OS
MINIX V3 FS	Andrew S. Tanenbaum	2005	MINIX 3
OCFS2	Oracle Corporation	2005	Linux
NILFS	NTT	2005	Linux, (para NetBSD como sólo lectura)
VMFS3	VMware	2005	VMware ESX 3.0
GFS2	Red Hat	2006	Linux
ext4	Various	2006	Linux
exFAT	Microsoft	2006, 2009	Windows CE 6.0, Windows XP SP3, Windows Vista SP1
TexFAT/TFAT	Microsoft	2006	Windows CE 6.0
Btrfs	Oracle Corporation	2007	Linux
Ceph	Sage Weil, Inktank Storage	2007, 2012	Linux
HAMMER	Matthew Dillon	2008	DragonFly BSD
Tux3	Various	2008	Linux
UBIFS	Nokia con ayuda de la University of Szeged	2008	Linux
Oracle ACFS	Oracle Corporation	2009	Linux - Red Hat Enterprise Linux 5 y Oracle Linux 5
Reliance Nitro^[2]	Datalight	2009	Windows CE, Windows Mobile, VxWorks, Linux, puertos personalizados
LTFS	IBM	2010	Linux, Mac OS X, se prevé también Microsoft Windows,
IlesfayFS	Ilesfay Technology Group	2011	Microsoft Windows, se prevé también Red Hat Enterprise Linux
VMFS5	VMware	2011	VMware ESXi 5.0tux 3 stats
ReFS	Microsoft	2012, 2013	Windows Server 2012
Lanyard Filesystem	Dan Luedtke	2012	Linux
F2FS	Samsung	2012	Linux
Sistema de archivos	Creador	Año de presentación	Sistema operativo originario

Límites

Sistema de archivos	Longitud máxima del nombre de archivo	Caracteres permitidos en las entradas de directorio^{[n 3]}	Longitud máxima de la ruta de acceso	Tamaño máximo de archivo	Tamaño máximo de volumen^{[n 4]}
Acorn ADFS	10 bytes	Cualquier carácter ISO 8859-1 excepto: ESPACIO $ & % @ \ ^ : . # * " ¦	No hay límite definido	512 MiB ó 4 GiB^{[n 5]}	512 MiB ó 4 GiB^{[n 6]}
Apple DOS 3.x	&&&&&&&&&&&&&030.&&&&&030 bytes	&0000000000000255.000000Any byte except NUL	B, no subdirectories (105 files per disk)	Desconocido	kB DOS 3.3 (assuming standard 35 tracks) 113.75\|kB DOS 3.1, 3.2
Apple ProDOS	&&&&&&&&&&&&&015.&&&&&015 bytes	&0000000000000063.000000A-Z, a-z, 0-9, and period	&&&&&&&&&&&&&064.&&&&&064 B, including slashes^[3]^[4]	16 MiB	32 MiB
CP/M file system	&0000000000000011.0000008.3	any byte except: SPACE < > . , ; : = ? * [ ] % \| ( ) / \^{[n 7]}	16 "user areas", no subdirectories	8 MiB^[5]	8 MiB to 512 MB^[5]
IBM SFS	&0000000000000016.0000008.8	Desconocido	Non-hierarchical^[6]	Desconocido	Desconocido
DECtape	&0000000000000009.0000006.3	&0000000000000036.000000A–Z, 0–9	DTxN:FILNAM.EXT = 15	B (577 * 640)	B (578 * 640)
Elektronika BK tape format	&&&&&&&&&&&&&016.&&&&&016 bytes	Desconocido	Non-hierarchical	kB	kB (approx) per side for 90 min cassette (limited only by tape length)
MicroDOS file system	&&&&&&&&&&&&&014.&&&&&014 bytes	Desconocido	Desconocido	16 MiB	32 MiB
Level-D	&0000000000000009.0000006.3	&0000000000000036.000000A–Z, 0–9	DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67	24 GB (34,359,738,368 words (2³⁵-1); 206,158,430,208 SIXBIT bytes)	12 GB (approx; 64 * 178 MB)
RT-11	&0000000000000009.0000006.3	&0000000000000037.000000A–Z, 0–9, $	Non-hierarchical	32 MiB (65536 * 512 B)	32 MiB
V6FS	&&&&&&&&&&&&&014.&&&&&014 bytes^{[n 8]}	&0000000000000254.000000Any byte except NUL and /^{[n 9]}	No hay límite definido^{[n 10]}	16 MiB^[7]	2 TiB
DOS (GEC)	&&&&&&&&&&&&&&08.&&&&&08 bytes	&0000000000000036.000000A–Z, 0–9	Non-hierarchical	64 MiB	64 MiB
OS4000	&&&&&&&&&&&&&&08.&&&&&08 bytes	&0000000000000036.000000A–Z, 0–9 Period is directory separator	No hay límite definido^{[n 10]}	2 GiB	1 GiB (por lo menos)
CBM DOS	&&&&&&&&&&&&&016.&&&&&016 bytes	&0000000000000255.000000Any byte except NUL	Non-hierarchical	16 MiB	16 MiB
V7FS	&&&&&&&&&&&&&014.&&&&&014 bytes^{[n 8]}	&0000000000000254.000000Any byte except NUL and /^{[n 9]}	No hay límite definido^{[n 10]}	1 GiB^{[n 11]}	2 TiB
exFAT	&0000000000000510.000000255 characters^[8]	&0000000001114111.000000Any Unicode except NUL	No hay límite definido	127 PiB	64 ZiB, 512 TiB recomendado^[9]
TexFAT	&0000000000000494.000000247 characters	&0000000001114111.000000Any Unicode except NUL	No hay límite definido	2 GiB	500 GiB comprobado^[10]
FAT12	&0000000000000011.0000008.3 (255 UTF-16 code units with LFN)^{[n 8]}	&0000000001114111.000000Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ \| + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL^{[n 8]}^{[n 9]}	No hay límite definido^{[n 10]}	32 MiB (256 MiB)	32 MiB (256 MiB)
FAT16	&0000000000000011.0000008.3 (255 UTF-16 code units with LFN)^{[n 8]}	&0000000001114111.000000Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ \| + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL^{[n 8]}^{[n 9]}	No hay límite definido^{[n 10]}	2 GiB (4 GiB)	2 GiB or 4 GiB
FAT32	&0000000000000011.0000008.3 (255 UTF-16 code units with LFN)^{[n 8]}	&0000000001114111.000000Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ \| + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL^{[n 8]}^{[n 9]}	No hay límite definido^{[n 10]}	4 GiB (256 GiB^[11])	2 TiB^[12] (16 TB)
FATX	&&&&&&&&&&&&&042.&&&&&042 bytes^{[n 8]}	&0000000000000108.000000ASCII. Unicode not permitted.	No hay límite definido^{[n 10]}	2 GiB	2 GiB
Fossil	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
MFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except :	No path (flat filesystem)	226 MiB	226 MiB
HFS	&&&&&&&&&&&&&031.&&&&&031 bytes	&0000000000000255.000000Any byte except :^{[n 12]}	Unlimited	2 GiB	2 TiB
HPFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 13]}	No hay límite definido^{[n 10]}	2 GiB	2 TiB^{[n 14]}
NTFS	&0000000000000510.000000255 characters^{[n 15]}^[13]^[14]	&0000000001114102.000000Depends on namespace used^{[n 15]}^[13]^[14]^{[n 16]}	32,767 Unicode characters with each path component (directory or filename) commonly up to 255 characters long^{[n 10]}	16 TB^[15]	256 TB^[15]
ReFS	&0000000000065536.000000255 unicode characters^[16]	Desconocido	KiB	16 EiB	256 ZiB with 16 KiB cluster size (2⁶⁴ × 16 × 2¹⁰). Windows stack addressing allows 16 EiB
HFS Plus	&0000000000000510.000000255 UTF-16 code units^[17]	&0000000001114112.000000Any valid Unicode^{[n 9]}^[18]	Unlimited	8 EiB	8 EiB^[19]^[20]
FFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 ZiB	8 ZiB
UFS1	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	226 TiB	226 TiB
UFS2	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	32 PiB	1 YiB
ext2	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000254.000000Any byte except NUL^{[n 9]} and /	No hay límite definido^{[n 10]}	2 TiB^{[n 4]}	32 TiB
ext3	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000254.000000Any byte except NUL^{[n 9]} and /	No hay límite definido^{[n 10]}	2 TiB^{[n 4]}	32 TiB
ext3cow	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000254.000000Any byte except NUL,^{[n 9]} / and @	No hay límite definido^{[n 10]}	2 TiB^{[n 4]}	32 TiB
ext4	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000254.000000Any byte except NUL^{[n 9]} and /	No hay límite definido^{[n 10]}	16 TiB^{[n 4]}^[21]	1 EiB^[22]
Lustre	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]} and /	No hay límite definido^{[n 10]}	32 PiB (on ext4)	1 YiB (on ext4, 20 PB tested)
GPFS	&&&&&&&&&&&&0255.&&&&&0255 UTF-8 codepoints	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	512 YiB	512 YiB (4 PiB comprobado)
GFS	&&&&&&&&&&&&0255.&&&&&0255	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 EiB^[23]	8 EiB^[23]
ReiserFS	&&&&&&&&&&&04032.&&&&&04032 bytes/226 characters	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 TiB^[24] (v3.6), 2 GiB (v3.5)	16 TiB
NILFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 EB	8 EB
Reiser4	&&&&&&&&&&&03976.&&&&&03976 bytes	&0000000000000254.000000Any byte except / and NUL	No hay límite definido^{[n 10]}	8 TiB on x86	Desconocido
OCFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 TiB	8 TiB
OCFS2	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	4 PiB	4 PiB
Reliance	&&&&&&&&&&&&0260.&&&&&0260 bytes	OS specific	B	4 GiB	2 TiB
Reliance Nitro	&&&&&&&&&&&01024.&&&&&01024 bytes	OS specific	1024 bytes	32 TiB	32 TiB
JFS1	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 EiB	4 PiB
JFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000001114111.000000Any Unicode except NUL	No hay límite definido^{[n 10]}	4 PiB	32 PiB
QFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000254.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	16 EiB^[25]	4 PiB^[25]
BFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	260 GB^[26]	2 EiB
AdvFS	&&&&&&&&&&&&0226.&&&&&0226 characters	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	16 TiB	16 TiB
NSS	&&&&&&&&&&&&0226.&&&&&0226 characters	Depends on namespace used^[27]	Only limited by client	8 TiB	8 TiB
NWFS	&&&&&&&&&&&&&080.&&&&&080 bytes^[28]	Depends on namespace used^[27]	No hay límite definido^{[n 10]}	4 GiB	1 TiB
ODS-5	&&&&&&&&&&&&0236.&&&&&0236 bytes^[29]	Desconocido	4,096 bytes^[30]	2 TiB	2 TiB
VxFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	256 TiB	256 TiB
UDF	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000001114111.000000Any Unicode except NUL	1,023 bytes^[31]	16 EiB	2 TB (hard disk), 8 TB (optical disc)^[32]
MINIX V1 FS	&0000000000000030.00000014 or 30 bytes, set at filesystem creation time	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	64 MiB^[33]	64 MiB^[33]
MINIX V2 FS	&0000000000000030.00000014 or 30 bytes, set at filesystem creation time	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	4 GiB^[33]	1 GiB, then 2 TiB^[33]
MINIX V3 FS	&&&&&&&&&&&&&060.&&&&&060 bytes	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	4 GiB	16 TiB^[33]
VMFS2	&&&&&&&&&&&&0128.&&&&&0128	&0000000000000254.000000Any byte except NUL and /^{[n 9]}	2,048	4 TiB^[34]	64 TiB
VMFS3	&&&&&&&&&&&&0128.&&&&&0128	&0000000000000254.000000Any byte except NUL and /^{[n 9]}	2,048	2 TiB^[34]	64 TiB
ISO 9660:1988	&0000000000000011.000000Level 1: 8.3, Level 2 & 3: ~ 180	Depends on Level^[35]	~ 180 bytes?	4 GiB (Level 1 & 2) to 8 TiB (Level 3)^[36]	8 TiB^[37]
Joliet ("CDFS")	&0000000000000128.00000064 Unicode characters	&0000000001112058.000000All UCS-2 code except * / \ : ; and ?^[38]	Desconocido	4 GiB (same as ISO 9660:1988)	8 TiB (same as ISO 9660:1988)
ISO 9660:1999	Desconocido (207?)	Desconocido	Desconocido	Desconocido	Desconocido
High Sierra	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
HAMMER	Desconocido	Desconocido	Desconocido	Desconocido	1 EiB
LTFS	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
PramFS	&&&&&&&&&&&&&031.&&&&&031 bytes	&0000000000000031.000000Any byte except NUL	Desconocido	1 GiB	8 EiB
Lanyard Filesystem	&&&&&&&&&&&&0255.&&&&&0255 bytes	Any byte except NUL and /^{[n 9]}	No hay límite definido	64 ZiB	128 KiB a 64 ZiB^[39]
LEAN	&&&&&&&&&&&04068.&&&&&04068 bytes^[40]	&0000000001114112.000000case sensitive, in UTF-8 (any Unicode codepoint)	No hay límite definido	8 EiB	8 EiB
XFS	&&&&&&&&&&&&0255.&&&&&0255 bytes^[41]	&0000000000000255.000000Any byte except NUL^{[n 9]}	No hay límite definido^{[n 10]}	8 EiB^[42]	16 EiB^[42]
ZFS	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000001114111.000000Any Unicode except NUL	No hay límite definido^{[n 10]}	16 EiB	16 EiB
Btrfs	&&&&&&&&&&&&0255.&&&&&0255 bytes	&0000000000000255.000000Any byte except NUL	Desconocido	16 EiB	16 EiB
File system	Maximum filename length	Allowable characters in directory entries^{[n 3]}	Maximum pathname length	Maximum file size	Maximum volume size^{[n 4]}

Metadatos

File system	Stores file owner	POSIX file permissions	Creation timestamps	Last access/ read timestamps	Last content modification timestamps	Disk copy created	Last metadata change timestamps	Last archive timestamps	Access control lists	Security/ MAC labels	Extended attributes/ Alternate data streams/ forks	Checksum/ ECC	Max Timestamp Granularity
CBM DOS	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
CP/M file system	No	No	Sí^[43]	No	Desconocido	Desconocido	No	No	No	No	No	No	Desconocido
DECtape	No	No	Sí	No	Desconocido	Desconocido	No	No	No	No	No	No	Desconocido
Elektronika BK tape format	No	No	No	No	Desconocido	Desconocido	No	No	No	No	No	Sí	Desconocido
Level-D	Sí	Sí	Sí	Sí	Desconocido	Desconocido	Sí	Sí	Sí	No	No	No	Desconocido
RT-11	No	No	Sí	No	No	No	No	No	No	No	No	No	Desconocido
DOS (GEC)	Sí	No	Sí	Sí	Sí	Desconocido	No	No	No	No	No	No	Desconocido
OS4000	Sí	No	Sí	Sí	Sí	Desconocido	No	No	No	No	No	No	Desconocido
V6FS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	No	No	No	No	Desconocido
V7FS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	No	No	No	No	Desconocido
FAT12	No^[44]	No^[45]	Parcial^[46]	Parcial^[46]	Sí	Sí	No^[47]	No	No	No	No^[48]	No	10 milliseconds
FAT16	No^[44]	No^[45]	Parcial^[46]	Parcial^[46]	Sí	Sí	No^[47]	No	No	No	No^[48]	No	10 milliseconds
FAT32	No	No	Parcial^[46]	Parcial^[46]	Sí	Sí	No^[47]	No	No	No	No	No	10 milliseconds
exFAT	No	No	Sí	Sí	Sí	No	Desconocido	No	No	Desconocido	Desconocido	Parcial	10 milliseconds
HPFS	Sí^[49]	No	Sí	Sí	Sí	Desconocido	No	No	No	Desconocido	Sí	No	Desconocido
NTFS	Sí	Sí^[50]	Sí	Sí	Sí	No	Sí	No	Sí	Sí^[51]	Sí	No	100 nanoseconds
HFS	No	No	Sí	No	Sí	No	No	Sí	No	No	Sí	No	Desconocido
HFS Plus	Sí	Sí	Sí	Sí	Sí	No	Sí	Sí	Sí	Sí^[52]	Sí	No	1 second
FFS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	No	No	No	No	Desconocido
UFS1	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	Sí^[53]	Sí^[53]	No^[54]	No	Desconocido
UFS2	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	No	Sí^[53]	Sí^[53]	Sí	No	Desconocido
LFS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	No	No	No	No	Desconocido
ext2	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	Sí^[55]	Sí^[55]	Sí	No	1 second
ext3	Sí	Sí	No	Sí	Sí	No	Sí	No	Sí^[55]	Sí^[55]	Sí	No	1 second
ext3cow	Sí	Sí	No	Sí	Sí	No	Sí	No	Sí^[55]	Sí^[55]	Sí	No	1 second
ext4	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	No	Sí^[55]	Sí^[55]	Sí	Parcial^[56]	1 nanosecond
Lustre	Sí	Sí	Parcial^[57]	Sí	Sí	No	Sí	No	Sí	Sí	Sí	Parcial^[58]^[59]	Desconocido
GPFS	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	No	Sí	Sí	Sí	Sí	Desconocido
GFS	Sí	Sí	No	Sí	Desconocido	Desconocido	Sí	No	Sí^[55]	Sí^[55]	Sí	No	Desconocido
NILFS	Sí	Sí	Sí	No	Desconocido	Desconocido	Sí	No	Planned	No	Planned	Sí	Desconocido
ReiserFS	Sí	Sí	No	Sí	Sí	No	No	No	No	No	No	No	Desconocido
Reiser4	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	No	No	No	No	Desconocido
OCFS	No	Sí	No	No	Desconocido	Desconocido	Sí	Sí	No	No	No	No	Desconocido
OCFS2	Sí	Sí	No	Sí	Desconocido	Desconocido	Sí	No	Sí	No	Sí	Parcial^[60]	Desconocido
Reliance	No	No	Sí	No	Sí	No	No	No	No	No	No	Parcial^[61]	Desconocido
Reliance Nitro	Linux port	Linux port	Sí	Sí	Sí	No	No	No	Linux port	No	Sí	Parcial^[61]	Desconocido
XFS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	Sí	Sí^[55]	Sí	Parcial	1 nanosecond
JFS	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	No	Sí	Sí	Sí	No	Desconocido
QFS	Sí	Sí	Sí	Sí	Desconocido	Desconocido	Sí	Sí	Sí	No	Sí	No	Desconocido
BFS	Sí	Sí	Sí	No	Desconocido	Desconocido	No	No	No	No	Sí	No	Desconocido
AdvFS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	Sí	No	Sí	No	Desconocido
NSS	Sí	Sí	Sí^[62]	Sí^[62]	Desconocido	Desconocido	Sí	Sí^[62]	Sí	Desconocido	Sí^[63]^[64]	No	Desconocido
NWFS	Sí	Desconocido	Sí^[62]	Sí^[62]	Desconocido	Desconocido	Sí	Sí^[62]	Sí	Desconocido	Sí^[63]^[64]	No	Desconocido
ODS-5	Sí	Sí	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Sí	Sí	Desconocido	Sí^[65]	No	Desconocido
VxFS	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	No	Sí	Desconocido	Sí^[55]	No	Desconocido
UDF	Sí	Sí	Sí	Sí	Desconocido	Desconocido	Sí	Sí	Sí	No	Sí	No	Desconocido
Fossil	Sí	Sí^[66]	No	Sí	Desconocido	Desconocido	Sí	No	No	No	No	No	Desconocido
ZFS	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	Sí	Sí	Sí^[67]	Sí^[68]	Sí	Desconocido
VMFS2	Sí	Sí	No	Sí	Desconocido	Desconocido	Sí	No	No	No	No	No	Desconocido
VMFS3	Sí	Sí	No	Sí	Desconocido	Desconocido	Sí	No	No	No	No	No	Desconocido
ISO 9660:1988	No	No	Sí^[69]	No^[70]	Sí^[71]	Desconocido	No	No	No	No	No	No	Desconocido
Joliet ("CDFS")	No	No	Sí^[69]	No^[70]	Sí^[71]	Desconocido	No	No	No	No	No	No	Desconocido
ISO 9660:1999	No	No	Sí	No	Desconocido	Desconocido	No	No	No	No	No	No	Desconocido
High Sierra	No	No	Sí	No	Desconocido	Desconocido	No	No	No	No	No	No	Desconocido
Btrfs	Sí	Sí	Sí	Sí	Sí	Desconocido	Sí	Desconocido	Sí	Sí	Sí	Sí	1 nanosecond
Lanyard Filesystem	No	No	Sí	No	Sí	No	Sí	No	No	No	No	No	1 nanosecond
PramFS	Sí	Sí	No	Sí	Sí	Desconocido	Sí	No	Sí	Sí	Sí	Sí	1 second
File system	Stores file owner	POSIX file permissions	Creation timestamps	Last access/read timestamps	Last content modification timestamps	Disk copy created	Last metadata change timestamps	Last archive timestamps	Access control lists	Security/ MAC labels	Extended attributes/ Alternate data streams/ forks	Checksum/ ECC	Max Timestamp Granularity

Características

File system	Enlace duros	Enlace simbólicos	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	Snapshot	XIP	Encryption	COW	Integrated LVM	Data deduplication	Volumes are resizeable
Lanyard Filesystem	No	No	No	No	Sí	Sí	No	No	No	No	No	No	No	Offline (cannot be shrunk)
CBM DOS	No	No	No	No	Sí	Sí	No	No	No	No	No	No	No	No
CP/M file system	No	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
DECtape	No	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
Level-D	No	No	No	No	No	No	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
RT-11	No	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
DOS (GEC)	No	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
OS4000	No	Sí^[72]	No	No	No	No	No	No	No	No	No	No	No	Desconocido
V6FS	Sí	No	No	No	Sí	Sí	No	No	No	No	No	No	No	Desconocido
V7FS	Sí	No^[73]	No	No	Sí	Sí	No	No	No	No	No	No	No	Desconocido
FAT12	No	No	No	No	No	Parcial	No	No	No	No	No	No	No	Offline^[74]
FAT16	No	No	No	No	No	Parcial	No	No	No	No	No	No	No	Offline^[74]
FAT32	No	No	No	No	No	Parcial	No	No	No	No	No	No	No	Offline^[74]
exFAT	No	No	Desconocido	No	No	Sí	No	Desconocido	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido
GFS	Sí	Sí^[75]	Sí	Sí^[76]	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Online
GPFS	Sí	Sí	Desconocido	Desconocido	Sí	Sí	Sí	Sí	Sí	No	Sí	Sí	No	Online
HAMMER	Sí	Sí	Desconocido	Desconocido	Sí	Sí	Desconocido	Sí	Desconocido	Desconocido	Desconocido	Desconocido	On demand	Desconocido
HPFS	No	No	No	No	No	Sí	No	Desconocido	No	No	Desconocido	Desconocido	No	Desconocido
NTFS	Sí	Sí^[77]	No^[78]	Sí^[78]	Sí^[79]	Sí	Sí	Parcial^[80]	Sí	Sí	Parcial	Desconocido	Sí (Windows Server 2012)^[81]	Online^[82]
HFS	No	Sí^[83]	No	No	No	Sí	No	No	No	No	No	No	No	Desconocido
HFS Plus	Sí^[84]	Sí	No	Sí^[85]	Parcial^[86]	Sí	Sí^[87]	No	No	Sí^[88]	No	No	No	Sí^[89]
FFS	Sí	Sí	No	No^[90]	Sí	Sí	No	No	No	No	No	No	No	Offline (cannot be shrunk)^[91]
UFS1	Sí	Sí	No	No	Sí	Sí	No	No	No	No	No	No	No	Desconocido
UFS2	Sí	Sí	No	No^[92]^[93]	Sí	Sí	No	Sí	Desconocido	No	No	No	No	Offline (cannot be shrunk)^[94]
LFS	Sí	Sí	Sí^[95]	No	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
ext2	Sí	Sí	No	No	Sí	Sí	No	No	Sí^[96]	No	No	No	No	Online^[97]
ext3	Sí	Sí	Sí^[98]	Sí	Sí	Sí	No	No	Sí	Sí	No	No	No	Online^[97]
ext3cow	Sí	Sí	Sí^[98]	Sí	Sí	Sí	Desconocido	Sí	Desconocido	Sí	Sí	No	No	Desconocido
ext4	Sí	Sí	Sí^[98]	Sí	Sí	Sí	No	No	Sí	Sí	No	No	No	Online^[97]
Lustre	Sí	Sí	Sí^[98]	Sí	Sí	Sí	Sí in 2.0 and later	No^[59]	No	No	No^[59]	No^[59]	No^[59]	Online^[99]
NILFS	Sí	Sí	Sí^[95]	No	Sí	Sí	Sí	Sí	No	No	Sí	Desconocido	Desconocido	Online (since Linux-3.x and nilfs-utils 2.1)
ReiserFS	Sí	Sí	No^[100]	Sí	Sí	Sí	No	No	No	No	No	No	No	Online
Reiser4	Sí	Sí	Sí	No	Sí	Sí	No	Desconocido	No	Sí^[101]	Sí	No	Desconocido	Online (can only be shrunk offline)
OCFS	No	Sí	No	No	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
OCFS2	Sí	Sí	Sí	Sí	Sí	Sí	No	Parcial^[102]	No	No	Desconocido	No	No	Online for version 1.4 and higher
Reliance	No	No	No^[103]	No	No	Sí	No	No	No	No	Sí	No	No	Desconocido
Reliance Nitro	Sí	Sí	No^[103]	No	Depende del sistema operativo	Sí	No	No	No	No	Sí	No	No	Desconocido
XFS	Sí	Sí	Sí	Sí	Sí^[104]	Sí	No	No	No	No	No	No	No	Online (cannot be shrunk)
JFS	Sí	Sí	No	Sí	Sí^[105]	Sí	No	Sí	No	No	No	Desconocido	Desconocido	Online (cannot be shrunk)^[106]
QFS	Sí	Sí	No	Sí	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
Be File System	Sí	Sí	No	Sí	Sí	Sí	Desconocido	No	No	No	No	No	No	Desconocido
NSS	Sí	Sí	Desconocido	Sí	Sí^[107]	Sí^[107]	Sí^[108]	Sí	No	Sí	Desconocido	Desconocido	Desconocido	Desconocido
NWFS	Sí^[109]	Sí^[109]	No	No	Sí^[107]	Sí^[107]	Sí^[108]	Desconocido	No	No	No	Sí^[110]	Desconocido	Desconocido
ODS-2	Sí	Sí^[111]	No	Sí	No	No	Sí	Sí	No	No	Desconocido	Desconocido	Desconocido	Desconocido
ODS-5	Sí	Sí^[111]	No	Sí	No	Sí	Sí	Sí	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido
UDF	Sí	Sí	Sí^[95]	Sí^[95]	Sí	Sí	No	No	Sí	No	No	No	No	Desconocido
VxFS	Sí	Sí	Sí	No	Sí	Sí	Sí	Sí^[112]	Desconocido	No	Desconocido	Desconocido	Sí	Desconocido
Fossil	No	No	No	No	Sí	Sí	Sí	Sí	No	No	Desconocido	No	Sí^[113]	Desconocido
ZFS	Sí	Sí	Sí^[114]	No^[114]	Sí	Sí	No	Sí	No	Sí	Sí	Sí	Sí	Online (cannot be shrunk)^[115]
VMFS2	Sí	Sí	No	Sí	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
VMFS3	Sí	Sí	No	Sí	Sí	Sí	No	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
Btrfs	Sí	Sí	No	No	Sí	Sí	Sí	Sí	No	Planned^[116]	Sí	Sí	Sí (via bedup)^[117]	Online
PramFS	No	Sí	No	No	Sí	Sí	No	No	Sí	No	No	No	No	No
File system	Enlace duros	Enlace simbólicos	Block journaling	Metadata-only journaling	Case-sensitive	Case-preserving	File Change Log	Snapshotting	XIP	Encryption	COW	integrated LVM	Data deduplication	Volumes are resizeable

Políticas de asignación y distribución

File system	Block suballocation	Variable file block size^[118]	Extents	Allocate-on-flush	Archivo dispersos	Transparent compression
CBM DOS	No	Parcial^[119]	No	No	No	No
CP/M filesystem	No	No	Sí	No	Sí	No
Btrfs	Parcial^[120]	No	Sí	Sí	Sí	Sí
DECtape	No	No	No	No	No	No
Level-D	Sí	No	Sí	No	No	No
DOS (GEC)	No	Sí	Sí	No	No	No
OS4000	No	Sí	Sí	No	No	No
V6FS	No	No	No	No	Sí	No
V7FS	No	No	No	No	Sí	No
FAT12	No	No	No	No	No	No^[121]
FAT16	No	No	No	No	No	No^[121]
FAT32	No	No	No	No	No	No
exFAT	Desconocido	No	No	Desconocido	No	No
GFS	Parcial^[122]	No	No	No	Sí	No
HPFS	No	No	Sí	No	No	No
NTFS	Parcial	No	Sí	No	Sí	Parcial^[123]
HFS Plus	No	No	Sí	Sí	No	Sí
FFS	8:1^[124]	No	No	No	Sí	No
UFS1	8:1^[124]	No	No	No	Sí	No
UFS2	8:1^[124]	Sí	No	No	Sí	No
LFS	8:1^[124]	No	No	No	Sí	No
ext2	No^[125]	No	No	No	Sí	No^[126]
ext3	No^[125]	No	No	No	Sí	No
ext3cow	No^[125]	No	No	No	Sí	No
ext4	No^[125]	No	Sí	Sí	Sí	No
Lustre	No	No	Sí	Sí	Sí	No
NILFS	No	No	No	Sí	Sí	No
ReiserFS	Sí	No	No	No	Sí	No
Reiser4	Sí	No	Sí^[127]	Sí	Sí	Sí^[101]
OCFS	No	No	Sí	No	Desconocido	No
OCFS2	No	No	Sí	No	Sí	No
Reliance	No	No	No	No	No	No
Reliance Nitro	No	No	Sí	No	Sí	No
XFS	No	No	Sí	Sí	Sí	No
JFS	Sí	No	Sí	No	Sí	only in JFS1 on AIX^[128]
QFS	Sí	No	No	No	Desconocido	No
BFS	No	No	Sí	No	Desconocido	No
NSS	No	No	Sí	No	Desconocido	Sí
NWFS	Sí^[129]	No	No	No	Desconocido	Sí
ODS-5	No	No	Sí	No	Desconocido	No
VxFS	Desconocido	No	Sí	No	Sí	No
UDF	No	No	Sí	Depende^[130]	No	No
Fossil	No	No	No	No	Desconocido	Sí
VMFS2	Sí	No	No	No	Sí	No
VMFS3	Sí	No	Sí	No	Sí	No
ZFS	Parcial^[131]	Sí	No	Sí	Sí	Sí
PramFS	No	No	No	No	Sí	No
File system	Block suballocation	Variable file block size^[118]	Extents	Allocate-on-flush	Archivo dispersos	Transparent compression

Soporte de sistemas operativos

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
FAT12	Sí	Sí	Sí	Sí	Sí	Sí	Sí	Sí	No	Parcial on diskettes only, through dos* commands	Desconocido	Sí	Sí^[132]	Desconocido	Sí^[133]	Desconocido
FAT16	Sí since DOS 3.0, FAT16B since DOS 3.31	Sí	Sí	Sí	Sí	Sí	Sí	Sí	Sí	Parcial on diskettes only, through dos* commands	Desconocido	Sí	Sí^[132]	Sí	Sí^[133]	Desconocido
FAT32	Sí since DOS 7.1^{[n 17]}	Sí since Windows 95 OSR2	Sí since Windows 2000	Sí	Sí	Sí	Sí	Sí	Sí	Parcial on diskettes only, through dos* commands	Desconocido	with third-party app^[134]	Sí^[132]	Sí	Sí^[133]	Desconocido
exFAT	No	Parcial read-only with third party driver	Sí: Win7, Vista SP1, can be added to XP SP2	with third party driver	No	Sí 10.6.5+	No	No	Sí	No	No	No	Sí	No	Desconocido	Desconocido
NTFS	with third-party driver	with third-party driver^[135]	Sí	Sí Kernel 2.2 or newer, or with NTFS-3G or ntfsprogs	with NTFS-3G or MacFUSE	Parcial: read-only (read-write with NTFS-3G)	with NTFS-3G	with NTFS-3G	with NTFS-3G on Opensolaris	Desconocido	Desconocido	Parcial read-only third-party driver^[136]	with 3rd-party driver^[137]	No	Desconocido	Desconocido
HFS	No	with third-party app^[138]	with third-party app^[138]	Sí	Sí	Parcial: read-only since OSX 10.6^[139]	with third-party app^[140]^[141]	Desconocido	Desconocido	Desconocido	No	with third-party app^[142]	No	No	No	Desconocido
HFS Plus	No	with third-party app^[138]	with third-party app^[138]	Parcial - write support occurs if journal is empty, but requires a force mount.	Sí since Mac OS 8.1	Sí	Parcial read-only third-party app^[143]	Desconocido	Desconocido	Desconocido	No	with third-party app	No	No	No	Desconocido
HPFS	with third-party driver	Parcial read-only third-party driver^[144]	included until v3.51, third-party driver until 4.0^[145]	Sí	No	Desconocido	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Sí	No	Desconocido	Desconocido	Desconocido
FFS	No	Desconocido	Desconocido	Sí^[146]	No	Sí	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
UFS1	No	Desconocido	Desconocido	Parcial - read only	No	Sí	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	Desconocido
UFS2	No	Desconocido	Desconocido	Parcial - read only	No	No	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	Desconocido
ext2	Desconocido	Desconocido	with Ext2Fsd (complete)^[147] or Ext2 IFS (partial, no large inodes)^[148] or Ext2Read (read-only, also on LVM2)^[149]	Sí	No	with fuse-ext2,^[150] ExtFS^[151] and ext2fsx^[152]	Sí	Desconocido	Desconocido	Desconocido	Desconocido	third-party app^[153]	with 3rd-party app^[154]	with 3rd-party app^[154]	Desconocido	Desconocido
ext3	Desconocido	Desconocido	with Ext2Fsd (complete)^[147] or Ext2 IFS (partial, no large inodes)^[148] or Ext2Read (read-only, also on LVM2)^[149]	Sí	No	with fuse-ext2^[150] and ExtFS^[151]	Sí	Desconocido	Sí	Desconocido	Desconocido	Desconocido	with 3rd-party app^[154]	with 3rd-party app^[154]	Desconocido	Desconocido
ext3cow	Desconocido	Desconocido	Desconocido	Sí Kernel 2.6.20	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
ext4	No	No	with Ext2Fsd (partial, extents limited)^[147] or Ext2Read (read-only, also on LVM2)^[149]	Sí since kernel 2.6.28	No	with fuse-ext2 (partial)^[150] and ExtFS (full read/write)^[151]	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	Desconocido	Desconocido	Desconocido
Btrfs	No	No	No	Sí	No	No	No	No	No	No	No	No	No	No	Desconocido	Desconocido
ZFS	No	No	No	with 3rd Party kernel module^[155] or FUSE^[156]	No	with free 3rd-party software^[157]	Sí	No	Sí	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido
Lustre	No	No	Parcial - en desarrollo^[158]	Sí^[159]	No	Parcial - via FUSE	Parcial - via FUSE	No	Parcial - under development^[160]	No	No	No	No	No	Desconocido	Desconocido
GFS	No	Desconocido	Desconocido	Sí	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
NILFS	No	Desconocido	Desconocido	Sí since kernel 2.6.30	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
ReiserFS	No	Desconocido	Parcial with third-party app	Sí	No	No	Parcial - read only	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	with 3rd-party app^[154]	with 3rd-party app^[154]	Desconocido	Desconocido
Reiser4	No	Desconocido	Desconocido	with a kernel patch	No	No	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
OCFS	No	Desconocido	Desconocido	Sí	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
OCFS2	No	Desconocido	Desconocido	Sí	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
Reliance	No	No	No	No	No	No	No	No	No	No	No	No	Sí	No	Sí	Desconocido
Reliance Nitro	No	No	No	Sí	No	No	No	No	No	No	No	No	Sí	Sí	Sí	Desconocido
XFS	No	Desconocido	Desconocido	Sí	No	Desconocido	Parcial	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
JFS	No	Desconocido	Desconocido	Sí	No	No	No	Desconocido	Desconocido	Sí	Desconocido	Sí	No	No	Desconocido
QFS	No	Desconocido	Desconocido	via client software^[161]	No	Desconocido	No	Desconocido	Sí	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
BFS	No	Desconocido	Desconocido	Parcial - read-only	No	Desconocido	No	Sí	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
NSS	Desconocido	Desconocido	Desconocido	with Novell OES2^{[cita requerida]}	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
NWFS	Desconocido	Desconocido	Desconocido	via ncpfs client software^[162]	No	Desconocido	Sí	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
UDF	Desconocido	Parcial read-only support of UDF 1.02 since Win98 and WinME	Sí^[163]	Sí	Sí since Mac OS 9	Sí	Sí	Desconocido	Sí	Desconocido	Desconocido	Desconocido	Sí	Desconocido	Desconocido	Desconocido
VxFS	No	Desconocido	Desconocido	Sí	No	Desconocido	No	Desconocido	Sí	Sí	Desconocido	Desconocido	No	No	Desconocido	Sí
Fossil	No	No	No	No	No	No	No	No	No	No	No	No	No	No	No	Desconocido
IBM HFS	No	No	No	No	No	No	No	No	No	No	Sí	No	Desconocido	Desconocido	Desconocido	Desconocido
IBM zFS	No	No	No	No	No	No	No	No	No	No	Sí	No	Desconocido	Desconocido	Desconocido	Desconocido
IBM GPFS^[164]	No	No	Sí	Sí	No	No	No	No	No	Sí	No	No	Desconocido	Desconocido	Desconocido	Desconocido
VMFS2	Desconocido	Desconocido	Desconocido	Desconocido	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
VMFS3	No	Desconocido	Desconocido	Parcial read-only with vmfs^[165]	Desconocido	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
DECtape	No	Desconocido	Desconocido	with AncientFS^[166]	No	with AncientFS^[166]	with AncientFS^[166]	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
Level-D	No	Desconocido	Desconocido	Desconocido	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
RT-11	No	Desconocido	Desconocido	Desconocido	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Sí	Desconocido
ODS-2	No	Desconocido	Desconocido	Parcial read-only with tool or kernel module^[167]	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
ODS-5	No	Desconocido	Desconocido	Parcial read-only with kernel module^[167]	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido
LFS	No	Desconocido	Desconocido	with logfs^[168] and others	No	Desconocido	No	Desconocido	Desconocido	Desconocido	Desconocido	Desconocido	No	No	Desconocido	Desconocido
LTFS	No	Desconocido	Desconocido	Sí	No	Sí	No	No	No	No	No	No	No	No	Desconocido	Desconocido
PramFS	No	No	No	Sí	No	No	No	No	No	No	No	No	No	No	No	No
File system	DOS	Windows 9x	Windows NT	Linux	Mac OS	Mac OS X	FreeBSD	BeOS	Solaris	AIX	z/OS	OS/2	Windows CE	Windows Mobile	VxWorks	HP-UX

Véase también

Notas

↑ 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.
↑ 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.
↑ ^a ^b These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; and particular and Sistema operativos 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.
↑ ^a ^b ^c ^d ^e ^f For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 kB for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and Sistema operativos do not support cluster sizes larger than 32 kB).
↑ 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.
↑ 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.
↑ 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: < > [ ].
↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ Depends on whether the FAT12, FAT16, and FAT32 implementation has support for long filenames (LFNs). Where it does not, as in OS/2, MS-DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also do not normally contain lowercase letters. Also note that a few special names (CON, NUL, LPT1) should be avoided, as some operating systems (notably DOS and windows) effectively reserve them.
↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^ñ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae 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.
↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^ñ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai The on-disk structures have no inherent limit. Particular Installable File System drivers and Sistema operativos 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.
↑ 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.
↑ 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 /.
↑ 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.
↑ 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.
↑ ^a ^b NTFS allows files to have multiple names, in separate namespaces: Win32, DOS, Win32&DOS, and Posix. Windows APIs create files with Win32 "long" names (1–255 characters), sometimes with an additional "short"/"alias" DOS name in the "8.3" format (12 characters).
↑ 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.
↑ 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.

Referencias

↑ «Polycenter File System — HELP», Tru64 Unix managers, ORNL .
↑ ^a ^b Specifications for the Reliance file systems are available here [1].
↑ «ProDOS 8 Technical Reference Manual». Consultado el 31 de mayo de 2013.
↑ Beneath Apple ProDOS. Quality Software. 1985. pp. 2-8. ISBN 0-912985-05-4.
↑ ^a ^b «Maximum CP/M-80 2.2 volume size?», comp.os.cpm, Google Groups, consultado el 9 de octubre de 2009 .
↑ «SFS file system». Publib.boulder.ibm.com. Consultado el 5 de febrero de 2013.
↑ See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html
↑ Table "Limits" states a maximum of 255 Unicode characters for the filename [2]
↑ «KB955704». 27 de enero de 2009. «Description of the exFAT file system driver update package [for 32-bit XP]».
↑ «msdn TexFAT File Naming Limitations». 14 de octubre de 2009.
↑ Udo Kuhnt, Luchezar Georgiev, Jeremy Davis (2007). FAT+. FATPLUS.TXT, draft revision 2 ([3], [4]).
↑ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GB. This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use Fdisk from a Windows ME Emergency Boot Disk to avoid. [5]
↑ ^a ^b Richard Russon and Yuval Fledel. «NTFS Documentation». Consultado el 26 de junio de 2011.
↑ ^a ^b «Naming Files, Paths, and Namespaces (MSDN Library article)». NB: This article includes discussion of the NT & Win32 namespaces used by Windows APIs; these are distinct from the NTFS filename namespaces.
↑ ^a ^b This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TB and the file size to 16 TB respectively.«How NTFS Works».
↑ «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. 16 de enero de 2012. Consultado el 5 de febrero de 2013.
↑ 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.
↑ 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.
↑ Docs, Apple .
↑ Docs .
↑ «Interviews/EricSandeen». FedoraProject. 9 de junio de 2008. Consultado el 9 de octubre de 2009.
↑ ext4 1.42 "This release of e2fsprogs has support for file systems > 16 TB"
↑ ^a ^b Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB. For 32-bit 2.6 kernels it is 16 TiB. For 64-bit 2.6 kernels it is 8 EiB.
↑ ReiserFS has a theoretical maximum file size of 1 EiB, but "page cache limits this to 8 TiB on architectures with 32 bit int"[6]
↑ ^a ^b QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.
↑ Varies wildly according to block size and fragmentation of block allocation groups.
↑ ^a ^b NSS allows files to have multiple names, in separate namespaces.
↑ 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.
↑ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
↑ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
↑ This restriction might be lifted in newer versions.
↑ 2³² × block size
↑ ^a ^b ^c ^d ^e «File, file system, and memory size limits in Minix». Minix1.woodhull.com. Consultado el 5 de febrero de 2013.
↑ ^a ^b Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.
↑ ISO 9660#Restrictions
↑ 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/4 GB file size limit
↑ 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.
↑ Joliet Specification
↑ https://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt
↑ «LEAN file system». Freedos-32.sourceforge.net. Consultado el 5 de febrero de 2013.
↑ Note that the filename can be much longer XFS#Extended_attributes
↑ ^a ^b XFS has a limitation under Linux 2.4 of 64 TiB file size, but Linux 2.4 only supports a maximum block size of 2 TiB. This limitation is not present under IRIX.
↑ Implemented in later versions as an extension
↑ ^a ^b Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store file owner information in reserved fields of directory entries on FAT12 and FAT16 volumes, if the optional multi-user security module is loaded. If loaded, most external commands invoke support for special /U:owner/group command line options to deal with this extra information.
↑ ^a ^b Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, DR DOS, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store read/write/delete/execute access permissions and file/directory passwords in reserved fields of directory entries on FAT12 and FAT16 volumes. This is an integral part of the design, therefore passwords can be appended to file or directory names with semicolon (for example: dirname;dirpwd\filename;filepwd), the PASSWORD command can be used to control permissions and some commands support a special /P:pwd option to deal with this feature.
↑ ^a ^b ^c ^d ^e ^f File creation and file access timestamps are supported only by DOS 7.0 and higher, and typically only when explicitly enabled.
↑ ^a ^b ^c Some FAT implementations, such as in Linux, show file modification timestamp (mtime) in the metadata change timestamp (ctime) field. This timestamp is however, not updated on file metadata change.
↑ ^a ^b Particular Installable File System drivers and Sistema operativos 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.
↑ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
↑ 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.
↑ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [7]
↑ «As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See». Trustedbsd.org. Consultado el 5 de febrero de 2013.
↑ ^a ^b ^c ^d Access-control lists and MAC labels are layered on top of extended attributes.
↑ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l Some Installable File System drivers and Sistema operativos 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.
↑ ext4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming
↑ Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
↑ Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
↑ ^a ^b ^c ^d ^e Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
↑ 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.
↑ ^a ^b CRCs are employed for certain types of metadata.
↑ ^a ^b ^c ^d ^e ^f The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
↑ ^a ^b Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.
↑ ^a ^b Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.
↑ Record Management Services (RMS) attributes include record type and size, among many others.
↑ 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.
↑ 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.
↑ 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
↑ ^a ^b Time the file was recorded on the volume always available; "File Creation Date and Time" available only if the file has an Extended Attribute block.
↑ ^a ^b Not applicable to file systems on a read-only medium.
↑ ^a ^b Available only if the file has an Extended Attribute block.
↑ Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
↑ System V Release 4, and some other Unix systems, retrofitted Enlace simbólicos to their versions of the UNIX Versión 7 file system, although the original version didn't support them.
↑ ^a ^b ^c «6», Parted manual, GNU .
↑ Context based symlinks were supported in GFS, GFS2 only supports standard symlinks since the bind mount feature of the Linux VFS has made context based symlinks obsolete
↑ Optional journaling of data
↑ As of Windows Vista, NTFS fully supports 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.
↑ ^a ^b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
↑ While NTFS itself supports case sensitivity, the Win32 environment subsystem cannot create files whose names differ only by case for compatibility reasons. When a file is opened for writing, if there is any existing file whose name is a case-insensitive match for the new file, the existing file is truncated and opened for writing instead of a new file with a different name being created. Other subsystems like e. g. Services for Unix, that operate directly above the kernel and not on top of Win32 can have case-sensitivity.
↑ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
↑ Rick Vanover. «Windows Server 8 data deduplication». Consultado el 2 de diciembre de 2011.
↑ «How to Shrink and Extend NTFS Volumes in Windows». Bleepingcomputer.com. Consultado el 5 de febrero de 2013.
↑ Mac OS System 7 introduced the 'alias', analogous to the POSIX Enlace simbólico 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 Enlace simbólico 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.
↑ «Enlace duros on HFS». Developer.apple.com. Consultado el 5 de febrero de 2013.
↑ 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.
↑ Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS 10.3 on the command newfs_hfs -s will create a case-sensitive new file system. HFS Plus version 5 optionally supports case-sensitivity. However, since case-sensitivity is fundamentally different from case-insensitivity, a new signature was required so existing HFS Plus utilities would not see case-sensitivity as a file system error that needed to be corrected. Since the new signature is 'HX', it is often believed this is a new filesystem instead of a simply an upgraded version of HFS Plus. See Apple's File System Comparisons (which hasn't been updated to discuss HFSX) and Technical Note TN1150: HFS Plus Volume Format (which provides a very technical overview of HFS Plus and HFSX).
↑ 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.
↑ As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.
↑ Since Mac OS X Snow Leopard, online resizing is supported.«How to resize a live partition in Snow Leopard and Lion».
↑ "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.
↑ «OpenBSD growfs(8) manpage». Openbsd.org. 28 de noviembre de 2008. Consultado el 5 de febrero de 2013.
↑ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
↑ Block level journals can be added by using gjournal module in FreeBSD.
↑ «FreeBSD growfs(8) manpage». Freebsd.org. 30 de abril de 2012. Consultado el 5 de febrero de 2013.
↑ ^a ^b ^c ^d UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
↑ Linux kernel versions 2.6.12 and newer.
↑ ^a ^b ^c Offline growing/shrinking as well as online growing: «Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)».
↑ ^a ^b ^c ^d Off by default.
↑ 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
↑ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.^[¿cuál?]
↑ ^a ^b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
↑ OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
↑ ^a ^b File system implements reliability via atomic transactions.
↑ Optionally no on IRIX.
↑ Particular Installable File System drivers and Sistema operativos may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.
↑ [8] (enlace roto disponible en Internet Archive; véase el historial, la primera versión y la última).
↑ ^a ^b ^c ^d Case-sensitivity/Preservation depends on client. Windows, DOS, and OS/2 clients don't see/keep case differences, whereas clients accessing via NFS or AFP may.
↑ ^a ^b The file change logs, last entry change timestamps, and other filesystem metadata, are all part of the extensive suite of auditing capabilities built into NDS/eDirectory called NSure Audit. (Filesystem Events tracked by NSure)
↑ ^a ^b Available only in the "NFS" namespace.
↑ Limited capability. Volumes can span physical disks (volume segment)
↑ ^a ^b These are referred to as "aliases".
↑ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
↑ When used with venti.
↑ ^a ^b ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.
↑ «How to resize ZFS».
↑ McPherson, Amanda (22 de junio de 2009), A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, consultado el 1 de septiembre de 2009 .
↑ Wiki, BTRFS, Deduplication .
↑ ^a ^b Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.
↑ only for.REL (record structured) files, up to 254 bytes/record
↑ Btrfs can only inline files smaller than 3916B with its metadata«Mailing list discussion».
↑ ^a ^b SuperStor in DR DOS 6.0 and PC DOS 6.1, DoubleSpace in MS-DOS 6.0, DriveSpace in MS-DOS 6.22, Windows 95 and Windows 98, and Stacker in Novell DOS 7, OpenDOS 7.01, DR-DOS 7.02/7.03 and PC DOS 7.0/2000 were compresión de datos schemes for FAT.
↑ Only for "stuffed" inodes
↑ Only if formatted with 4kB-sized clusters or smaller
↑ ^a ^b ^c ^d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
↑ ^a ^b ^c ^d Fragments were planned, but never actually implemented on ext2 and ext3.
↑ 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.
↑ In "extents" mode.
↑ «AIX documentation: JFS compresión de datos». IBM.
↑ Each possible size (in sectors) of file tail has a corresponding suballocation block chain in which all the tails of that size are stored. The overhead of managing suballocation block chains is usually less than the amount of block overhead saved by being able to increase the block size but the process is less efficient if there is not much free disk space.
↑ Depends on UDF implementation.
↑ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
↑ ^a ^b ^c Files, Databases, and Persistent Storage. MSDN.
↑ ^a ^b ^c Via dosFs.
↑ «OS/2 and eComstation FAT32 Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
↑ «NTFS for Windows 98». Download.chip.eu. Consultado el 5 de febrero de 2013.
↑ «OS/2 NTFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
↑ Tuxera NTFS for Windows CE. See «article». Archivado desde el original el 18 de septiembre de 2012. and announcement.
↑ ^a ^b ^c ^d Cross-platform Drive Solutions. «Sharing Disks - Windows Products». Macwindows.com. Consultado el 5 de febrero de 2013.
↑ Gagne, Ken (31 de agosto de 2009). «Losing legacy data to Snow Leopard». Computerworld. Consultado el 7 de septiembre de 2009.
↑ «hfsutils at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.
↑ «hfs at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.
↑ «OS/2 HFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
↑ «Catacombae HFSExplorer». Hem.bredband.net. Consultado el 5 de febrero de 2013.
↑ «DOS/Win 9x HPFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
↑ Win NT 4.0 HPFS Driver
↑ «How to mount FFS partition under Linux - NetBSD Wiki». Wiki.netbsd.se. Archivado desde el original el 19 de marzo de 2008. Consultado el 9 de octubre de 2009.
↑ ^a ^b ^c Ext2Fsd is an open source ext2/ext3/ext4 kernel-level file system driver for Windows systems (NT/2K/XP/VISTA/7, X86/AMD64) that provides both read/write access to the file system. Currently, does not fully support extents (no size truncating/extending, no file deletion), a default feature of ext4. [9]
↑ ^a ^b Ext2 IFS for Windows provides kernel-level read/write access to ext2 and ext3 volumes in Windows NT4, 2000, XP, Vista and Windows 2008. Does not support inodes size above 128 bytes and does not support ext4.[10]
↑ ^a ^b ^c Ext2Read is an explorer-like utility to explore ext2/ext3/ext4 file systems that provides read-only access to the file system. It supports extents, large inodes, and LVM2 volumes.Ext2Read
↑ ^a ^b ^c Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[11]
↑ ^a ^b ^c Paragon ExtFS for Mac is a low-level file system driver specially developed to bridge file system incompatibility between Linux and Mac by providing full read/write access to the Ext2, Ext3 and Ext4 file systems under Mac OS X.[12]
↑ Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[13]
↑ OS/2 ext2 Driver
↑ ^a ^b ^c ^d ^e ^f See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
↑ Native ZFS for Linux
↑ ZFS on FUSE
↑ Mac ZFS
↑ http://wiki.lustre.org/index.php/Windows_Native_Client
↑ http://wiki.lustre.org/index.php?title=Main_Page
↑ http://wiki.lustre.org/index.php/FAQ_-_OS_Support
↑ Using SAM-QFS on Linux Clients
↑ ncpfs
↑ «Understanding the difference between the Live File System and Mastered disc formats». Which CD or DVD format should I use?. Microsoft. Consultado el 22 de noviembre de 2008.
↑ [14]
↑ vmfs
↑ ^a ^b ^c AncientFS
↑ ^a ^b VMS2Linux
↑ logfs

Enlaces externos

Datos: Q2370201

[note-11-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.

[note-10-3] Microsoft first introduced FAT32 in Windows 95 OSR2 (OEM Service Release 2) and then later in Windows 98. NT-based Windows did not have any support for FAT32 up to Windows NT4; Windows 2000 was the first NT-based Windows OS that received the ability to work with it.

[note-25-5] 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 Sistema operativos 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.

[note-4-6] ↑ ^a ^b ^c ^d ^e ^f For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 kB for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and Sistema operativos do not support cluster sizes larger than 32 kB).

[note-167-7] While the on-disk filesystem structure uses a 4-byte file length, which allows files up to 4G, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum file size to 512M.

[note-168-8] While the on-disk filesystem structure uses a 3-byte sector number, which allows access to 4G of disk space, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum disk size to 512M.

[note-CPMFS-01-11] The CP/M filesystem itself does have limitations in regard to the allowed filename characters to be used, but officially the following characters are not allowed: SPACE < > . , ; : = ? * [ ] % | ( ) / \. CCP reserves the following characters for special purposes: SPACE , = _ . : ;, PIP additionally reserves: < > [ ].

[note-24-14] ↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ Depends on whether the FAT12, FAT16, and FAT32 implementation has support for long filenames (LFNs). Where it does not, as in OS/2, MS-DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also do not normally contain lowercase letters. Also note that a few special names (CON, NUL, LPT1) should be avoided, as some operating systems (notably DOS and windows) effectively reserve them.

[note-26-15] ↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^ñ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae 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.

[note-12-16] ↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l ^m ⁿ ^ñ ^o ^p ^q ^r ^s ^t ^u ^v ^w ^x ^y ^z ^aa ^ab ^ac ^ad ^ae ^af ^ag ^ah ^ai The on-disk structures have no inherent limit. Particular Installable File System drivers and Sistema operativos 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.

[note-58-18] The actual maximum was 1,082,201,088 bytes, with 10 direct blocks, 1 singly indirect block, 1 doubly indirect block, and 1 triply indirect block. The 4.0BSD and 4.1BSD versions, and the System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4 GB.

[osxhfs-24] As Mac OS X is a Unix-like system, which supports : in file names, and which uses / as a pathname component separator, : in file names is represented on disk in HFS and HFS+ as /.

[note-27-25] The "." and ".." directory entries in HPFS that are seen by applications programs are a partial fiction created by the Installable File System drivers. The on-disk data structure for a directory does not contain entries by those names, but instead contains a special "start" entry. Whilst on-disk directory entries by those names are not physically prohibited, they cannot be created in normal operation, and a directory containing such entries is corrupt.

[note-13-26] This is the limit of the on-disk structures. The HPFS Installable File System driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64 GB.

[note-171-27] 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).

[note-174-30] In the Win32 namespace, any UTF-16 code unit (case insensitive) except NUL and \ / : * ? " < > | is allowed; in the Posix namespace, any UTF-16 code unit (case sensitive) except NUL and / is allowed; in the DOS namespace, any character in the U+0021–U+007E range except \ / : * ? " < > | is allowed. Windows APIs require Win32 namespace compatibility, which prevents access to folders & files having only Posix names containing Win32-incompatible characters.

[fat32-150] Native FAT32 support with MS-DOS 7.10 and 8.0. Loadable FAT32 support for any DOS since 3.31 with DRFAT32 redirector driver. Native FAT32 support since OEM DR-DOS 7.04, bootable FAT32 support since OEM DR-DOS 7.06. Native FAT32 support with OEM PC DOS 7.10.

[ornl_gov_mailinglist-2] «Polycenter File System — HELP», Tru64 Unix managers, ORNL .

[relspec-4] Specifications for the Reliance file systems are available here [1].

[ProDOS_TechRefMan-9] «ProDOS 8 Technical Reference Manual». Consultado el 31 de mayo de 2013.

[AppleProDOS-10] Beneath Apple ProDOS. Quality Software. 1985. pp. 2-8. ISBN 0-912985-05-4.

[note-101-12] «Maximum CP/M-80 2.2 volume size?», comp.os.cpm, Google Groups, consultado el 9 de octubre de 2009 .

[Lib_IBM_SFS_hlp-13] «SFS file system». Publib.boulder.ibm.com. Consultado el 5 de febrero de 2013.

[Man_Stuttgart-17] See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html

[MS_Table_Limits-19] Table "Limits" states a maximum of 255 Unicode characters for the filename [2]

[xpkb-20] «KB955704». 27 de enero de 2009. «Description of the exFAT file system driver update package [for 32-bit XP]».

[texfat-21] «msdn TexFAT File Naming Limitations». 14 de octubre de 2009.

[DRDOS_FAT+_R2-22] Udo Kuhnt, Luchezar Georgiev, Jeremy Davis (2007). FAT+. FATPLUS.TXT, draft revision 2 ([3], [4]).

[note-7-23] While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GB. This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use Fdisk from a Windows ME Emergency Boot Disk to avoid. [5]

[note-172-28] Richard Russon and Yuval Fledel. «NTFS Documentation». Consultado el 26 de junio de 2011.

[note-173-29] «Naming Files, Paths, and Namespaces (MSDN Library article)». NB: This article includes discussion of the NT & Win32 namespaces used by Windows APIs; these are distinct from the NTFS filename namespaces.

[note-55-31] 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».

[REFS_MSDN_BLOG-32] «MSDN Blogs - Resilient File System, Windows 8 RC's filename length reduced (from 32K to 255) with Windows 8 RTM for NTFS compatibility». Blogs.msdn.com. 16 de enero de 2012. Consultado el 5 de febrero de 2013.

[note-1-33] The Mac OS provides two sets of functions to retrieve file names from an HFS Plus volume, one of them returning the full Unicode names, the other shortened names fitting in the older 31 byte limit to accommodate older applications.

[note-2-34] HFS Plus mandates support for an escape sequence to allow arbitrary Unicode. Users of older software might see the escape sequences instead of the desired characters.

[note-71-35] Docs, Apple .

[36] Docs .

[ext4-features-37] «Interviews/EricSandeen». FedoraProject. 9 de junio de 2008. Consultado el 9 de octubre de 2009.

[38] xt4 1.42 "This release of e2fsprogs has support for file systems > 16 TB"

[note-63-39] Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB. For 32-bit 2.6 kernels it is 16 TiB. For 64-bit 2.6 kernels it is 8 EiB.

[note-8-40] ReiserFS has a theoretical maximum file size of 1 EiB, but "page cache limits this to 8 TiB on architectures with 32 bit int"[6]

[note-72-41] 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.

[note-3-42] Varies wildly according to block size and fragmentation of block allocation groups.

[note-28-43] NSS allows files to have multiple names, in separate namespaces.

[note-52-44] Some namespaces had lower name length limits. "LONG" had an 80-byte limit, "NWFS" 80 bytes, "NFS" 40 bytes and "DOS" imposed 8.3 filename.

[note-15-45] Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.

[note-16-46] Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.

[note-43-47] This restriction might be lifted in newer versions.

[48] 2³² × block size

[minix-filesize-49] «File, file system, and memory size limits in Minix». Minix1.woodhull.com. Consultado el 5 de febrero de 2013.

[note-74-50] Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.

[51] ISO 9660#Restrictions

[52] Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB in size. See ISO 9660#The 2/4 GB file size limit

[53] Assuming the typical 2048 byte sector size. The volume size is specified as a 32-bit value identifying the number of sectors on the volume.

[54] Joliet Specification

[55] ttps://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt

[56] «LEAN file system». Freedos-32.sourceforge.net. Consultado el 5 de febrero de 2013.

[57] Note that the filename can be much longer XFS#Extended_attributes

[note-9-58] XFS has a limitation under Linux 2.4 of 64 TiB file size, but Linux 2.4 only supports a maximum block size of 2 TiB. This limitation is not present under IRIX.

[59] Implemented in later versions as an extension

[fat-owner-60] 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.

[fat-permissions-61] 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.

[fat-cstamp-62] ↑ ^a ^b ^c ^d ^e ^f File creation and file access timestamps are supported only by DOS 7.0 and higher, and typically only when explicitly enabled.

[fat-ctime-63] 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.

[note-22-64] Particular Installable File System drivers and Sistema operativos 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.

[note-14-65] The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.

[note-5-66] NTFS access control lists can express any access policy possible using simple POSIX file permissions (and far more), but use of a POSIX-like interface is not supported without an add-on such as Services for UNIX or Cygwin.

[note-92-67] As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [7]

[68] «As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See». Trustedbsd.org. Consultado el 5 de febrero de 2013.

[note-33-69] Access-control lists and MAC labels are layered on top of extended attributes.

[note-32-70] Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).

[note-23-71] ↑ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j ^k ^l Some Installable File System drivers and Sistema operativos may not support extended attributes, access control lists or security labels on these filesystems. Linux kernels prior to 2.6.x may either be missing support for these altogether or require a patch.

[72] xt4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming

[lustre-crtime-73] Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.

[lustre-cksum-74] Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data

[lustre-zfs-75] Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.

[76] s2 computes and validates checksums of metadata objects like inodes and directories. It also stores an error correction code capable to fixing single-bite errors.

[relcrc-77] CRCs are employed for certain types of metadata.

[note-31-78] ↑ ^a ^b ^c ^d ^e ^f The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.

[note-19-79] 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.

[note-29-80] 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.

[note-17-81] Record Management Services (RMS) attributes include record type and size, among many others.

[note-61-82] File permission in 9P are a variation of the traditional Unix permissions with some minor changes, e.g. the suid bit is replaced by a new 'exclusive access' bit.

[note-69-83] MAC/Sensitivity labels are per filesystem. A label per file are not out of the question as a future compatible change but aren't part of any available version of ZFS.

[note-60-84] Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS. ZFS also has "system attributes" used for storing MS-DOS/NTFS compatible attributes for use by CIFS; as well as some attributes ported from FreeBSD

[9660crtime-85] 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.

[9660atime-86] Not applicable to file systems on a read-only medium.

[9660mtime-87] Available only if the file has an Extended Attribute block.

[88] Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.

[note-59-89] System V Release 4, and some other Unix systems, retrofitted Enlace simbólicos to their versions of the UNIX Versión 7 file system, although the original version didn't support them.

[parted-resize-90] «6», Parted manual, GNU .

[91] Context based symlinks were supported in GFS, GFS2 only supports standard symlinks since the bind mount feature of the Linux VFS has made context based symlinks obsolete

[92] Optional journaling of data

[note-34-93] As of Windows Vista, NTFS fully supports soft links. See this Microsoft article on Vista kernel improvements. NTFS 5.0 (Windows 2000) and higher can create junctions, which allow any valid local directory (but not individual files) ("target" of junction) to be mapped to an NTFS version thereof ("source" = location of junction). The source directory must lie on an NTFS 5+ partition, but the target directory can lie on any valid local partition and needn't be NTFS. Junctions are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.

[note-37-94] NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.

[note-36-95] While NTFS itself supports case sensitivity, the Win32 environment subsystem cannot create files whose names differ only by case for compatibility reasons. When a file is opened for writing, if there is any existing file whose name is a case-insensitive match for the new file, the existing file is truncated and opened for writing instead of a new file with a different name being created. Other subsystems like e. g. Services for Unix, that operate directly above the kernel and not on top of Win32 can have case-sensitivity.

[note-93-96] NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.

[singleinstancestorage-97] Rick Vanover. «Windows Server 8 data deduplication». Consultado el 2 de diciembre de 2011.

[ntfs-shrink-98] «How to Shrink and Extend NTFS Volumes in Windows». Bleepingcomputer.com. Consultado el 5 de febrero de 2013.

[note-HFS-alias-99] Mac OS System 7 introduced the 'alias', analogous to the POSIX Enlace simbólico 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 Enlace simbólico nature of the link. The Finder displayed their file names in an italic font (at least in Roman scripts), but otherwise they behaved identically to their referent.

[100] «Enlace duros on HFS». Developer.apple.com. Consultado el 5 de febrero de 2013.

[note-48-101] Metadata-only journaling was introduced in the Mac OS 10.2.2 HFS Plus driver; journaling is enabled by default on Mac OS 10.3 and later.

[note-35-102] Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS 10.3 on the command newfs_hfs -s will create a case-sensitive new file system. HFS Plus version 5 optionally supports case-sensitivity. However, since case-sensitivity is fundamentally different from case-insensitivity, a new signature was required so existing HFS Plus utilities would not see case-sensitivity as a file system error that needed to be corrected. Since the new signature is 'HX', it is often believed this is a new filesystem instead of a simply an upgraded version of HFS Plus. See Apple's File System Comparisons (which hasn't been updated to discuss HFSX) and Technical Note TN1150: HFS Plus Volume Format (which provides a very technical overview of HFS Plus and HFSX).

[note-64-103] Mac OS Tiger (10.4) and late versions of Panther (10.3) provide file change logging (it's a feature of the file system software, not of the volume format, actually). See fslogger.

[note-77-104] As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.

[105] Since Mac OS X Snow Leopard, online resizing is supported.«How to resize a live partition in Snow Leopard and Lion».

[note-110-106] "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.

[107] «OpenBSD growfs(8) manpage». Openbsd.org. 28 de noviembre de 2008. Consultado el 5 de febrero de 2013.

[note-66-108] "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).

[note-143-109] Block level journals can be added by using gjournal module in FreeBSD.

[110] «FreeBSD growfs(8) manpage». Freebsd.org. 30 de abril de 2012. Consultado el 5 de febrero de 2013.

[note-38-111] UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.

[note-65-112] Linux kernel versions 2.6.12 and newer.

[resize2fs-113] Offline growing/shrinking as well as online growing: «Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)».

[note-62-114] Off by default.

[lustre-shrink-115] Can be shrunk online by migrating files off an OST and removing the OST, or offline with ext3/4 backing filesystems by shrinking the OST filesystem

[note-44-116] Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.^[¿cuál?]

[note-50-117] Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.

[118] OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.

[reltrans-119] File system implements reliability via atomic transactions.

[note-40-120] Optionally no on IRIX.

[note-30-121] Particular Installable File System drivers and Sistema operativos may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.

[linux-resizing-122] [8] (enlace roto disponible en Internet Archive; véase el historial, la primera versión y la última).

[note-20-123] 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.

[note-6-124] 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)

[note-53-125] Available only in the "NFS" namespace.

[note-99-126] Limited capability. Volumes can span physical disks (volume segment)

[note-18-127] These are referred to as "aliases".

[note-70-128] VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.

[fossil+venti-129] When used with venti.

[note-56-130] ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.

[131] «How to resize ZFS».

[CM090622-132] McPherson, Amanda (22 de junio de 2009), A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, consultado el 1 de septiembre de 2009 .

[BtrfsWikiDedup-133] Wiki, BTRFS, Deduplication .

[note-41-134] Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.

[135] y for.REL (record structured) files, up to 254 bytes/record

[Btrfs_tail_packing-136] Btrfs can only inline files smaller than 3916B with its metadata«Mailing list discussion».

[note-51-137] 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 compresión de datos schemes for FAT.

[138] Only for "stuffed" inodes

[139] Only if formatted with 4kB-sized clusters or smaller

[note-45-140] Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.

[note-47-141] Fragments were planned, but never actually implemented on ext2 and ext3.

[note-49-142] 2compr, 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.

[note-39-143] In "extents" mode.

[144] «AIX documentation: JFS compresión de datos». IBM.

[note-42-145] 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.

[note-46-146] Depends on UDF implementation.

[note-68-147] When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.

[wince_fdps-148] Files, Databases, and Persistent Storage. MSDN.

[vxworks_dosfs-149] Via dosFs.

[OS/2_and_eComstation_FAT32_Driver-151] «OS/2 and eComstation FAT32 Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.

[NTFS_for_Windows_98-152] «NTFS for Windows 98». Download.chip.eu. Consultado el 5 de febrero de 2013.

[OS/2_NTFS_Driver-153] «OS/2 NTFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.

[154] Tuxera NTFS for Windows CE. See «article». Archivado desde el original el 18 de septiembre de 2012. and announcement.

[Sharing_Disks-155] Cross-platform Drive Solutions. «Sharing Disks - Windows Products». Macwindows.com. Consultado el 5 de febrero de 2013.

[OS_X_read-only_support-156] Gagne, Ken (31 de agosto de 2009). «Losing legacy data to Snow Leopard». Computerworld. Consultado el 7 de septiembre de 2009.

[hfsutils-157] «hfsutils at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.

[hfs-158] «hfs at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.

[OS/2_HFS_Driver-159] «OS/2 HFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.

[HFSExplorer-160] «Catacombae HFSExplorer». Hem.bredband.net. Consultado el 5 de febrero de 2013.

[DOS/Win9x_HPFS_Driver-161] «DOS/Win 9x HPFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.

[Win_NT_4.0_HPFS_Driver-162] Win NT 4.0 HPFS Driver

[How_to_mount_FFS_partition_under_Linux-163] «How to mount FFS partition under Linux - NetBSD Wiki». Wiki.netbsd.se. Archivado desde el original el 19 de marzo de 2008. Consultado el 9 de octubre de 2009.

[Ext2Fsd_Driver-164] Ext2Fsd is an open source ext2/ext3/ext4 kernel-level file system driver for Windows systems (NT/2K/XP/VISTA/7, X86/AMD64) that provides both read/write access to the file system. Currently, does not fully support extents (no size truncating/extending, no file deletion), a default feature of ext4. [9]

[Ext2_IFS_for_Windows-165] Ext2 IFS for Windows provides kernel-level read/write access to ext2 and ext3 volumes in Windows NT4, 2000, XP, Vista and Windows 2008. Does not support inodes size above 128 bytes and does not support ext4.[10]

[Ext2Read-166] 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

[fuse-ext2-167] Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[11]

[Paragon_ExtFS_for_Mac_OS_X-168] Paragon ExtFS for Mac is a low-level file system driver specially developed to bridge file system incompatibility between Linux and Mac by providing full read/write access to the Ext2, Ext3 and Ext4 file systems under Mac OS X.[12]

[Mac_OS_X_Ext2_Filesystem-169] Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[13]

[OS/2_ext2_Driver-170] OS/2 ext2 Driver

[tcmdr-171] ↑ ^a ^b ^c ^d ^e ^f See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.

[Native_ZFS_for_Linux-172] Native ZFS for Linux

[zfs_on_fuse-173] ZFS on FUSE

[Mac_ZFS-174] Mac ZFS

[lustre-wnc-175] ttp://wiki.lustre.org/index.php/Windows_Native_Client

[lustre-176] ttp://wiki.lustre.org/index.php?title=Main_Page

[lustre-sol-177] ttp://wiki.lustre.org/index.php/FAQ_-_OS_Support

[Using+SAM-QFS+on+Linux+Clients-178] Using SAM-QFS on Linux Clients

[ncpfs-179] s

[180] «Understanding the difference between the Live File System and Mastered disc formats». Which CD or DVD format should I use?. Microsoft. Consultado el 22 de noviembre de 2008.

[GPFS_OS_Support-181] [14]

[vmfs-182] vmfs

[ancientfs-183] AncientFS

[VMS2Linux-184] VMS2Linux

[logfs-185] s

[n 1]

[1]

[n 2]

[2]

[n 3]

[n 4]

[n 5]

[n 6]

[3]

[4]

[n 7]

[5]

[6]

[n 8]

[n 9]

[n 10]

[7]

[n 11]

[8]

[9]

[10]

[11]

[12]

[n 12]

[n 13]

[n 14]

[n 15]

[13]

[14]

[n 16]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

[26]

[27]

[28]

[29]

[30]

[31]

[32]

[33]

[34]

[35]

[36]

[37]

[38]

[39]

[40]

[41]

[42]

[43]

[44]

[45]

[46]

[47]

[48]

[49]

[50]

[51]

[52]

[53]

[54]

[55]

[56]

[57]

[58]

[59]

[60]

[61]

[62]

[63]

[64]

[65]

[66]

[67]

[68]

[69]

[70]

[71]

[72]

[73]

[74]

[75]

[76]

[77]

[78]

[79]

[80]

[81]

[82]

[83]

[84]