Comparison of file systems

From Seo Wiki - Search Engine Optimization and Programming Languages
Jump to navigationJump to search


Template:Contradict-other

Please help improve this article by expanding it. Further information might be found on the talk page. (January 2007)
This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (March 2008)

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

General information

File system Creator Year
introduced 		Original operating system
DECtape DEC 1964 PDP-6 Monitor
Level-D DEC 1968 TOPS-10
George 2 ICT (later ICL) 1968 George 2
V6FS Bell Labs 1972 Version 6 Unix
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
OS4000 GEC 1977 OS4000
FAT12 Microsoft 1977 Microsoft Disk BASIC
DOS 3.x Apple Computer 1978 Apple DOS
Pascal Apple Computer 1978 Apple Pascal
CBM DOS Commodore 1978 Microsoft BASIC (for CBM PET)
V7FS Bell Labs 1979 Version 7 Unix
ODS-2 DEC 1979 OpenVMS
DFS Acorn Computers Ltd 1982 Acorn BBC Micro MOS
ADFS Acorn Computers Ltd 1983 Acorn Electron (later Arthur RISC OS)
FFS Kirk McKusick 1983 4.2BSD
ProDOS Apple Computer 1983 ProDOS 8
MFS Apple Computer 1984 Mac OS
Elektronika BK tape format NPO "Scientific centre" (now Sitronics) 1985 Vilnius Basic, BK monitor program
HFS Apple Computer 1985 Mac OS
Amiga OFSTemplate:Fn Metacomco for Commodore 1985 Amiga OS
High Sierra Ecma International 1985 MS-DOS, Microsoft Windows, Mac OS
NWFS Novell 1985 NetWare 286
FAT16 Microsoft 1987 MS-DOS 3.31
Minix V1 FS Andrew S. Tanenbaum 1987 Minix 1.0
Amiga FFS Commodore 1988 Amiga OS 1.3
HPFS IBM & Microsoft 1988 OS/2
ISO 9660:1988 Ecma International, Microsoft 1988 MS-DOS, Microsoft Windows, Linux, Mac OS X, FreeBSD, and AmigaOS
JFS1 IBM 1990 AIX[1]
VxFS VERITAS 1991 SVR4.0
WAFL NetApp 1992 Data ONTAP
AdvFS DEC 1993 [2] Digital Unix
NTFS Version 1.0 Microsoft, Gary Kimura, Tom Miller 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 IBM 1994 MVS/ESA (now z/OS)
Joliet ("CDFS") Microsoft 1995 Microsoft Windows, Linux, Mac OS X, and FreeBSD
UDF ISO/ECMA/OSTA 1995 -
FAT32 Microsoft 1996 Windows 95b[3]
QFS LSC Inc, Sun Microsystems 1996 Solaris
GPFS IBM 1996 AIX, Linux, Windows
Be File System Be Inc., D. Giampaolo, C. Meurillon 1996 BeOS
Minix V2 FS Andrew S. Tanenbaum 1997 Minix 2.0
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
ext3 Stephen Tweedie 1999 Linux
ISO 9660:1999 Ecma International, Microsoft 1999 Microsoft Windows, Linux, Mac OS X, FreeBSD, and AmigaOS
Lustre Sun Microsystems/Cluster File Systems 2002 Linux
JFS IBM 1999 OS/2 Warp Server for e-business
GFS Sistina (Red Hat) 2000 Linux
NTFS Version 5.1 Microsoft 2001 Windows XP
ReiserFS Namesys 2001 Linux
zFS IBM 2001 z/OS (backported to OS/390)
FATX Microsoft 2002 Xbox
UFS2 Kirk McKusick 2002 FreeBSD 5.0
OCFS Oracle Corporation 2002 Linux
VMFS2 VMware 2002 VMware ESX Server 2.0
Fossil Bell Labs 2003 Plan 9 from Bell Labs 4
Google File System Google 2003 Linux
ZFS Sun Microsystems 2004 Solaris
Reiser4 Namesys 2004 Linux
Non-Volatile File System Palm, Inc. 2004 Palm OS Garnet
Minix V3 FS Andrew S. Tanenbaum 2005 MINIX 3
OCFS2 Oracle Corporation 2005 Linux
NILFS NTT 2005 Linux, NetBSD
VMFS3 VMware 2005 VMware ESX Server 3.0
GFS2 Red Hat 2006 Linux
ext4 various 2006 Linux
exFAT Microsoft 2006,2009 Windows CE 6.0, Windows XP SP3, Windows Vista SP1
TexFAT/TFAT Microsoft 2006 Windows CE 6.0
NTFS Version 6.0 Microsoft 2006 Windows Vista
Btrfs Oracle Corporation 2007 Linux
HAMMER Matthew Dillon 2008 Dragonfly BSD
WBFS Nintendo 2009 Wii, Wii Linux, Windows using WBFS Manager

Limits

