Anexo:Comparación de sistemas de archivos

De Wikipedia, la enciclopedia libre
Saltar a: navegación, búsqueda

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

Información general[editar]

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[editar]

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 (235-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 EiB[15] 16 EiB[15]
ReFS &0000000000065536.000000255 unicode characters[16] Desconocido KiB 16 EiB 256 ZiB with 16 KiB cluster size (264 × 16 × 210). 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] 8 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[editar]

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 [43] No Desconocido Desconocido No No No No No No Desconocido
DECtape No No 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 Desconocido
Level-D Desconocido Desconocido No No No Desconocido
RT-11 No No No No No No No No No No No Desconocido
DOS (GEC) No Desconocido No No No No No No Desconocido
OS4000 No Desconocido No No No No No No Desconocido
V6FS No Desconocido No No No No No Desconocido
V7FS No Desconocido No No No No No Desconocido
FAT12 No[44] No[45] Parcial[46] Parcial[46] No[47] No No No No[48] No 10 milliseconds
FAT16 No[44] No[45] Parcial[46] Parcial[46] No[47] No No No No[48] No 10 milliseconds
FAT32 No No Parcial[46] Parcial[46] No[47] No No No No No 10 milliseconds
exFAT No No No Desconocido No No Desconocido Desconocido Parcial 10 milliseconds
HPFS [49] No Desconocido No No No Desconocido No Desconocido
NTFS [50] No No [51] No 100 nanoseconds
HFS No No No No No No No No Desconocido
HFS Plus No [52] No 1 second
FFS No Desconocido No No No No No Desconocido
UFS1 No Desconocido No [53] [53] No[54] No Desconocido
UFS2 Desconocido No [53] [53] No Desconocido
LFS No Desconocido No No No No No Desconocido
ext2 No Desconocido No [55] [55] No 1 second
ext3 No No No [55] [55] No 1 second
ext3cow No No No [55] [55] No 1 second
ext4 Desconocido No [55] [55] Parcial[56] 1 nanosecond
Lustre Parcial[57] No No Parcial[58] [59] Desconocido
GPFS Desconocido No Desconocido
GFS No Desconocido Desconocido No [55] [55] No Desconocido
NILFS No Desconocido Desconocido No Planned No Planned Desconocido
ReiserFS No No No No No No No No Desconocido
Reiser4 No Desconocido No No No No No Desconocido
OCFS No No No Desconocido Desconocido No No No No Desconocido
OCFS2 No Desconocido Desconocido No No Parcial[60] Desconocido
Reliance No No No No No No No No No Parcial[61] Desconocido
Reliance Nitro Linux port Linux port No No No Linux port No Parcial[61] Desconocido
XFS No Desconocido No [55] Parcial 1 nanosecond
JFS Desconocido No No Desconocido
QFS Desconocido Desconocido No No Desconocido
BFS No Desconocido Desconocido No No No No No Desconocido
AdvFS No Desconocido No No No Desconocido
NSS [62] [62] Desconocido Desconocido [62] Desconocido [63] [64] No Desconocido
NWFS Desconocido [62] [62] Desconocido Desconocido [62] Desconocido [63] [64] No Desconocido
ODS-5 Desconocido Desconocido Desconocido Desconocido Desconocido [65] No Desconocido
VxFS Desconocido No Desconocido [55] No Desconocido
UDF Desconocido Desconocido No No Desconocido
Fossil [66] No Desconocido Desconocido No No No No No Desconocido
ZFS Desconocido [67] [68] Desconocido
VMFS2 No Desconocido Desconocido No No No No No Desconocido
VMFS3 No Desconocido Desconocido No No No No No Desconocido
ISO 9660:1988 No No [69] No[70] [71] Desconocido No No No No No No Desconocido
Joliet ("CDFS") No No [69] No[70] [71] Desconocido No No No No No No Desconocido
ISO 9660:1999 No No No Desconocido Desconocido No No No No No No Desconocido
High Sierra No No No Desconocido Desconocido No No No No No No Desconocido
Btrfs Desconocido Desconocido 1 nanosecond
Lanyard Filesystem No No No No No No No No No 1 nanosecond
PramFS No Desconocido No 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[editar]

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 No No No No No No No Parcial Offline (cannot be shrunk)
CBM DOS No No No No 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 [72] No No No No No No No No No No No Desconocido
V6FS No No No No No No No No No No Desconocido
V7FS No[73] No No No No No No No No No Desconocido
FAT12 No No No No No Parcial No No No No No No No Parcial Offline[74]
FAT16 No No No No No Parcial No No No No No No No Parcial Offline[74]
FAT32 No No No No No Parcial No No No No No No No Parcial Offline[74]
exFAT No No Desconocido No No No Desconocido Desconocido No Desconocido Desconocido Desconocido Desconocido
GFS [75] [76] No No No No Desconocido Desconocido Desconocido Sí Online
GPFS Desconocido Desconocido No No Sí Online
HAMMER Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Sí On demand Desconocido
HPFS No No No No No No Desconocido No No Desconocido Desconocido No Desconocido
NTFS [77] No[78] [78] [79] Parcial[80] Parcial Desconocido Sí (Windows Server 2012)[81] Sí Online[82]
HFS No [83] No No No No No No No No No No Desconocido
HFS Plus [84] No [85] Parcial[86] [87] No No [88] No No No [89]
FFS No No[90] No No No No No No No Parcial Offline (cannot be shrunk)[91]
UFS1 No No No No No No No No No Desconocido
UFS2 No No[92] [93] No Desconocido No No No No Parcial Offline (cannot be shrunk)[94]
LFS [95] No No No No No Desconocido Desconocido Desconocido Desconocido
ext2 No No No No [96] No No No No Sí Online[97]
ext3 [98] No No No No No Sí Online[97]
ext3cow [98] Desconocido Desconocido No No Desconocido
ext4 [98] No No No No No Sí Online[97]
Lustre [98] Sí in 2.0 and later No[59] No No No[59] No[59] No[59] Sí Online[99]
NILFS [95] No No No Desconocido Desconocido Sí Online (since Linux-3.x and nilfs-utils 2.1)
ReiserFS No[100] No No No No No No No Sí Online
Reiser4 No No Desconocido No [101] No Desconocido Sí Online (can only be shrunk offline)
OCFS No No No No No No No Desconocido Desconocido Desconocido Desconocido
OCFS2 No Parcial[102] No No Desconocido No No Sí Online for version 1.4 and higher
Reliance No No No[103] No No No No No No No No Desconocido
Reliance Nitro No[103] No Depende del sistema operativo No No No No No No Desconocido
XFS [104] No No No No No No No Sí Online (cannot be shrunk)
JFS No [105] No No No No Desconocido Desconocido Sí Online (cannot be shrunk)[106]
QFS No No No No No Desconocido Desconocido Desconocido Desconocido
Be File System No Desconocido No No No No No No Desconocido
NSS Desconocido [107] [107] [108] No Desconocido Desconocido Desconocido Desconocido
NWFS [109] [109] No No [107] [107] [108] Desconocido No No No [110] Desconocido Desconocido
ODS-2 [111] No No No No No Desconocido Desconocido Desconocido Desconocido
ODS-5 [111] No No Desconocido No Desconocido Desconocido Desconocido Desconocido
UDF [95] [95] No No No No No No Desconocido
VxFS No [112] Desconocido No Desconocido Desconocido Desconocido
Fossil No No No No No No Desconocido No [113] Desconocido
ZFS [114] No[114] No No Sí Online (cannot be shrunk)[115]
VMFS2 No No No No No Desconocido Desconocido Desconocido Desconocido
VMFS3 No No No No No Desconocido Desconocido Desconocido Desconocido
Btrfs No No No Planned[116] Sí (via bedup)[117] Sí Online
PramFS No No No No No 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[editar]

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 No No
Btrfs Parcial[120] No
DECtape No No No No No No
Level-D No No No No
DOS (GEC) No No No No
OS4000 No No No No
V6FS No No No No No
V7FS No No No No 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 No
HPFS No No No No No
NTFS Parcial No No Parcial[123]
HFS Plus No No No
FFS 8:1[124] No No No No
UFS1 8:1[124] No No No No
UFS2 8:1[124] No No No
LFS 8:1[124] No No No No
ext2 No[125] No No No No[126]
ext3 No[125] No No No No
ext3cow No[125] No No No No
ext4 No[125] No No
Lustre No No No
NILFS No No No No
ReiserFS No No No No
Reiser4 No [127] [101]
OCFS No No No Desconocido No
OCFS2 No No No No
Reliance No No No No No No
Reliance Nitro No No No No
XFS No No No
JFS No No only in JFS1 on AIX[128]
QFS No No No Desconocido No
BFS No No No Desconocido No
NSS No No No Desconocido
NWFS [129] No No No Desconocido
ODS-5 No No No Desconocido No
VxFS Desconocido No No No
UDF No No Depende[130] No No
Fossil No No No No Desconocido
VMFS2 No No No No
VMFS3 No No No
ZFS Parcial[131] No
PramFS No No No No No
File system Block suballocation Variable file block size[118] Extents Allocate-on-flush Archivo dispersos Transparent compression

