Jump to content

Comparison of file systems: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
JeffV (talk | contribs)
ZFS includes both encryption and deduplication.
Line 2,358: Line 2,358:
| {{Yes}}
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}} (currently [[Development stage#Beta|beta]])<ref>{{Cite web|title = ZFS on disk encryption |publisher = Sun Microsystems |url = http://opensolaris.org/os/project/zfs-crypto}}</ref>
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}} (currently [[Development stage#Beta|beta]])<ref>{{Cite web| title = ZFS Deduplication : Jeff Bonwick's Blog |publisher = Jeff Bonwick |url = http://blogs.sun.com/bonwick/en_US/entry/zfs_dedup}}</ref>
| {{Yes}}
| {{Yes}} online <ref>{{Cite web| title = How to resize ZFS | url = http://harryd71.blogspot.com/2008/08/how-to-resize-zfs.html}}</ref>
| {{Yes}} online <ref>{{Cite web| title = How to resize ZFS | url = http://harryd71.blogspot.com/2008/08/how-to-resize-zfs.html}}</ref>
|-
|-

Revision as of 21:55, 4 February 2011

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 OFS[10] Metacomco for Commodore 1985 Amiga OS
High Sierra Ecma International 1985 MS-DOS, 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, Mac OS, and AmigaOS
JFS1 IBM 1990 AIX[1]
VxFS VERITAS 1991 SVR4.0
WAFL NetApp 1992 Data ONTAP
Minix V2 FS Andrew S. Tanenbaum 1992 MINIX 1.6 and 2.0
AdvFS DEC 1993[2] 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 IBM 1994 MVS/ESA (now z/OS)
Joliet ("CDFS") Microsoft 1995 Microsoft Windows, Linux, Mac OS, 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
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
JFS IBM 1999 OS/2 Warp Server for e-business
GFS Sistina (Red Hat) 2000 Linux
Melio FS Sanbolic 2001 Windows
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
Lustre Sun Microsystems/Cluster File Systems 2002 Linux
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, FreeBSD
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
Oracle ACFS Oracle Corporation 2009 Linux - Red Hat Enterprise Linux 5 and Oracle Enterprise Linux 5 only
LTFS IBM 2010 Linux, Mac OS X, planned Microsoft Windows,
IlesfayFS Ilesfay Technology Group 2011 Microsoft Windows, planned Red Hat Enterprise Linux

Limits

File system Maximum filename length Allowable characters in directory entries[4] Maximum pathname length Maximum file size Maximum volume size [5]
Acorn ADFS 10 + 3 bytes Any ISO 8859-1 character except: $ & % @ \ ^ : . # * " ¦ No limit defined 512 MB 512 MB
Apple DOS 3.x 30 bytes Any byte except NUL 30 bytes, no subdirectories (105 files per disk) Un­known 113.75 KB (113.75 × 1024 bytes) DOS 3.1, 3.2

140 KB DOS 3.3 (assuming standard 35 tracks)

Apple ProDOS 15 bytes A-Z, a-z, 0-9, and period Un­known 16 MB (16 × 10242 bytes) 32 MB
CP/M file system 8.3 Un­known 16 "user areas", no subdirectories 8 MB[6] 8 MB to 512 MB[6]
IBM SFS 8.8 Un­known Non-hierarchical[7] Un­known Un­known
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 Un­known Non-hierarchical 64 KB Not limited. Approx. 800KB (one side) for 90 min cassette
MicroDOS file system 14 bytes Un­known Un­known 16 MB 32 MB
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] 16 MB [11] 2 TB (2 × 10244 bytes)
DOS (GEC) 8 bytes A–Z, 0–9 Non-hierarchical Same as Maximum volume size 64 MB
OS4000 8 bytes A–Z, 0–9
Period is directory separator
No limit defined [10] 2 GB (2 × 10243 bytes) Unknown, but at least 1 GB
CBM DOS 16 bytes Any byte except NUL Non-hierarchical 16 MB 16 MB
V7FS 14 bytes [8] Any byte except NUL and / [9] No limit defined [10] 1 GB [12] 2 TB
exFAT 226 characters Any Unicode except NUL No limit defined 127 PB (127 × 10245 bytes) 64 ZB (64 × 10247 bytes), 512 TB recommended [13]
TexFAT 247 characters Any Unicode except NUL No limit defined 2 GB 500 GB 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 MB 1 MB to 32 MB
FAT16 8.3 (255 UTF-16 code units with LFN) [8] Any Unicode except NUL (with LFN)[8][9] No limit defined [10] 2 GB 16 MB to 2 GB
FAT32 8.3 (255 UTF-16 code units with LFN) [8] Any Unicode except NUL (with LFN)[8][9] No limit defined [10] 4 GB 512 MB to 8 TB [15]
FATX 42 bytes [8] ASCII. Unicode not permitted. No limit defined [10] 2 GB 16 MB to 2 GB
Fossil Un­known Un­known Un­known Un­known Un­known
MFS 255 bytes Any byte except : No path (flat filesystem) 226 MB 226 MB
HFS 31 bytes Any byte except :[16] Unlimited 2 GB 2 TB
HPFS 255 bytes Any byte except NUL [17] No limit defined [10] 2 GB 2 TB[18]
NTFS 255 characters Any Unicode except NUL and \ / : * ? " < > | 32,767 Unicode characters with each path component (directory or filename) commonly up to 255 characters long [10] 16 EB (16 × 10246 bytes) [19] 16 EB [19]
HFS Plus 255 UTF-16 code units [20] Any valid Unicode [9][21] Unlimited slightly less than 8 EB slightly less than 8 EB [22][23]
FFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 ZB 8 ZB
UFS1 255 bytes Any byte except NUL [9] No limit defined [10] 4 GB to 226 TB 226 TB
UFS2 255 bytes Any byte except NUL [9] No limit defined [10] 512 GB to 32 PB 1 YB (10248 bytes)
ext2 255 bytes Any byte except NUL [9] and / No limit defined [10] 16 GB to 2 TB[5] 2 TB to 32 TB
ext3 255 bytes Any byte except NUL [9] and / No limit defined [10] 16 GB to 2 TB[5] 2 TB to 32 TB
ext4 256 bytes Any byte except NUL [9] and / No limit defined [10] 16 GB to 16 TB[5][24] 1 EB
Lustre 255 bytes Any byte except NUL [9] No limit defined [10] 320 TB on ext4 (16 TB tested) 220 EB on ext4 (10 PB tested)
GPFS 255 UTF-8 codepoints Any byte except NUL [9] No limit defined [10] 299 bytes 299 bytes (4 PB tested)
GFS 255 Any byte except NUL [9] No limit defined [10] 2 TB to 8 EB[25] 2 TB to 8 EB[25]
ReiserFS 4,032 bytes/226 characters Any byte except NUL [9] No limit defined [10] 8 TB[26] (v3.6), 2 GB (v3.5) 16 TB
NILFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 EB 8 EB
Reiser4 3,976 bytes Any byte except / and NUL No limit defined [10] 8 TB on x86 Un­known
OCFS 255 bytes Any byte except NUL [9] No limit defined [10] 8 TB 8 TB
OCFS2 255 bytes Any byte except NUL [9] No limit defined [10] 4 PB 4 PB
XFS 255 bytes [27] Any byte except NUL [9] No limit defined [10] 8 EB[28] 8 EB[28]
JFS1 255 bytes Any byte except NUL [9] No limit defined [10] 8 EB 512 TB to 4 PB
JFS 255 bytes Any Unicode except NUL No limit defined [10] 4 PB 32 PB
QFS 255 bytes Any byte except NUL [9] No limit defined [10] 16 EB [29] 4 PB [29]
BFS 255 bytes Any byte except NUL [9] No limit defined [10] 12,288 bytes to 260 GB[30] 226 PB to 2 EB
AdvFS 226 characters Any byte except NUL [9] No limit defined [10] 16 TB 16 TB
NSS 226 characters Depends on namespace used [31] Only limited by client 8 TB 8 TB
NWFS 80 bytes [32] Depends on namespace used [31] No limit defined [10] 4 GB 1 TB
ODS-5 236 bytes[33] Un­known 4,096 bytes[34] 1 TB 1 TB
VxFS 255 bytes Any byte except NUL [9] No limit defined [10] 16 EB Un­known
UDF 255 bytes Any Unicode except NUL 1,023 bytes [35] 16 EB Un­known
ZFS 255 bytes Any Unicode except NUL No limit defined [10] 16 EB 16 EB
Minix V1 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL [9] No limit defined [10] 64 MB[36] 64 MB[36]
Minix V2 FS 14 or 30 bytes, set at filesystem creation time Any byte except NUL [9] No limit defined [10] 4 GB[36] 1 GB then 2 TB[36]
Minix V3 FS 60 bytes Any byte except NUL [9] No limit defined [10] 4 GB 16 TB[36]
VMFS2 128 Any byte except NUL and / [9] 2,048 4 TB [37] 64 TB
VMFS3 128 Any byte except NUL and / [9] 2,048 2 TB[37] 64 TB
ISO 9660:1988 Level 1: 8.3,
Level 2 & 3: ~ 180
Depends on Level [38] ~ 180 bytes? 4 GB (Level 1 & 2) to 8 TB (Level 3) [39] 8 TB [40]
Joliet ("CDFS") 64 Unicode characters All UCS-2 code except *, /, \, :, ;, and ? [41] Un­known same as ISO 9660:1988 same as ISO 9660:1988
ISO 9660:1999 Un­known (207?) Un­known Un­known Un­known Un­known
High Sierra Un­known Un­known Un­known Un­known Un­known
HAMMER Un­known Un­known Un­known Un­known 1 EB
Btrfs 255 bytes Any byte except NUL Un­known 16 EB 16 EB
LTFS Un­known Un­known Un­known Un­known Un­known
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[42] No Un­known Un­known No No No No No No
DECtape No No Yes No Un­known Un­known No No No No No No
Elektronika BK tape format No No No No Un­known Un­known No No No No No Yes
Level-D Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No No No
RT-11 No No Yes No No No No No No No No No
DOS (GEC) Yes No Yes Yes Yes Un­known No No No No No No
OS4000 Yes No Yes Yes Yes Un­known No No No No No No
V6FS Yes Yes No Yes Yes Un­known Yes No No No No No
V7FS Yes Yes No Yes Yes Un­known Yes No No No No No
FAT12 No No Yes Yes Un­known Un­known No[43] No No No No [44] No
FAT16 No No Yes Yes Yes No No[43] No No No No [44] No
FAT32 No No Yes Yes Yes No No[43] No No No No No
exFAT Un­known Un­known Yes Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known
HPFS Yes[45] No Yes Yes Yes Un­known No No No Un­known Yes No
NTFS Yes Yes[46] Yes Yes Yes No Yes No Yes Yes[47] 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 [48] Yes No
FFS Yes Yes No Yes Yes Un­known Yes No No No No No
UFS1 Yes Yes No Yes Yes Un­known Yes No Yes [49] Yes [49] No [50] No
UFS2 Yes Yes Yes Yes Yes Un­known Yes No Yes [49] Yes [49] Yes No
LFS Yes Yes No Yes Yes Un­known Yes No No No No No
ext2 Yes Yes No Yes Yes Un­known Yes No Yes [51] Yes [51] Yes No
ext3 Yes Yes No Yes Yes No Yes No Yes [51] Yes [51] Yes No
ext4 Yes Yes Yes Yes Yes Un­known Yes No Yes [51] Yes [51] Yes Partial [52]
Lustre Yes Yes Partial [53] Yes Yes No Yes No Yes Yes Yes No [54]
GPFS Yes Yes Yes Yes Yes Un­known Yes No Yes Yes Yes Yes
GFS Yes Yes No Yes Un­known Un­known Yes No Yes [51] Yes [51] Yes No
NILFS Yes Yes Yes No Un­known Un­known 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 Un­known Yes No No No No No
OCFS No Yes No No Un­known Un­known Yes Yes No No No No
OCFS2 Yes Yes No Yes Un­known Un­known Yes No No No No No
XFS Yes Yes No Yes Yes Un­known Yes No Yes Yes [51] Yes No
JFS Yes Yes Yes Yes Yes Un­known Yes No Yes Yes Yes No
QFS Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No Yes No
BFS Yes Yes Yes No Un­known Un­known No No No No Yes No
AdvFS Yes Yes No Yes Yes Un­known Yes No Yes No Yes No
NSS Yes Yes Yes[55] Yes[55] Un­known Un­known Yes Yes[55] Yes Un­known Yes[56][57] No
NWFS Yes Un­known Yes[55] Yes[55] Un­known Un­known Yes Yes[55] Yes Un­known Yes[56][57] No
ODS-5 Yes Yes Yes Un­known Un­known Un­known Un­known Yes Yes Un­known Yes [58] No
VxFS Yes Yes Yes Yes Yes Un­known Yes No Yes Un­known Yes [51] No
UDF Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No Yes No
Fossil Yes Yes [59] No Yes Un­known Un­known Yes No No No No No
ZFS Yes Yes Yes Yes Yes Un­known Yes Yes Yes Yes [60] Yes [61] Yes
VMFS2 Yes Yes No Yes Un­known Un­known Yes No No No No No
VMFS3 Yes Yes No Yes Un­known Un­known Yes No No No No No
ISO 9660:1988 No No Yes[62] No[63] Yes[64] Un­known No No No No No No
Joliet ("CDFS") No No Yes[62] No[63] Yes[64] Un­known No No No No No No
ISO 9660:1999 No No Yes No Un­known Un­known No No No No No No
High Sierra No No Yes No Un­known Un­known No No No No No No
Btrfs Yes Yes Yes Yes Yes Un­known Yes Un­known Yes Un­known 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 Volumes are resizeable
CP/M file system No No No No No No No No No No No No No Un­known
DECtape No No No No No No No No No No No No No Un­known
Level-D No No No No No No No No No No Un­known Un­known Un­known Un­known
RT-11 No No No No No No No No No No No No No Un­known
DOS (GEC) No No No No No No No No No No No No No Un­known
OS4000 No Yes [65] No No No No No No No No No No No Un­known
V6FS Yes No No No Yes Yes No No No No No No No Un­known
V7FS Yes No [66] No No Yes Yes No No No No No No No Un­known
FAT12 No No No No No Partial No No No No No No No Yes offline[67]
FAT16 No No No No No Partial No No No No No No No Yes offline [67]
FAT32 No No No No No Partial No No No No No No No Yes offline[67]
exFAT Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
GFS Yes Yes[68] Yes Yes[69] Yes Yes No No No No Un­known Un­known Un­known Un­known
GPFS Yes Yes Un­known Un­known Yes Yes Yes Yes Yes No Yes Yes No Yes online
HPFS No No No No No Yes No Un­known No No Un­known Un­known No Un­known
NTFS Yes Yes[70] No[71] Yes[71] Yes[72] Yes Yes Partial[73] Yes Yes Partial Un­known No Yes[74]
HFS No Yes[75] No No No Yes No No No No No No No Un­known
HFS Plus Yes[76] Yes No Yes[77] Partial[78] Yes Yes[79] No No No[80] No No No Yes offline
FFS Yes Yes No No[81] Yes Yes No No No No No No No Un­known
UFS1 Yes Yes No No Yes Yes No No No No No No No Un­known
UFS2 Yes Yes No No[82][83] Yes Yes No Yes Un­known No No No No Un­known
LFS Yes Yes Yes[84] No Yes Yes No Yes No No Un­known Un­known Un­known Un­known
ext2 Yes Yes No No Yes Yes No No Yes[85] No No No No Yes online[86]
ext3 Yes Yes Yes [87] Yes Yes Yes No No Yes No No No No Yes online[86]
ext4 Yes Yes Yes [87] Yes Yes Yes No No Yes No No No No Yes offline
Lustre Yes Yes Yes [87] Yes Yes Yes Yes in 2.0 No [54] No No [54] No [54] No [54] No [54] Yes [88]
NILFS Yes Yes Yes [84] No Yes Yes Yes Yes No No Yes Un­known Un­known Un­known
ReiserFS Yes Yes No [89] Yes Yes Yes No No No No No No No Yes offline
Reiser4 Yes Yes Yes No Yes Yes No Un­known No Yes [90] Yes No Un­known Yes
OCFS No Yes No No Yes Yes No No No No Un­known Un­known Un­known Un­known
OCFS2 Yes Yes Yes Yes Yes Yes No No No No Un­known Un­known Un­known Yes online for version 1.4 and higher
XFS Yes Yes Yes Yes Yes [91] Yes No Yes No No No No No Yes online (cannot be shrunk)
JFS Yes Yes No Yes Yes[92] Yes No Yes No No Yes Un­known Un­known Yes[93]
QFS Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
Be File System Yes Yes No Yes Yes Yes Un­known No No No No No No Un­known
NSS Yes Yes Un­known Yes Yes[94] Yes[94] Yes[95] Yes No Yes Un­known Un­known Un­known Un­known
NWFS Yes[96] Yes[96] No No Yes[94] Yes[94] Yes[95] Un­known No No No Yes[97] Un­known Un­known
ODS-2 Yes Yes[98] No Yes No No Yes Yes No No Un­known Un­known Un­known Un­known
ODS-5 Yes Yes[98] No Yes No Yes Yes Yes Un­known No Un­known Un­known Un­known Un­known
UDF Yes Yes Yes[84] Yes[84] Yes Yes No No Yes No No No No Un­known
VxFS Yes Yes Yes No Yes Yes Yes Yes[99] Un­known No Un­known Un­known Un­known Un­known
Fossil No No No No Yes Yes Yes Yes No No Un­known No Yes[100] Un­known
ZFS Yes Yes Yes[101] No[101] Yes Yes No Yes No Yes Yes Yes Yes Yes online [102]
VMFS2 Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
VMFS3 Yes Yes No Yes Yes Yes No No No No Un­known Un­known Un­known Un­known
Btrfs Yes Yes Un­known Yes Yes Yes Un­known Yes No No Yes Yes Work-in-Progress Yes online
File system Hard links Symbolic links Block journaling Metadata-only journaling Case-sensitive Case-preserving File Change Log Snapshotting XIP Encryption COW integrated LVM Data deduplication Volumes are resizeable

Allocation and layout policies

File system Block suballocation Variable file block size [103] 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 [104]
FAT16 No No No No No No [104]
FAT32 No No No No No No
exFAT Un­known Un­known Un­known Un­known Un­known Un­known
GFS Partial[105] 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 Yes
FFS 8:1 [106] No No No Yes No
UFS1 8:1 [106] No No No Yes No
UFS2 8:1 [106] Yes No No Yes No
LFS 8:1 [106] No No No Yes No
ext2 No [107] No No No Yes No [108]
ext3 No [107] No No No Yes No
ext4 No [107] 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 [109] Yes Yes Yes [90]
OCFS No No Yes No Un­known 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[110]
QFS Yes No No No Un­known No
BFS No No Yes No Un­known No
NSS No No Yes No Un­known Yes
NWFS Yes [111] No No No Un­known Yes
ODS-5 No No Yes No Un­known No
VxFS Un­known No Yes No Yes No
UDF No No Yes Depends [112] No No
Fossil No No No No Un­known Yes
VMFS2 Yes No No No Yes No
VMFS3 Yes No Yes No Yes No
ZFS Partial [113] Yes No Yes Yes Yes
File system Block suballocation Variable file block size [103] Extents Allocate-on-flush Sparse files Transparent compression

Supporting operating systems

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 Un­known Yes
FAT16 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known Yes
FAT32 Yes since Windows 95 OSR2 Yes since Windows 2000 Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known with 3rd party app[114]
exFAT Partial read-only with third party driver Yes : Win7, Vista SP1, can be added to XP SP2 with third party driver No Yes 10.6.5+ No No Yes No No No
NTFS with 3rd party driver [115] Yes Yes Kernel 2.2 or newer, or with NTFS-3G or ntfsprogs with NTFS-3G with NTFS-3G with NTFS-3G with NTFS-3G with NTFS-3G on Opensolaris Un­known Un­known Partial read-only 3rd party driver [116]
Apple HFS with 3rd party app[117] with 3rd party app[117] Yes Yes Yes with 3rd party app[118][119] Un­known Un­known Un­known No with 3rd party app[120]
Apple HFS Plus with 3rd party app[117] with 3rd party app[117] 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[121] Un­known Un­known Un­known No with 3rd party app
HPFS Partial read-only 3rd party driver[122] included until v3.51, 3rd party driver until 4.0[123] Yes Un­known Un­known Yes Un­known Un­known Un­known Un­known Yes
FFS Un­known Un­known Yes [124] Un­known Yes Yes Un­known Un­known Un­known Un­known Un­known
UFS1 Un­known Un­known Partial - read only Un­known Yes Yes Un­known Un­known Un­known Un­known Un­known
UFS2 Un­known Un­known Partial - read only Un­known No Yes Un­known Un­known Un­known Un­known Un­known
ext2 Un­known with Ext2 IFS (partial, no large inodes)[125] or ext2fsd[126] Yes with ext2fsx[127] with fuse-ext2[128], ExtFS[129] and ext2fsx[127] Yes Un­known Un­known Un­known Un­known 3rd party app[130]
ext3 Un­known Partial with Ext2 IFS[125] or ext2fsd[126] Yes Un­known with fuse-ext2[129] and ExtFS[128] Yes Un­known Yes Un­known Un­known Un­known
ext4 No Partial with Ext2Read [131] read-only for LVM2 and Ext4 extents Yes since kernel 2.6.28 Un­known Partial with fuse-ext2[128] No Un­known Un­known Un­known Un­known Un­known
Lustre No Partial - under development [132] Yes [133] No Partial - via FUSE Partial - via FUSE No Partial - under development [134] No No No
GFS Un­known Un­known Yes Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
NILFS Un­known Un­known Yes since kernel 2.6.30 Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
ReiserFS Un­known Partial with 3rd party app Yes Un­known No Partial - read only Un­known Un­known Un­known Un­known Un­known
Reiser4 Un­known Un­known with a kernel patch Un­known No No Un­known Un­known Un­known Un­known Un­known
OCFS Un­known Un­known Yes Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
OCFS2 Un­known Un­known Yes Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
XFS Un­known Un­known Yes Un­known Un­known Partial Un­known Un­known Un­known Un­known Un­known
JFS Un­known Un­known Yes Un­known Un­known No Un­known Un­known Yes Un­known Yes
QFS Un­known Un­known via client software [135] Un­known Un­known No Un­known Yes Un­known Un­known Un­known
BFS Un­known Un­known Partial - read-only Un­known Un­known No Yes Un­known Un­known Un­known Un­known
NSS Un­known Un­known with Novell OES2[citation needed] Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
NWFS Un­known Un­known via ncpfs client software [136] Un­known Un­known Yes Un­known Un­known Un­known Un­known Un­known
UDF Partial read-only support of UDF 1.02 since Win98 and WinME Yes [137] Yes Yes since Mac OS 9 Yes Yes Un­known Yes Un­known Un­known Un­known
VxFS Un­known Un­known Yes Un­known Un­known No Un­known Yes Yes Un­known Un­known
Fossil No No No No No No No No No No No
ZFS No No with FUSE[138] Un­known No [139] 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 [140] No Yes Yes No No No No No Yes No No
VMFS2 Un­known Un­known Un­known Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
VMFS3 Un­known Un­known Partial read-only with vmfs [141] Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
DECtape Un­known Un­known with AncientFS [142] Un­known with AncientFS [142] with AncientFS [142] Un­known Un­known Un­known Un­known Un­known
Level-D Un­known Un­known Un­known Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
RT-11 Un­known Un­known Un­known Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
ODS-2 Un­known Un­known Partial read-only with tool or kernel module [143] Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
ODS-5 Un­known Un­known Partial read-only with kernel module [143] Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
LFS Un­known Un­known with logfs [144] and others Un­known Un­known No Un­known Un­known Un­known Un­known Un­known
Btrfs No No Yes No No No No No No No No
LTFS Un­known Un­known Yes Yes Yes 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, 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. ^ "Polycenter File System — HELP", Tru64 Unix managers, ORNL.
  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. ^ 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 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. ^ a b c d e For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 KB for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KB).
  6. ^ a b "Maximum CP/M-80 2.2 volume size?", Google Groups http://groups.google.com/group/comp.os.cpm/browse_thread/thread/ac56a0ae9ed64fd1, retrieved 2009-10-09 {{citation}}: Missing or empty |title= (help); Unknown parameter |tiel= ignored (help)
  7. ^ SFS file system
  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 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 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. ^ See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html
  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 GB.
  13. ^ "KB955704". 2009-01-27. Description of the exFAT file system driver update package [for 32-bit XP]
  14. ^ "msdn TexFAT File Naming Limitations". 2009-10-14.
  15. ^ 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. [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 GB.
  19. ^ 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 226 TB and the file size to 16 TB 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. ^ Docs, Apple.
  23. ^ Docs.
  24. ^ "Interviews/EricSandeen". FedoraProject. 2008-06-09. Retrieved 2009-10-09.
  25. ^ a b Depends on kernel version and arch. For 2.4 kernels the max is 2 TB. For 32-bit 2.6 kernels it is 16 TB. For 64-bit 2.6 kernels it is 8 EB.
  26. ^ ReiserFS has a theoretical maximum file size of 1 EB, but "page cache limits this to 8TB on architectures with 32 bit int"[2]
  27. ^ Note that the filename can be much longer XFS#Extended_attributes
  28. ^ a b XFS has a limitation under Linux 2.4 of 64 TB file size, but Linux 2.4 only supports a maximum block size of 2 TB. This limitation is not present under IRIX.
  29. ^ 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.
  30. ^ Varies wildly according to block size and fragmentation of block allocation groups.
  31. ^ a b NSS allows files to have multiple names, in separate namespaces.
  32. ^ 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.
  33. ^ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  34. ^ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  35. ^ This restriction might be lifted in newer versions.
  36. ^ a b c d e http://minix1.woodhull.com/faq/filesize.html
  37. ^ 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.
  38. ^ ISO_9660#Restrictions
  39. ^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GB in size. See ISO_9660#The 2.2F4 GiB file size limit
  40. ^ 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.
  41. ^ Joliet Specification
  42. ^ Implemented in later versions as an extension
  43. ^ 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.
  44. ^ a b 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.
  45. ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  46. ^ 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.
  47. ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [3]
  48. ^ As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See
  49. ^ a b c d Access-control lists and MAC labels are layered on top of extended attributes.
  50. ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  51. ^ a b c d e f g h i j 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.
  52. ^ ext4 has group descriptor and journal checksums only
  53. ^ Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
  54. ^ a b c d e f Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
  55. ^ 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.
  56. ^ 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.
  57. ^ 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.
  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 compatible attributes for use by CIFS; as well as some attributes ported from FreeBSD
  62. ^ 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.
  63. ^ a b Not applicable to file systems on a read-only medium.
  64. ^ a b 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. ^ a b c "6", Parted manual, GNU.
  68. ^ 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
  69. ^ Optional journaling of data
  70. ^ 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.
  71. ^ a b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  72. ^ 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.
  73. ^ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
  74. ^ http://www.bleepingcomputer.com/tutorials/tutorial133.html
  75. ^ 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.
  76. ^ Hard Links on HFS+
  77. ^ 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.
  78. ^ 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).
  79. ^ 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.
  80. ^ 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.
  81. ^ "Write Ahead Physical Block Logging" in NetBSD, provides metadata journalling and consistency as an alternative to softdep.
  82. ^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
  83. ^ Block level journals can be added by using gjournal module in FreeBSD.
  84. ^ a b c d UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  85. ^ Linux kernel versions 2.6.12 and newer.
  86. ^ a b Offline growing/shrinking as well as online growing: "Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)".
  87. ^ a b c Off by default.
  88. ^ 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
  89. ^ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.
  90. ^ a b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  91. ^ Optionally no on IRIX.
  92. ^ 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.
  93. ^ http://www.linux.com/archive/feed/32002
  94. ^ 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.
  95. ^ 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)
  96. ^ a b Available only in the "NFS" namespace.
  97. ^ Limited capability. Volumes can span physical disks (volume segment)
  98. ^ a b These are referred to as "aliases".
  99. ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  100. ^ When used with venti.
  101. ^ 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.
  102. ^ "How to resize ZFS".
  103. ^ 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.
  104. ^ a b 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.
  105. ^ Only for "stuffed" inodes
  106. ^ a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  107. ^ a b c Fragments were planned, but never actually implemented on ext2 and ext3.
  108. ^ 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.
  109. ^ In "extents" mode.
  110. ^ "AIX documentation: JFS data compression". IBM.
  111. ^ 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.
  112. ^ Depends on UDF implementation.
  113. ^ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  114. ^ OS/2 and eComstation FAT32 Driver
  115. ^ NTFS for Windows 98
  116. ^ OS/2 NTFS Driver
  117. ^ a b c d Sharing Disks - Windows Products
  118. ^ hfsutils at FreshPorts
  119. ^ hfs at FreshPorts
  120. ^ OS/2 HFS Driver
  121. ^ Catacombae HFSExplorer
  122. ^ DOS/Win 9x HPFS Driver
  123. ^ Win NT 4.0 HPFS Driver
  124. ^ "How to mount FFS partition under Linux - NetBSD Wiki". Wiki.netbsd.se. Archived from the original on March 19, 2008. Retrieved 2009-10-09.
  125. ^ a b Ext2 IFS for Windows provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.[4]
  126. ^ a b Ext2Fsd is an open source linux ext2/ext3 file system driver for Windows systems (NT/2K/XP/VISTA, X86/AMD64).[5]
  127. ^ a b Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[6]
  128. ^ a b c Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read write support.[7]
  129. ^ a b 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.[8]
  130. ^ OS/2 ext2 Driver
  131. ^ Ext2Read
  132. ^ http://wiki.lustre.org/index.php/Windows_Native_Client
  133. ^ http://wiki.lustre.org/index.php?title=Main_Page
  134. ^ http://wiki.lustre.org/index.php/FAQ_-_OS_Support
  135. ^ Using SAM-QFS on Linux Clients
  136. ^ ncpfs
  137. ^ "Understanding the difference between the Live File System and Mastered disc formats". Which CD or DVD format should I use?. Microsoft. Retrieved 2008-11-22.
  138. ^ ZFS on FUSE
  139. ^ http://www.osnews.com/story/22388
  140. ^ [9][dead link]
  141. ^ vmfs
  142. ^ a b c AncientFS
  143. ^ a b VMS2Linux
  144. ^ logfs