File system Maximum filename length Allowable characters in directory entries[4] Maximum pathname length Maximum file size Maximum volume size [5]
Apple DOS 3.x 30 bytes Any byte except NUL 30 bytes, no subdirectories (105 files per disk) Template:Unk 3.1 and 3.2 = 113.75 KiB,
3.3 = 140 KiB (assuming standard 35 tracks)
Apple ProDOS 15 bytes A-Z, a-z, 0-9, and period Template:Unk 16 MiB 32 MiB
CP/M file system 8.3 Template:Unk 16 "user areas", no subdirectories 8 MiB[6] 8 MiB to 512 MiB[6]
IBM SFS 8.8 Template:Unk Non-hierarchical[7] Template:Unk Template:Unk
DECtape 6.3 A–Z, 0–9 DTxN:FILNAM.EXT = 15 369,280 bytes (577 * 640) 369,920 bytes (578 * 640)
Elektronika BK tape format 16 bytes Template:Unk Non-hierarchical 64 KiB Not limited. Approx. 800KB (one side) for 90 min cassette
MicroDOS file system 14 bytes Template:Unk Template:Unk 16 MiB 32 MiB
Level-D 6.3 A–Z, 0–9 DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67 34,359,738,368 words (2**35-1); 206,158,430,208 SIXBIT bytes Approx 12 GB (64 * 178 MB)
RT-11 6.3 A–Z, 0–9, $ Non-hierarchical 33,554,432 bytes (65536 * 512) 33,554,432 bytes
V6FS 14 bytes [8] Any byte except NUL and / [9] No limit defined [10] 8 MiB [11] 2 TiB
DOS (GEC) 8 bytes A–Z, 0–9 Non-hierarchical Same as Maximum volume size 64 MiB
OS4000 8 bytes A–Z, 0–9
Period is directory separator 		No limit defined [10] 2 GiB Unknown, but at least 1 GiB
CBM DOS 16 bytes Any byte except NUL Non-hierarchical 16 MiB 16 MiB
V7FS 14 bytes [8] Any byte except NUL and / [9] No limit defined [10] 1 GiB [12] 2 TiB
exFAT 255 characters Any Unicode except NUL No limit defined 127 PiB 64 ZiB, 512 TiB recommended [13]
TexFAT 247 characters Any Unicode except NUL No limit defined 2 GiB 500 GiB Tested [14]


FAT12 8.3 (255 UTF-16 code units with LFN) [8] Any Unicode except NUL (with LFN) [8][9] No limit defined [10] 32 MiB 1 MiB to 32 MiB
FAT16 8.3 (255 UTF-16 code units with LFN) [8] Any Unicode except NUL (with LFN)[8][9] No limit defined [10] 2 GiB 16 MiB to 2 GiB
FAT32 8.3 (255 UTF-16 code units with LFN) [8] Any Unicode except NUL (with LFN)[8][9] No limit defined [10] 4 GiB 512 MiB to 8 TiB [15]
FATX 42 bytes [8] ASCII. Unicode not permitted. No limit defined [10] 2 GiB 16 MiB to 2 GiB
Fossil Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
MFS 255 bytes Any byte except : No path (flat filesystem) 256 MiB 256 MiB
HFS 31 bytes Any byte except :[16] Unlimited 2 GiB 2 TiB
HPFS 255 bytes Any byte except NUL [17] No limit defined [10] 2 GiB 2 TiB[18]
NTFS 255 characters Any Unicode except NUL, / 32,767 Unicode characters with each path component (directory or filename) up to 255 characters long [10] 16 EiB [19] 16 EiB [19]
HFS Plus 255 UTF-16 code units [20] Any valid Unicode [9][21] Unlimited slightly less than 8 EiB slightly less than 8 EiB [22]
FFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 ZiB 256 TiB
UFS1 255 bytes Any byte except NUL [9] No limit defined [10] 4 GiB to 256 TiB 256 TiB
UFS2 255 bytes Any byte except NUL [9] No limit defined [10] 512 GiB to 32 PiB 1 YiB
ext2 255 bytes Any byte except NUL [9] No limit defined [10] 16 GiB to 2 TiB[5] 2 TiB to 32 TiB
ext3 255 bytes Any byte except NUL [9] No limit defined [10] 16 GiB to 2 TiB[5] 2 TiB to 32 TiB
ext4 256 bytes Any byte except NUL [9] No limit defined [10] 16 GiB to 16 TiB[5][23] 1 EiB
Lustre 255 bytes Any byte except NUL [9] No limit defined [10] 320 TiB on ext4 (16 TiB tested) 220 EiB on ext4 (2 PiB tested)
GPFS 255 UTF-8 codepoints Any byte except NUL [9] No limit defined [10] 299 bytes 299 bytes (4 PiB tested)
GFS 255 Any byte except NUL [9] No limit defined [10] 2 TB to 8 EB[24] 2 TB to 8 EB[24]
ReiserFS 4,032 bytes/255 characters Any byte except NUL [9] No limit defined [10] 8 TiB[25] (v3.6), 4 GiB (v3.5) 16 TiB
NILFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 EiB 8 EiB
Reiser4 3,976 bytes Any byte except / and NUL No limit defined [10] 8 TiB on x86 Template:Unk
OCFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 TiB 8 TiB
OCFS2 255 bytes Any byte except NUL [9] No limit defined [10] 4 PiB 4 PiB
XFS 255 bytes [26] Any byte except NUL [9] No limit defined [10] 8 EiB[27] 8 EiB[27]
JFS1 255 bytes Any byte except NUL [9] No limit defined [10] 8 EiB 512 TiB to 4 PiB
JFS 255 bytes Any Unicode except NUL No limit defined [10] 4 PiB 32 PiB
QFS 255 bytes Any byte except NUL [9] No limit defined [10] 16 EiB [28] 4 PiB [28]
BFS 255 bytes Any byte except NUL [9] No limit defined [10] 12,288 bytes to 260 GiB[29] 256 PiB to 2 EiB
AdvFS 255 characters Any byte except NUL [9] No limit defined [10] 16 TiB 16 TiB
NSS 256 characters Depends on namespace used [30] Only limited by client 8 TiB 8 TiB
NWFS 80 bytes [31] Depends on namespace used [30] No limit defined [10] 4 GiB 1 TiB
ODS-5 236 bytes[32] Template:Unk 4,096 bytes[33] 1 TiB 1 TiB
VxFS 255 bytes Any byte except NUL [9] No limit defined [10] 16 EiB Template:Unk
UDF 255 bytes Any Unicode except NUL 1,023 bytes [34] 16 EiB Template:Unk
ZFS 255 bytes Any Unicode except NUL No limit defined [10] 16 EiB 16 EiB
Minix V1 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL [9] No limit defined [10] 64 MiB[35] 64 MiB[36]
Minix V2 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL [9] No limit defined [10] slightly more than 64 MiB[37] 1 GiB[38]
Minix V3 FS 60 bytes Any byte except NUL [9] No limit defined [10] 4 GiB 4 GiB
VMFS2 128 Any byte except NUL and / [9] 2,048 4 TiB [39] 64 TiB
VMFS3 128 Any byte except NUL and / [9] 2,048 2 TiB [39] 64 TiB
ISO 9660:1988 Level 1: 8.3,
Level 2 & 3: ~ 180 		Depends on Level [40] ~ 180 bytes? 4 GiB (Level 1 & 2) to 8 TiB (Level 3) [41] 8 TiB [42]
Joliet ("CDFS") 64 Unicode characters All UCS-2 code except *, /, \, :, ;, and ? [43] Template:Unk same as ISO 9660:1988 same as ISO 9660:1988
ISO 9660:1999 Template:Unk (207?) Template:Unk Template:Unk Template:Unk Template:Unk
High Sierra Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
HAMMER Template:Unk Template:Unk Template:Unk Template:Unk 1 Exabyte
Btrfs 255 bytes Any byte except NUL Template:Unk 16 EiB 16 EiB
WBFS 255 bytes Template:Unk Template:Unk 8.74 GB 1 TB
File system Maximum filename length Allowable characters in directory entries[4] Maximum pathname length Maximum file size Maximum volume size [5]