Soporte de sistemas operativos[editar]

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 No Parcial on diskettes only, through dos* commands Desconocido [132] Desconocido [133] Desconocido
FAT16 Sí since DOS 3.0, FAT16B since DOS 3.31 Parcial on diskettes only, through dos* commands Desconocido [132] [133] Desconocido
FAT32 Sí since DOS 7.1[n 17] Sí since Windows 95 OSR2 Sí since Windows 2000 Parcial on diskettes only, through dos* commands Desconocido with third-party app[134] [132] [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 No No No No Desconocido Desconocido
NTFS with third-party driver with third-party driver[135] 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] 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 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] No Desconocido Desconocido Desconocido Desconocido Desconocido No Desconocido Desconocido Desconocido
FFS No Desconocido Desconocido [146] No Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido
UFS1 No Desconocido Desconocido Parcial - read only No Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido No Desconocido
UFS2 No Desconocido Desconocido Parcial - read only No No 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] No with fuse-ext2,[150] ExtFS[151] and ext2fsx[152] 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] No with fuse-ext2[150] and ExtFS[151] Desconocido 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 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] No No No No Desconocido Desconocido Desconocido Desconocido
Lustre No No Parcial - en desarrollo[158] [159] No Parcial - via FUSE Parcial - via FUSE No Parcial - under development[160] No No No No No Desconocido Desconocido
GFS No Desconocido Desconocido 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 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 No Desconocido No Desconocido Desconocido Desconocido Desconocido Desconocido No No Desconocido Desconocido
OCFS2 No Desconocido Desconocido 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 No Desconocido
Reliance Nitro No No No No No No No No No No No Desconocido
XFS No Desconocido Desconocido No Desconocido Parcial Desconocido Desconocido Desconocido Desconocido Desconocido No No Desconocido Desconocido
JFS No Desconocido Desconocido No No No Desconocido Desconocido Desconocido No No Desconocido
QFS No Desconocido Desconocido via client software[161] No Desconocido No Desconocido Desconocido Desconocido Desconocido No No Desconocido Desconocido
BFS No Desconocido Desconocido Parcial - read-only No Desconocido No 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 Desconocido Desconocido Desconocido Desconocido Desconocido No No Desconocido Desconocido
UDF Desconocido Parcial read-only support of UDF 1.02 since Win98 and WinME [163] Sí since Mac OS 9 Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido Desconocido
VxFS No Desconocido Desconocido No Desconocido No Desconocido Desconocido Desconocido No No Desconocido
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 No Desconocido Desconocido Desconocido Desconocido
IBM zFS No No No No No No No No No No No Desconocido Desconocido Desconocido Desconocido
IBM GPFS[164] No No No No No No No 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 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 No No No No No No No No No Desconocido Desconocido
PramFS No No No No No No No No No No No No No No No
File system DOS Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2 Windows CE Windows Mobile VxWorks HP-UX

Véase también[editar]

Notas[editar]

  1. IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, ported from OS/2 to AIX and Linux, was first shipped in OS/2 Warp Server for e-Business in 1999. It was released as JFS2 on AIX 5L.
  2. 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.
  3. 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.
  4. 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).
  5. 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.
  6. 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.
  7. 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: < > [ ].
  8. a b c d e f g h i Depends on whether the FAT12, FAT16, and FAT32 implementation has support for long filenames (LFNs). Where it does not, as in OS/2, MS-DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also do not normally contain lowercase letters. Also note that a few special names (CON, NUL, LPT1) should be avoided, as some operating systems (notably DOS and windows) effectively reserve them.
  9. a b c d e f g h i j k l m n ñ o p q r s t u v w x y z aa ab ac ad ae 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.
  10. a b c d e f g h i j k l m n ñ o p q r s t u v w x y z aa ab ac ad ae af ag ah ai 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.
  11. 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.
  12. 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 /.
  13. 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.
  14. 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.
  15. 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).
  16. 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.
  17. 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[editar]

  1. «Polycenter File System — HELP», Tru64 Unix managers, ORNL, http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html 
  2. a b Specifications for the Reliance file systems are available here [1].
  3. «ProDOS 8 Technical Reference Manual». Consultado el 31 de mayo de 2013.
  4. Beneath Apple ProDOS. Quality Software. 1985. pp. 2–8. ISBN 0-912985-05-4. 
  5. a b «Maximum CP/M-80 2.2 volume size?», comp.os.cpm, Google Groups, http://groups.google.com/group/comp.os.cpm/browse_thread/thread/ac56a0ae9ed64fd1, consultado el 2009-10-09 
  6. «SFS file system». Publib.boulder.ibm.com. Consultado el 5 de febrero de 2013.
  7. See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html
  8. Table "Limits" states a maximum of 255 Unicode characters for the filename [2]
  9. «KB955704» (27 de enero de 2009). «Description of the exFAT file system driver update package [for 32-bit XP]».
  10. «msdn TexFAT File Naming Limitations» (14 de octubre de 2009).
  11. Udo Kuhnt, Luchezar Georgiev, Jeremy Davis (2007). FAT+. FATPLUS.TXT, draft revision 2 ([3], [4]).
  12. 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]
  13. a b Richard Russon and Yuval Fledel. «NTFS Documentation». Consultado el 26 de junio de 2011.
  14. 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.
  15. 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».
  16. «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.
  17. 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.
  18. 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.
  19. Docs, Apple, http://docs.info.apple.com/article.html?artnum=25557 
  20. Docs, http://docs.info.apple.com/article.html?artnum=24601 
  21. «Interviews/EricSandeen». FedoraProject (9 de junio de 2008). Consultado el 9 de octubre de 2009.
  22. ext4 1.42 "This release of e2fsprogs has support for file systems > 16 TB"
  23. 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.
  24. 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]
  25. 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.
  26. Varies wildly according to block size and fragmentation of block allocation groups.
  27. a b NSS allows files to have multiple names, in separate namespaces.
  28. 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.
  29. Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  30. Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  31. This restriction might be lifted in newer versions.
  32. 232 × block size
  33. a b c d e «File, file system, and memory size limits in Minix». Minix1.woodhull.com. Consultado el 5 de febrero de 2013.
  34. 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.
  35. ISO 9660#Restrictions
  36. 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
  37. 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.
  38. Joliet Specification
  39. https://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt
  40. «LEAN file system». Freedos-32.sourceforge.net. Consultado el 5 de febrero de 2013.
  41. Note that the filename can be much longer XFS#Extended_attributes
  42. 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.
  43. Implemented in later versions as an extension
  44. 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.
  45. 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.
  46. 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.
  47. 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.
  48. 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.
  49. The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  50. 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.
  51. As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [7]
  52. «As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See». Trustedbsd.org. Consultado el 5 de febrero de 2013.
  53. a b c d Access-control lists and MAC labels are layered on top of extended attributes.
  54. Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  55. a b c d e f g h i 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.
  56. ext4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming
  57. Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
  58. Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
  59. a b c d e Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
  60. 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.
  61. a b CRCs are employed for certain types of metadata.
  62. 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.
  63. 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.
  64. 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.
  65. Record Management Services (RMS) attributes include record type and size, among many others.
  66. 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.
  67. 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.
  68. 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
  69. 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.
  70. a b Not applicable to file systems on a read-only medium.
  71. a b Available only if the file has an Extended Attribute block.
  72. Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
  73. 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.
  74. a b c «6», Parted manual, GNU, http://www.gnu.org/software/parted/manual/html_chapter/parted_6.html 
  75. 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
  76. Optional journaling of data
  77. 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.
  78. a b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  79. 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.
  80. NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
  81. Rick Vanover. «Windows Server 8 data deduplication». Consultado el 2 de diciembre de 2011.
  82. «How to Shrink and Extend NTFS Volumes in Windows». Bleepingcomputer.com. Consultado el 5 de febrero de 2013.
  83. 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.
  84. «Enlace duros on HFS». Developer.apple.com. Consultado el 5 de febrero de 2013.
  85. 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.
  86. 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).
  87. 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.
  88. As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.
  89. Since Mac OS X Snow Leopard, online resizing is supported.«How to resize a live partition in Snow Leopard and Lion».
  90. "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.
  91. «OpenBSD growfs(8) manpage». Openbsd.org (28 de noviembre de 2008). Consultado el 5 de febrero de 2013.
  92. "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
  93. Block level journals can be added by using gjournal module in FreeBSD.
  94. «FreeBSD growfs(8) manpage». Freebsd.org (30 de abril de 2012). Consultado el 5 de febrero de 2013.
  95. a b c d UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  96. Linux kernel versions 2.6.12 and newer.
  97. a b c Offline growing/shrinking as well as online growing: «Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)».
  98. a b c d Off by default.
  99. 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
  100. Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.[¿cuál?]
  101. a b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  102. OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
  103. a b File system implements reliability via atomic transactions.
  104. Optionally no on IRIX.
  105. 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.
  106. [8] (enlace roto disponible en Internet Archive; véase el historial y la última versión).
  107. 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.
  108. 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)
  109. a b Available only in the "NFS" namespace.
  110. Limited capability. Volumes can span physical disks (volume segment)
  111. a b These are referred to as "aliases".
  112. VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  113. When used with venti.
  114. 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.
  115. «How to resize ZFS».
  116. McPherson, Amanda (2009-06-22), A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, http://www.linuxfoundation.org/news-media/blogs/browse/2009/06/conversation-chris-mason-btrfs-next-generation-file-system-linux, consultado el 2009-09-01 
  117. Wiki, BTRFS, Deduplication, https://btrfs.wiki.kernel.org/index.php/Deduplication 
  118. 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.
  119. only for.REL (record structured) files, up to 254 bytes/record
  120. Btrfs can only inline files smaller than 3916B with its metadata«Mailing list discussion».
  121. 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.
  122. Only for "stuffed" inodes
  123. Only if formatted with 4kB-sized clusters or smaller
  124. a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  125. a b c d Fragments were planned, but never actually implemented on ext2 and ext3.
  126. 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.
  127. In "extents" mode.
  128. «AIX documentation: JFS compresión de datos». IBM.
  129. 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.
  130. Depends on UDF implementation.
  131. When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  132. a b c Files, Databases, and Persistent Storage. MSDN.
  133. a b c Via dosFs.
  134. «OS/2 and eComstation FAT32 Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
  135. «NTFS for Windows 98». Download.chip.eu. Consultado el 5 de febrero de 2013.
  136. «OS/2 NTFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
  137. Tuxera NTFS for Windows CE. See «article». Archivado desde el original el 18 de septiembre de 2012. and announcement.
  138. a b c d Cross-platform Drive Solutions. «Sharing Disks - Windows Products». Macwindows.com. Consultado el 5 de febrero de 2013.
  139. Gagne, Ken (31 de agosto de 2009). «Losing legacy data to Snow Leopard». Computerworld. Consultado el 7 de septiembre de 2009.
  140. «hfsutils at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.
  141. «hfs at FreshPorts». Freshports.org. Consultado el 5 de febrero de 2013.
  142. «OS/2 HFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
  143. «Catacombae HFSExplorer». Hem.bredband.net. Consultado el 5 de febrero de 2013.
  144. «DOS/Win 9x HPFS Driver». Hobbes.nmsu.edu. Consultado el 5 de febrero de 2013.
  145. Win NT 4.0 HPFS Driver
  146. «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.
  147. 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]
  148. 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]
  149. 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
  150. 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]
  151. 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]
  152. Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[13]
  153. OS/2 ext2 Driver
  154. a b c d e f See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
  155. Native ZFS for Linux
  156. ZFS on FUSE
  157. Mac ZFS
  158. http://wiki.lustre.org/index.php/Windows_Native_Client
  159. http://wiki.lustre.org/index.php?title=Main_Page
  160. http://wiki.lustre.org/index.php/FAQ_-_OS_Support
  161. Using SAM-QFS on Linux Clients
  162. ncpfs
  163. «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.
  164. [14]
  165. vmfs
  166. a b c AncientFS
  167. a b VMS2Linux
  168. logfs

Enlaces externos[editar]