Metadata

File system Stores file owner POSIX file permissions Creation timestamps Last access/ read timestamps Last content modification timestamps This copy created Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC
CP/M file system No No Yes[44] No Template:Unk Template:Unk No No No No No No
DECtape No No Yes No Template:Unk Template:Unk No No No No No No
Elektronika BK tape format No No No No Template:Unk Template:Unk No No No No No Yes
Level-D Yes Yes Yes Yes Template:Unk Template:Unk Yes Yes Yes No No No
RT-11 No No Yes No Template:Unk Template:Unk No No No No No No
DOS (GEC) Yes No Yes Yes Yes Template:Unk No No No No No No
OS4000 Yes No Yes Yes Yes Template:Unk No No No No No No
V6FS Yes Yes No Yes Yes Template:Unk Yes No No No No No
V7FS Yes Yes No Yes Yes Template:Unk Yes No No No No No
FAT12 No No Yes Yes Template:Unk Template:Unk No[45] No No No No [46] No
FAT16 No No Yes Yes Yes No No[45] No No No No [46] No
FAT32 No No Yes Yes Yes No No[45] No No No No No
HPFS Yes[47] No Yes Yes Yes Template:Unk No No No Template:Unk Yes No
NTFS Yes Yes[48] Yes Yes Yes No Yes No Yes Yes[49] Yes No
HFS No No Yes No Yes No No Yes No No Yes No
HFS Plus Yes Yes Yes Yes Yes No Yes Yes Yes Yes [50] Yes No
FFS Yes Yes No Yes Yes Template:Unk Yes No No No No No
UFS1 Yes Yes No Yes Yes Template:Unk Yes No Yes [51] Yes [51] No [52] No
UFS2 Yes Yes Yes Yes Yes Template:Unk Yes No Yes [51] Yes [51] Yes No
LFS Yes Yes No Yes Yes Template:Unk Yes No No No No No
ext2 Yes Yes No Yes Yes Template:Unk Yes No Yes [53] Yes [53] Yes No
ext3 Yes Yes No Yes Yes No Yes No Yes [53] Yes [53] Yes No
ext4 Yes Yes Yes Yes Yes Template:Unk Yes No Yes [53] Yes [53] Yes Yes [54]
Lustre Yes Yes No Yes Template:Unk Template:Unk Yes No Yes Yes Yes No
GPFS Yes Yes Yes Yes Template:Unk Template:Unk Yes No Yes Yes Yes Yes
GFS Yes Yes No Yes Template:Unk Template:Unk Yes No Yes [53] Yes [53] Yes No
NILFS Yes Yes Yes No Template:Unk Template:Unk Yes No No No No Yes
ReiserFS Yes Yes No Yes Yes No No No No No No No
Reiser4 Yes Yes No Yes Yes Template:Unk Yes No No No No No
OCFS No Yes No No Template:Unk Template:Unk Yes Yes No No No No
OCFS2 Yes Yes No Yes Template:Unk Template:Unk Yes No No No No No
XFS Yes Yes No Yes Yes Template:Unk Yes No Yes Yes [53] Yes No
JFS Yes Yes Yes Yes Yes Template:Unk Yes No Yes Yes Yes No
QFS Yes Yes Yes Yes Template:Unk Template:Unk Yes Yes Yes No Yes No
BFS Yes Yes Yes No Template:Unk Template:Unk No No No No Yes No
AdvFS Yes Yes No Yes Yes Template:Unk Yes No Yes No Yes No
NSS Yes Yes Yes[55] Yes[55] Template:Unk Template:Unk Yes Yes[55] Yes Template:Unk Yes[56][57] No
NWFS Yes Template:Unk Yes[55] Yes[55] Template:Unk Template:Unk Yes Yes[55] Yes Template:Unk Yes[56][57] No
ODS-5 Yes Yes Yes Template:Unk Template:Unk Template:Unk Template:Unk Yes Yes Template:Unk Yes [58] No
VxFS Yes Yes Yes Yes Yes Template:Unk Yes No Yes Template:Unk Yes [53] No
UDF Yes Yes Yes Yes Template:Unk Template:Unk Yes Yes Yes No Yes No
Fossil Yes Yes [59] No Yes Template:Unk Template:Unk Yes No No No No No
ZFS Yes Yes Yes Yes Yes Template:Unk Yes Yes Yes Yes [60] Yes [61] Yes
VMFS2 Yes Yes No Yes Template:Unk Template:Unk Yes No No No No No
VMFS3 Yes Yes No Yes Template:Unk Template:Unk Yes No No No No No
ISO 9660:1988 No No Yes[62] No[63] Yes[64] Template:Unk No No No No No No
Joliet ("CDFS") No No Yes[62] No[63] Yes[64] Template:Unk No No No No No No
ISO 9660:1999 No No Yes No Template:Unk Template:Unk No No No No No No
High Sierra No No Yes No Template:Unk Template:Unk No No No No No No
Btrfs Yes Yes Yes Yes Yes Template:Unk Template:Unk Template:Unk Yes Template:Unk Yes Yes
File system Stores file owner POSIX file permissions Creation timestamps Last access/read timestamps Last content modification timestamps This copy created Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC

Features

File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log Snapshot XIP Encryption COW integrated LVM Data deduplication
CP/M file system No No No No No No No No No No No No No
DECtape No No No No No No No No No No No No No
Level-D No No No No No No No No No No Template:Unk Template:Unk Template:Unk
RT-11 No No No No No No No No No No No No Template:Unk
DOS (GEC) No No No No No No No No No No No No No
OS4000 No Yes [65] No No No No No No No No No No No
V6FS Yes No No No Yes Yes No No No No No No No
V7FS Yes No [66] No No Yes Yes No No No No No No No
FAT12 No No No No No Partial No No No No No No No
FAT16 No No No No No Partial No No No No No No No
FAT32 No No No No No Partial No No No No No No No
GFS Yes Yes[67] Yes Yes[68] Yes Yes No No No No Template:Unk Template:Unk Template:Unk
HPFS No No No No No Yes No Template:Unk No No Template:Unk Template:Unk No
NTFS Yes Yes[69] No[70] Yes[70] Yes[71] Yes Yes Template:Third party[72] Template:Unk Yes Partial Template:Unk Yes[73]
HFS No Yes[74] No No No Yes No No No No No No No
HFS Plus Yes[75] Yes No Yes[76] Partial[77] Yes Yes[78] No No No[79] No No No
FFS Yes Yes No No[80] Yes Yes No No No No No No No
UFS1 Yes Yes No No Yes Yes No No No No No No No
UFS2 Yes Yes No No[81] Yes Yes No Yes Template:Unk No No No No
LFS Yes Yes Yes[82] No Yes Yes No Yes No No Template:Unk Template:Unk Template:Unk
ext2 Yes Yes No No Yes Yes No No Yes[83] No No No No
ext3 Yes Yes Yes [84] Yes Yes Yes No No Yes No No No No
ext4 Yes Yes Yes [84] Yes Yes Yes No No Yes No No No No
Lustre Yes Yes Yes [84] Yes Yes Yes No No No No Template:Unk Template:Unk Template:Unk
NILFS Yes Yes Yes [82] No Yes Yes Yes Yes No No Template:Unk Template:Unk Template:Unk
ReiserFS Yes Yes No [85] Yes Yes Yes No No No No No No No
Reiser4 Yes Yes Yes No Yes Yes No Template:Unk No Yes [86] Yes No Template:Unk
OCFS No Yes No No Yes Yes No No No No Template:Unk Template:Unk Template:Unk
OCFS2 Yes Yes Yes Yes Yes Yes No No No No Template:Unk Template:Unk Template:Unk
XFS Yes Yes No Yes Yes [87] Yes No Yes No No No No No
JFS Yes Yes No Yes Yes[88] Yes No Yes No No Yes Template:Unk Template:Unk
QFS Yes Yes No Yes Yes Yes No No No No Template:Unk Template:Unk Template:Unk
Be File System Yes Yes No Yes Yes Yes Template:Unk No No No No No No
NSS Yes Yes Template:Unk Yes Yes[89] Yes[89] Yes[90] Yes No Yes Template:Unk Template:Unk Template:Unk
NWFS Yes[91] Yes[91] No No Yes[89] Yes[89] Yes[90] Template:Unk No No No Yes[92] Template:Unk
ODS-2 Yes Yes[93] No Yes No No Yes Yes No No Template:Unk Template:Unk Template:Unk
ODS-5 Yes Yes[93] No Yes No Yes Yes Yes Template:Unk No Template:Unk Template:Unk Template:Unk
UDF Yes Yes Yes[82] Yes[82] Yes Yes No No Yes No No No No
VxFS Yes Yes Yes No Yes Yes Yes Yes[94] Template:Unk No Template:Unk Template:Unk Template:Unk
Fossil No No No No Yes Yes Yes Yes No No Template:Unk Template:Unk Template:Unk
ZFS Yes Yes Yes[95] No[95] Yes Yes No Yes No Yes (currently beta)[96] Yes Yes Yes (currently beta)[97]
VMFS2 Yes Yes No Yes Yes Yes No No No No Template:Unk Template:Unk Template:Unk
VMFS3 Yes Yes No Yes Yes Yes No No No No Template:Unk Template:Unk Template:Unk
Btrfs Yes Yes Template:Unk Yes Yes Yes Template:Unk Yes No No Yes Yes Work-in-Progress
File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log Snapshotting XIP Encryption COW integrated LVM Data deduplication

Allocation and layout policies

File system Block suballocation Variable file block size [98] Extents Allocate-on-flush Sparse files Transparent compression
Btrfs Yes No Yes Yes Yes Yes
DECtape No No No No No No
Level-D Yes No Yes No No No
DOS (GEC) No Yes Yes No No No
OS4000 No Yes Yes No No No
V6FS No No No No Yes No
V7FS No No No No Yes No
FAT12 No No No No No No [99]
FAT16 No No No No No No [99]
FAT32 No No No No No No
GFS Partial[100] No No No Yes No
HPFS No No Yes No No No
NTFS Partial No Yes No Yes Yes
HFS Plus No No Yes Yes No No
FFS 8:1 [101] No No No Yes No
UFS1 8:1 [101] No No No Yes No
UFS2 8:1 [101] Yes No No Yes No
LFS 8:1 [101] No No No Yes No
ext2 No [102] No No No Yes No [103]
ext3 No [102] No No No Yes No
ext4 No [102] No Yes Yes Yes No
Lustre No No Yes Yes Yes No
NILFS No No No Yes Yes No
ReiserFS Yes No No No Yes No
Reiser4 Yes No Yes [104] Yes Yes Yes [86]
OCFS No No Yes No Template:Unk No
OCFS2 No No Yes No Yes No
XFS No No Yes Yes Yes No
JFS Yes No Yes No Yes only in JFS1 on AIX[105]
QFS Yes No No No Template:Unk No
BFS No No Yes No Template:Unk No
NSS No No Yes No Template:Unk Yes
NWFS Yes [106] No No No Template:Unk Yes
ODS-5 No No Yes No Template:Unk No
VxFS Template:Unk No Yes No Yes No
UDF No No Yes Depends [107] No No
Fossil No No No No Template:Unk Yes
VMFS2 Yes No No No Yes No
VMFS3 Yes No Yes No Yes No
ZFS Partial [108] Yes No Yes Yes Yes
File system Block suballocation Variable file block size [98] Extents Allocate-on-flush Sparse files Transparent compression

OS support

File system Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2
FAT12 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Template:Unk Yes
FAT16 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Template:Unk Yes
FAT32 Yes since Windows 95 OSR2 Yes since Windows 2000 Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Template:Unk with 3rd party app[109]
NTFS with 3rd party driver [110] Yes Yes No with NTFS-3G with NTFS-3G with NTFS-3G with NTFS-3G on Opensolaris Template:Unk Template:Unk Partial read-only 3rd party driver [111]
Apple HFS with 3rd party app[112] with 3rd party app[112] Yes Yes Yes with 3rd party app[113][114] Template:Unk Template:Unk Template:Unk No with 3rd party app[115]
Apple HFS Plus with 3rd party app[112] with 3rd party app[112] Partial - write support occurs if journal is empty, but requires a force mount. Yes since Mac OS 8.1 Yes Partial read-only 3rd party app[116] Template:Unk Template:Unk Template:Unk No with 3rd party app
HPFS Partial read-only 3rd party driver[117] included until v3.51, 3rd party driver until 4.0[118] Yes Template:Unk Template:Unk Yes Template:Unk Template:Unk Template:Unk Template:Unk Yes
FFS Template:Unk Template:Unk Yes [119] Template:Unk Yes Yes Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
UFS1 Template:Unk Template:Unk Partial - read only Template:Unk Yes Yes Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
UFS2 Template:Unk Template:Unk Partial - read only Template:Unk Yes Yes Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
ext2 Template:Unk with Ext2 IFS (partial, no large inodes)[120] or ext2fsd[121] Yes with ext2fsx[122] with fuse-ext2[123], ExtFS[124] and ext2fsx[122] Yes Template:Unk Template:Unk Template:Unk Template:Unk 3rd party app[125]
ext3 Template:Unk Partial with Ext2 IFS[120] or ext2fsd[121] Yes Template:Unk with fuse-ext2[124] and ExtFS[123] Yes Template:Unk Yes Template:Unk Template:Unk Template:Unk
ext4 Template:Unk Template:Unk Yes in kernel 2.6.28 Template:Unk Partial with fuse-ext2[123] No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
GFS Template:Unk Template:Unk Yes Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
Lustre Template:Unk Template:Unk Yes [126] Template:Unk Template:Unk No Template:Unk No Template:Unk Template:Unk Template:Unk
NILFS Template:Unk Template:Unk Yes in kernel 2.6.30 Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
ReiserFS Template:Unk Partial with 3rd party app Yes Template:Unk Template:Unk Partial - read only Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
Reiser4 Template:Unk Template:Unk with a kernel patch Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
OCFS Template:Unk Template:Unk Yes Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
OCFS2 Template:Unk Template:Unk Yes Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
XFS Template:Unk Template:Unk Yes Template:Unk Template:Unk Partial Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
JFS Template:Unk Template:Unk Yes Template:Unk Template:Unk No Template:Unk Template:Unk Yes Template:Unk Yes
QFS Template:Unk Template:Unk via client software [127] Template:Unk Template:Unk No Template:Unk Yes Template:Unk Template:Unk Template:Unk
BFS Template:Unk Template:Unk Partial - read-only Template:Unk Template:Unk No Yes Template:Unk Template:Unk Template:Unk Template:Unk
NSS Template:Unk Template:Unk via EVMS[128] Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
NWFS Template:Unk Template:Unk via ncpfs client software [129] Template:Unk Template:Unk Yes Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
UDF Partial read-only support of UDF 1.02 in Win98 and WinME Yes [130] Yes Template:Unk Yes Yes Template:Unk Yes Template:Unk Template:Unk Template:Unk
VxFS Template:Unk Template:Unk Yes Template:Unk Template:Unk No Template:Unk Yes Yes Template:Unk Template:Unk
Fossil No No Yes [131] No Yes [131] Yes [131] No Yes [131] Template:Unk Template:Unk No
ZFS No No with FUSE[132] Template:Unk No [133] Yes No Yes No No No
IBM HFS No No No No No No No No No Yes No
IBM zFS No No No No No No No No No Yes No
IBM GPFS [134] No Yes Yes No No No No No Yes No No
VMFS2 Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
VMFS3 Template:Unk Template:Unk Partial read-only with vmfs [135] Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
DECtape Template:Unk Template:Unk with AncientFS [136] Template:Unk with AncientFS [136] with AncientFS [136] Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
Level-D Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
RT-11 Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
ODS-2 Template:Unk Template:Unk Partial read-only with tool or kernel module [137] Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
ODS-5 Template:Unk Template:Unk Partial read-only with kernel module [137] Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
LFS Template:Unk Template:Unk with logfs [138] and others Template:Unk Template:Unk No Template:Unk Template:Unk Template:Unk Template:Unk Template:Unk
Btrfs No No Yes No No No No No No No No
File system Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2

See also

Notes

  1. ↑ IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, on which the Linux port was based, was first shipped in OS/2 Warp Server for e-Business in 1999. The same sourcebase was also used for release JFS2 on AIX 5L.
  2. ↑ Polycenter File System - - HELP
  3. ↑ Microsoft first introduced FAT32 in Windows 95 OSR2 (OEM Service Release 2) and then later in Windows 98. NT-based Windows did not have any support for FAT32 up to Windows NT4; Windows 2000 was the first NT-based Windows OS that received the ability to work with it.
  4. ↑ 4.0 4.1 These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; and particular and operating systems may also place restrictions of their own, across all filesystems. MS-DOS, Microsoft Windows, and OS/2 disallow the characters \ / : ? * " > < | and NUL in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
  5. ↑ 5.0 5.1 5.2 5.3 5.4 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 KiB for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KiB).
  6. ↑ 6.0 6.1 "Maximum CP/M-80 2.2 volume size? - comp.os.cpm | Google Groups". Groups.google.com. http://groups.google.com/group/comp.os.cpm/browse_thread/thread/ac56a0ae9ed64fd1. Retrieved 2009-10-09. 
  7. ↑ SFS file system
  8. ↑ 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 Depends on whether the FAT12, FAT16, and FAT32 implementation has support for 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. ↑ 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 9.11 9.12 9.13 9.14 9.15 9.16 9.17 9.18 9.19 9.20 9.21 9.22 9.23 9.24 9.25 9.26 9.27 9.28 9.29 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. ↑ 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 10.11 10.12 10.13 10.14 10.15 10.16 10.17 10.18 10.19 10.20 10.21 10.22 10.23 10.24 10.25 10.26 10.27 10.28 10.29 10.30 10.31 10.32 10.33 10.34 The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. MS-DOS does not support full pathnames longer than 260 bytes for FAT12 and FAT16. Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Linux has a pathname limit of 4,096.
  11. ↑ The actual maximum was 8,847,360 bytes, with 7 singly-indirect blocks and 1 doubly-indirect block; PWB/UNIX 1.0's variant had 8 singly-indirect blocks, making the maximum 524,288 bytes or half a MiB.
  12. ↑ The actual maximum was 1,082,201,088 bytes, with 10 direct blocks, 1 singly-indirect block, 1 doubly-indirect block, and 1 triply-indirect block. The 4.0BSD and 4.1BSD versions, and the System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4 GiB.
  13. ↑ "KB955704". 2009-01-27. http://support.microsoft.com/?kbid=955704. "Description of the exFAT file system driver update package [for 32-bit XP]" 
  14. ↑ "msdn TexFAT File Naming Limitations". 2009-10-14. http://msdn.microsoft.com/en-us/library/cc907928.aspx. 
  15. ↑ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB. This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid. [1]
  16. ↑ 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 /.
  17. ↑ 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.
  18. ↑ This is the limit of the on-disk structures. The HPFS Installable File System driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64 GiB.
  19. ↑ 19.0 19.1 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 TiB and the file size to 16 TiB respectively.
  20. ↑ 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.
  21. ↑ 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.
  22. ↑ See http://docs.info.apple.com/article.html?artnum=25557 and http://docs.info.apple.com/article.html?artnum=24601.
  23. ↑ "Interviews/EricSandeen". FedoraProject. 2008-06-09. http://fedoraproject.org/wiki/Interviews/EricSandeen. Retrieved 2009-10-09. 
  24. ↑ 24.0 24.1 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.
  25. ↑ ReiserFS has a theoretical maximum file size of 1 EiB, but "page cache limits this to 8 Ti on architectures with 32 bit int"[2]
  26. ↑ Note that the filename can be much longer XFS#Extended_attributes
  27. ↑ 27.0 27.1 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.
  28. ↑ 28.0 28.1 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.
  29. ↑ Varies wildly according to block size and fragmentation of block allocation groups.
  30. ↑ 30.0 30.1 NSS allows files to have multiple names, in separate namespaces.
  31. ↑ 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.
  32. ↑ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  33. ↑ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  34. ↑ This restriction might be lifted in newer versions.
  35. ↑ http://minix1.woodhull.com/faq/filesize.html
  36. ↑ http://minix1.woodhull.com/faq/filesize.html
  37. ↑ http://minix1.woodhull.com/faq/filesize.html
  38. ↑ http://minix1.woodhull.com/faq/filesize.html
  39. ↑ 39.0 39.1 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.
  40. ↑ ISO_9660#Restrictions
  41. ↑ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB in size. See ISO_9660#The_2_GiB_.28or_4_GiB_depending_on_implementation.29_file_size_limit
  42. ↑ 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.
  43. ↑ Joliet Specification
  44. ↑ Implemented in later versions as an extension
  45. ↑ 45.0 45.1 45.2 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.
  46. ↑ 46.0 46.1 Particular Installable File System drivers and operating systems may not support extended attributes on FAT12 and FAT16. The OS/2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes (using a "EA DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.
  47. ↑ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  48. ↑ 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.
  49. ↑ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [3]
  50. ↑ As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See [4]
  51. ↑ 51.0 51.1 51.2 51.3 Access-control lists and MAC labels are layered on top of extended attributes.
  52. ↑ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  53. ↑ 53.0 53.1 53.2 53.3 53.4 53.5 53.6 53.7 53.8 53.9 Some Installable File System drivers and operating systems may not support extended attributes, access control lists or security labels on these filesystems. Linux kernels prior to 2.6.x may either be missing support for these altogether or require a patch.
  54. ↑ ext4 uses journal checksumming only
  55. ↑ 55.0 55.1 55.2 55.3 55.4 55.5 The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
  56. ↑ 56.0 56.1 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.
  57. ↑ 57.0 57.1 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.
  58. ↑ Record Management Services (RMS) attributes include record type and size, among many others.
  59. ↑ File permission in 9P are a variation of the traditional Unix permissions with some minor changes, eg. the suid bit is replaced by a new 'exclusive access' bit.
  60. ↑ 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.
  61. ↑ 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 compaible attributes for use by CIFS; as well as some attributes ported from FreeBSD
  62. ↑ 62.0 62.1 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.
  63. ↑ 63.0 63.1 Not applicable to file systems on a read-only medium.
  64. ↑ 64.0 64.1 Available only if the file has an Extended Attribute block.
  65. ↑ Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
  66. ↑ System V Release 4, and some other Unix systems, retrofitted symbolic links to their versions of the Version 7 Unix file system, although the original version didn't support them.
  67. ↑ 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
  68. ↑ Optional journaling of data
  69. ↑ 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.
  70. ↑ 70.0 70.1 NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  71. ↑ 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.
  72. ↑ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
  73. ↑ NTFS Single Instance Storage, see [5].
  74. ↑ Mac OS System 7 introduced the 'alias', analogous to the POSIX symbolic link but with some notable differences. Not only could they cross file systems but they could point to entirely different file servers, and recorded enough information to allow the remote file system to be mounted on demand. It had its own API that application software had to use to gain their benefits-- this is the opposite approach from POSIX which introduced specific APIs to avoid the symbolic link nature of the link. The Finder displayed their file names in an italic font (at least in Roman scripts), but otherwise they behaved identically to their referent.
  75. ↑ Hard Links on HFS+[6]
  76. ↑ 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.
  77. ↑ 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).
  78. ↑ 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.
  79. ↑ HFS+ does not actually encrypt files: to implement FileVault, OS X creates an HFS+ filesystem in a sparse, encrypted disk image that is automatically mounted over the home directory when the user logs in.
  80. ↑ "Write Ahead Physical Block Logging" in NetBSD, provides metadata journalling and consistency as an alternative to softdep.
  81. ↑ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
  82. ↑ 82.0 82.1 82.2 82.3 UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  83. ↑ Linux kernel versions 2.6.12 and newer.
  84. ↑ 84.0 84.1 84.2 Off by default.
  85. ↑ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.
  86. ↑ 86.0 86.1 Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  87. ↑ Optionally no on IRIX.
  88. ↑ Particular Installable File System drivers and operating systems may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.
  89. ↑ 89.0 89.1 89.2 89.3 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.
  90. ↑ 90.0 90.1 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)
  91. ↑ 91.0 91.1 Available only in the "NFS" namespace.
  92. ↑ Limited capability. Volumes can span physical disks (volume segment)
  93. ↑ 93.0 93.1 These are referred to as "aliases".
  94. ↑ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  95. ↑ 95.0 95.1 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.
  96. ↑ "ZFS on disk encryption". Sun Microsystems. http://opensolaris.org/os/project/zfs-crypto. 
  97. ↑ "ZFS Deduplication : Jeff Bonwick's Blog". Jeff Bonwick. http://blogs.sun.com/bonwick/en_US/entry/zfs_dedup. 
  98. ↑ 98.0 98.1 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.
  99. ↑ 99.0 99.1 DoubleSpace in DOS 6, and DriveSpace in Windows 95 and Windows 98 were data compression schemes for FAT, but are no longer supported by Microsoft.
  100. ↑ Only for "stuffed" inodes
  101. ↑ 101.0 101.1 101.2 101.3 Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  102. ↑ 102.0 102.1 102.2 Fragments were planned, but never actually implemented on ext2 and ext3.
  103. ↑ 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.
  104. ↑ In "extents" mode.
  105. ↑ "AIX documentation: JFS data compression". IBM. http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.baseadmn/doc/baseadmndita/jfsdatacomp.htm. 
  106. ↑ 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.
  107. ↑ Depends on UDF implementation.
  108. ↑ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  109. ↑ OS/2 and eComstation FAT32 Driver[7]
  110. ↑ NTFS for Windows 98[8]
  111. ↑ OS/2 NTFS Driver[9]
  112. ↑ 112.0 112.1 112.2 112.3 Sharing Disks - Windows Products[10]
  113. ↑ hfsutils at FreshPorts[11]
  114. ↑ hfs at FreshPorts[12]
  115. ↑ OS/2 HFS Driver[13]
  116. ↑ Catacombae HFSExplorer[14]
  117. ↑ DOS/Win 9x HPFS Driver[15]
  118. ↑ Win NT 4.0 HPFS Driver[16]
  119. ↑ "How to mount FFS partition under Linux - NetBSD Wiki". Wiki.netbsd.se. http://wiki.netbsd.se/How_to_mount_FFS_partition_under_Linux. Retrieved 2009-10-09. 
  120. ↑ 120.0 120.1 Ext2 IFS for Windows provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.[17]
  121. ↑ 121.0 121.1 Ext2Fsd is an open source linux ext2/ext3 file system driver for Windows systems (NT/2K/XP/VISTA, X86/AMD64).[18]
  122. ↑ 122.0 122.1 Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[19]
  123. ↑ 123.0 123.1 123.2 Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read write support.[20]
  124. ↑ 124.0 124.1 Paragon ExtFS for Mac® a low-level file system driver was specially developed to bridge file system incompatibility between Linux and Mac by providing full read/-write access to the Ext2 and Ext3 file systems under Mac® OS X.[21]
  125. ↑ OS/2 ext2 Driver[22]
  126. ↑ http://wiki.lustre.org/index.php?title=Main_Page
  127. ↑ Using SAM-QFS on Linux Clients [23]
  128. ↑ Supported using only EVMS; not currently supported using LVM
  129. ↑ ncpfs [24]
  130. ↑ "Understanding the difference between the Live File System and Mastered disc formats". Which CD or DVD format should I use?. Microsoft. http://windowshelp.microsoft.com/Windows/en-US/help/2af64e60-60aa-4d79-ab6c-3a5db5806cbe1033.mspx#section_2. Retrieved 2008-11-22. 
  131. ↑ 131.0 131.1 131.2 131.3 Provided in Plan 9 from User Space
  132. ↑ ZFS on FUSE
  133. ↑ http://www.osnews.com/story/22388
  134. ↑ [25][dead link]
  135. ↑ vmfs[26]
  136. ↑ 136.0 136.1 136.2 AncientFS [27]
  137. ↑ 137.0 137.1 VMS2Linux[28]
  138. ↑ logfs [29]

External links

fr:Comparaison des systèmes de fichiers ru:Сравнение файловых систем sk:Porovnanie súborových systémov

If you like SEOmastering Site, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...

→

Retrieved from "https://www.seomastering.com:443/w/index.php?title=Comparison_of_file_systems&oldid=9328"