Jump to content

User:Engleman/sandbox

From Wikipedia, the free encyclopedia
< User:Engleman

This is an old revision of this page, as edited by Engleman (talk | contribs) at 01:13, 1 November 2011 (→Metadata). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

General information

File system Creator Year
introduced 		Original operating system
V6FS Bell Labs 1972 Version 6 Unix
FAT12 Microsoft 1977 Microsoft Disk BASIC
V7FS Bell Labs 1979 Version 7 Unix
FFS Kirk McKusick 1983 4.2BSD
HFS Apple Computer 1985 Mac OS
FAT16 Microsoft 1987 MS-DOS 3.31
HPFS IBM & Microsoft 1988 OS/2
ISO 9660:1988 Ecma International, Microsoft 1988 MS-DOS, Mac OS, and AmigaOS
JFS1 IBM 1990 AIX[1]
ext Rémy Card 1992 Linux
WAFL NetApp 1992 Data ONTAP
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
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
FATX Microsoft 2002 Xbox
UFS2 Kirk McKusick 2002 FreeBSD 5.0
Lustre Cluster File Systems (later Oracle Corporation) 2002 Linux
OCFS Oracle Corporation 2002 Linux
VMFS2 VMware 2002 VMware ESX Server 2.0
Fossil Bell Labs 2003 Plan 9 from Bell Labs 4
Google File System Google 2003 Linux
Reliance[4] Datalight 2003 Windows CE, VxWorks, custom ports
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
Reliance Nitro[4] Datalight 2009 Windows CE, Windows Mobile, VxWorks, Linux, custom ports
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[5] Maximum pathname length Maximum file size Maximum volume size[6]
Acorn ADFS 10 + 3 bytes Any ISO 8859-1 character except: $ & % @ \ ^ : . # * " ¦ No limit defined Template:Ntss Template:Ntss
CP/M file system 8.3 Un­known 16 "user areas", no subdirectories Template:Ntss[7] Template:Ntss to 512 MiB[7]
IBM SFS 8.8 Un­known Non-hierarchical[8] Un­known Un­known
Elektronika BK tape format 16 bytes Un­known Non-hierarchical Template:Ntss Not limited. Approx. 800KB (one side) for 90 min cassette
MicroDOS file system 14 bytes Un­known Un­known Template:Ntss Template:Ntss
Level-D 6.3 A–Z, 0–9 DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67 Template:Ntss (34,359,738,368 words (235-1); 206,158,430,208 SIXBIT bytes) Template:Ntss (approx; 64 * 178 MiB)
RT-11 6.3 A–Z, 0–9, $ Non-hierarchical Template:Ntss (65536 * 512) Template:Ntss
V6FS 14 bytes[9] Any byte except NUL and /[10] No limit defined[11] Template:Ntss[12] Template:Ntss
OS4000 8 bytes A–Z, 0–9
Period is directory separator 		No limit defined[11] Template:Ntss Template:Ntss (at least)
V7FS 14 bytes[9] Any byte except NUL and /[10] No limit defined[11] Template:Ntss[13] Template:Ntss
exFAT 255 characters [14] Any Unicode except NUL No limit defined Template:Ntss Template:Ntss, 512 TiB recommended[15]
TexFAT 247 characters Any Unicode except NUL No limit defined Template:Ntss Template:Ntss Tested[16]
FAT12 8.3 (255 UTF-16 code units with LFN)[9] Any Unicode except NUL (with LFN)[9][10] No limit defined[11] Template:Ntss Template:Ntss
FAT16 8.3 (255 UTF-16 code units with LFN)[9] Any Unicode except NUL (with LFN)[9][10] No limit defined[11] Template:Ntss Template:Ntss or 4 GiB
FAT32 8.3 (255 UTF-16 code units with LFN)[9] Any Unicode except NUL (with LFN)[9][10] No limit defined[11] Template:Ntss Template:Ntss[17]
FATX 42 bytes[9] ASCII. Unicode not permitted. No limit defined[11] Template:Ntss Template:Ntss
Fossil Un­known Un­known Un­known Un­known Un­known
MFS 255 bytes Any byte except : No path (flat filesystem) Template:Ntss Template:Ntss
HFS 31 bytes Any byte except :[18] Unlimited Template:Ntss Template:Ntss
HPFS 255 bytes Any byte except NUL[19] No limit defined[11] Template:Ntss Template:Ntss[20]
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[11] Template:Ntss[21] Template:Ntss[21]
HFS Plus 255 UTF-16 code units[22] Any valid Unicode[10][23] Unlimited Template:Ntss Template:Ntss[24][25]
FFS 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
UFS1 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
UFS2 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
ext2 255 bytes Any byte except NUL[10] and / No limit defined[11] Template:Ntss[6] Template:Ntss
ext3 255 bytes Any byte except NUL[10] and / No limit defined[11] Template:Ntss[6] Template:Ntss
ext4 256 bytes Any byte except NUL[10] and / No limit defined[11] Template:Ntss[6][26] Template:Ntss (but user tools limited to 16 TB)
Lustre 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss (on ext4) Template:Ntss (on ext4, 10 PB tested)
GPFS 255 UTF-8 codepoints Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss (4 PiB tested)
GFS 255 Any byte except NUL[10] No limit defined[11] Template:Ntss[27] Template:Ntss[27]
ReiserFS 4,032 bytes/226 characters Any byte except NUL[10] No limit defined[11] Template:Ntss[28] (v3.6), 2 GB (v3.5) Template:Ntss
NILFS 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
Reiser4 3,976 bytes Any byte except / and NUL No limit defined[11] Template:Ntss on x86 Un­known
OCFS 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
OCFS2 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
Reliance 260 bytes OS specific Template:Ntss Template:Ntss 2 TB
Reliance Nitro 1,024 bytes OS specific 1024 bytes Template:Ntss Template:Ntss
XFS 255 bytes[29] Any byte except NUL[10] No limit defined[11] Template:Ntss[30] Template:Ntss[30]
JFS1 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
JFS 255 bytes Any Unicode except NUL No limit defined[11] Template:Ntss Template:Ntss
QFS 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss[31] Template:Ntss[31]
BFS 255 bytes Any byte except NUL[10] No limit defined[11] Template:Ntss[32] Template:Ntss
AdvFS 226 characters Any byte except NUL[10] No limit defined[11] Template:Ntss Template:Ntss
ODS-5 236 bytes[33] Un­known 4,096 bytes[34] Template:Ntss Template:Ntss
UDF 255 bytes Any Unicode except NUL 1,023 bytes[35] Template:Ntss Un­known
ZFS 255 bytes Any Unicode except NUL No limit defined[11] Template:Ntss Template:Ntss
VMFS2 128 Any byte except NUL and /[10] 2,048 Template:Ntss[36] Template:Ntss
VMFS3 128 Any byte except NUL and /[10] 2,048 Template:Ntss[36] Template:Ntss
ISO 9660:1988 Level 1: 8.3,
Level 2 & 3: ~ 180 		Depends on Level[37] ~ 180 bytes? Template:Ntss (Level 1 & 2) to 8 TiB (Level 3)[38] Template:Ntss[39]
Joliet ("CDFS") 64 Unicode characters All UCS-2 code except *, /, \, :, ;, and ?[40] Un­known Template:Ntss (same as ISO 9660:1988) Template:Ntss (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 Template:Ntss
Btrfs 255 bytes Any byte except NUL Un­known Template:Ntss Template:Ntss
LTFS Un­known Un­known Un­known Un­known Un­known
LEAN 4,068 bytes[41] case sensitive, in UTF-8 (any Unicode codepoint) No limit defined Template:Ntss Template:Ntss
File system Maximum filename length Allowable characters in directory entries[5] Maximum pathname length Maximum file size Maximum volume size[6]

Metadata

File system Stores file owner POSIX file permissions Creation timestamps Last access/ read timestamps Last content modification timestamps Disk copy created Last metadata change timestamps Last archive timestamps Access control lists Security/ MAC labels Extended attributes/ Alternate data streams/ forks Checksum/ ECC
Level-D Yes Yes Yes Yes Un­known Un­known Yes Yes Yes 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[42] No No No No[43] No
FAT16 No No Yes Yes Yes No No[42] No No No No[43] No
FAT32 No No Yes Yes Yes No No[42] No No No No No
exFAT No No Yes Yes Yes Un­known Un­known No No Un­known Un­known Partial
HPFS Yes[44] No Yes Yes Yes Un­known No No No Un­known Yes No
NTFS Yes Yes[45] Yes Yes Yes No Yes No Yes Yes[46] 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[47] 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[48] Yes[48] No[49] No
UFS2 Yes Yes Yes Yes Yes Un­known Yes No Yes[48] Yes[48] 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[50] Yes[50] Yes No
ext3 Yes Yes No Yes Yes No Yes No Yes[50] Yes[50] Yes No
ext4 Yes Yes Yes Yes Yes Un­known Yes No Yes[50] Yes[50] Yes Partial[51]
Lustre Yes Yes Partial[52] Yes Yes No Yes No Yes Yes Yes Partial[53][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[50] Yes[50] 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 Yes No Yes Partial[55]
Reliance No No Yes No Yes No No No No No No Partial[56]
Reliance Nitro Linux port Linux port Yes Yes Yes No No No Linux port No Yes Partial[56]
XFS Yes Yes No Yes Yes Un­known Yes No Yes Yes[50] 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
ODS-5 Yes Yes Yes Un­known Un­known Un­known Un­known Yes Yes Un­known Yes[57] No
UDF Yes Yes Yes Yes Un­known Un­known Yes Yes Yes No Yes No
Fossil Yes Yes[58] No Yes Un­known Un­known Yes No No No No No
ZFS Yes Yes Yes Yes Yes Un­known Yes Yes Yes Yes[59] Yes[60] 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[61] No[62] Yes[63] Un­known No No No No No No
Joliet ("CDFS") No No Yes[61] No[62] Yes[63] 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 Disk 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[64] 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[65] 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 Offline[66]
FAT16 No No No No No Partial No No No No No No No Offline[66]
FAT32 No No No No No Partial No No No No No No No Offline[66]
exFAT No No Un­known No No Yes No Un­known Un­known No Un­known Un­known Un­known Un­known
GFS Yes Yes[67] Yes Yes[68] 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 Online
HPFS No No No No No Yes No Un­known No No Un­known Un­known No Un­known
NTFS Yes Yes[69] No[70] Yes[70] Yes[71] Yes Yes Partial[72] Yes Yes Partial Un­known No Online[73]
HFS No Yes[74] No No No Yes No No No No No No No Un­known
HFS Plus Yes[75] Yes No Yes[76] Partial[77] Yes Yes[78] No No No[79] No No No Offline
FFS Yes Yes No No[80] Yes Yes No No No No No No No Offline (cannot be shrunk)[81]
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 Offline (cannot be shrunk)[84]
LFS Yes Yes Yes[85] 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[86] No No No No Online[87]
ext3 Yes Yes Yes[88] Yes Yes Yes No No Yes No No No No Online[87]
ext4 Yes Yes Yes[88] Yes Yes Yes No No Yes No No No No Online[87]
Lustre Yes Yes Yes[88] Yes Yes Yes Yes in 2.0 No[54] No No[54] No[54] No[54] No[54] Online[89]
NILFS Yes Yes Yes[85] No Yes Yes Yes Yes No No Yes Un­known Un­known Un­known
ReiserFS Yes Yes No[90] Yes Yes Yes No No No No No No No Offline
Reiser4 Yes Yes Yes No Yes Yes No Un­known No Yes[91] Yes No Un­known Online (can only be shrunk offline)
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 Partial[92] No No Un­known No No Online for version 1.4 and higher
Reliance No No No[93] No No Yes No No No No Yes No No Un­known
Reliance Nitro Yes Yes No[93] No Depends on OS Yes No No No No Yes No No Un­known
XFS Yes Yes Yes Yes Yes[94] Yes No No No No No No No Online (cannot be shrunk)
JFS Yes Yes No Yes Yes[95] Yes No Yes No No Yes Un­known Un­known Online (cannot be shrunk)[96]
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[97] Yes[97] Yes[98] Yes No Yes Un­known Un­known Un­known Un­known
NWFS Yes[99] Yes[99] No No Yes[97] Yes[97] Yes[98] Un­known No No No Yes[100] Un­known Un­known
ODS-2 Yes Yes[101] No Yes No No Yes Yes No No Un­known Un­known Un­known Un­known
ODS-5 Yes Yes[101] No Yes No Yes Yes Yes Un­known No Un­known Un­known Un­known Un­known
UDF Yes Yes Yes[85] Yes[85] Yes Yes No No Yes No No No No Un­known
VxFS Yes Yes Yes No Yes Yes Yes Yes[102] 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[103] Un­known
ZFS Yes Yes Yes[104] No[104] Yes Yes No Yes No Yes Yes Yes Yes Online (cannot be shrunk)[105]
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 Planned[106] Yes Yes Work-in-Progress 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[107] 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[108]
FAT16 No No No No No No[108]
FAT32 No No No No No No
exFAT Un­known No No Un­known No No
GFS Partial[109] No No No Yes No
HPFS No No Yes No No No
NTFS Partial No Yes No Yes Yes[110]
HFS Plus No No Yes Yes No Yes
FFS 8:1[111] No No No Yes No
UFS1 8:1[111] No No No Yes No
UFS2 8:1[111] Yes No No Yes No
LFS 8:1[111] No No No Yes No
ext2 No[112] No No No Yes No[113]
ext3 No[112] No No No Yes No
ext4 No[112] 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[114] Yes Yes Yes[91]
OCFS No No Yes No Un­known No
OCFS2 No No Yes No Yes No
Reliance No No No No No No
Reliance Nitro No No Yes No Yes No
XFS No No Yes Yes Yes No
JFS Yes No Yes No Yes only in JFS1 on AIX[115]
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[116] 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[117] 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[118] Yes No Yes Yes Yes
File system Block suballocation Variable file block size[107] 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 Windows CE Windows Mobile VxWorks HP-UX
FAT12 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known Yes Yes[119] Un­known Yes[120] Un­known
FAT16 Yes Yes Yes Yes Yes Yes Yes Yes Partial on diskettes only, through dos* commands Un­known Yes Yes[119] Yes Yes[120] Un­known
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 third-party app[121] Yes[119] Yes Yes[120] Un­known
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 Yes No Un­known Un­known
NTFS with third-party driver[122] Yes Yes Kernel 2.2 or newer, or with NTFS-3G or ntfsprogs No with NTFS-3G with NTFS-3G with NTFS-3G with NTFS-3G on Opensolaris Un­known Un­known Partial read-only third-party driver[123] with 3rd-party driver[124] No Un­known Un­known
HFS with third-party app[125] with third-party app[125] Yes Yes Yes with third-party app[126][127] Un­known Un­known Un­known No with third-party app[128] No No No Un­known
HFS Plus with third-party app[125] with third-party app[125] Partial - write support occurs if journal is empty, but requires a force mount. Yes since Mac OS 8.1 Yes Partial read-only third-party app[129] Un­known Un­known Un­known No with third-party app No No No Un­known
HPFS Partial read-only third-party driver[130] included until v3.51, third-party driver until 4.0[131] Yes No Un­known Yes Un­known Un­known Un­known Un­known Yes No Un­known Un­known Un­known
FFS Un­known Un­known Yes[132] No Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
UFS1 Un­known Un­known Partial - read only No Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known No Un­known
UFS2 Un­known Un­known Partial - read only No No Yes Un­known Un­known Un­known Un­known Un­known Un­known Un­known No Un­known
ext2 Un­known with Ext2Fsd (complete)[133] or Ext2 IFS (partial, no large inodes)[134] or Ext2Read (read-only, also on LVM2)[135] Yes No with fuse-ext2[136], ExtFS[137] and ext2fsx[138] Yes Un­known Un­known Un­known Un­known third-party app[139] with 3rd-party app[140] with 3rd-party app[140] Un­known Un­known
ext3 Un­known with Ext2Fsd (complete)[133] or Ext2 IFS (partial, no large inodes)[134] or Ext2Read (read-only, also on LVM2)[135] Yes No with fuse-ext2[136] and ExtFS[137] Yes Un­known Yes Un­known Un­known Un­known with 3rd-party app[140] with 3rd-party app[140] Un­known Un­known
ext4 No with Ext2Fsd (partial, no extents)[133], Ext2 IFS (partial, no large inodes)[134] or Ext2Read (read-only, also on LVM2)[135] Yes since kernel 2.6.28 No with fuse-ext2 (partial)[136] and ExtFS (full read/write)[137] No Un­known Un­known Un­known Un­known Un­known No Un­known Un­known Un­known
Lustre No Partial - under development[141] Yes[142] No Partial - via FUSE Partial - via FUSE No Partial - under development[143] No No No No No Un­known Un­known
GFS Un­known Un­known Yes No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
NILFS Un­known Un­known Yes since kernel 2.6.30 No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
ReiserFS Un­known Partial with third-party app Yes No No Partial - read only Un­known Un­known Un­known Un­known Un­known with 3rd-party app[140] with 3rd-party app[140] Un­known Un­known
Reiser4 Un­known Un­known with a kernel patch No No No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
OCFS Un­known Un­known Yes No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
OCFS2 Un­known Un­known Yes No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
Reliance No No No No No No No No No No No Yes No Yes Un­known
Reliance Nitro No No Yes No No No No No No No No Yes Yes Yes Un­known
XFS Un­known Un­known Yes No Un­known Partial Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
JFS Un­known Un­known Yes No No No Un­known Un­known Yes Un­known Yes No No Un­known
QFS Un­known Un­known via client software[144] No Un­known No Un­known Yes Un­known Un­known Un­known No No Un­known Un­known
BFS Un­known Un­known Partial - read-only No Un­known No Yes Un­known Un­known Un­known Un­known No No Un­known Un­known
NSS Un­known Un­known with Novell OES2[citation needed] No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
NWFS Un­known Un­known via ncpfs client software[145] No Un­known Yes Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
UDF Partial read-only support of UDF 1.02 since Win98 and WinME Yes[146] Yes Yes since Mac OS 9 Yes Yes Un­known Yes Un­known Un­known Un­known Yes Un­known Un­known Un­known
VxFS Un­known Un­known Yes No Un­known No Un­known Yes Yes Un­known Un­known No No Un­known Yes
Fossil No No No No No No No No No No No No No No Un­known
ZFS No No with 3rd Party kernel module [147] or FUSE[148] No with free 3rd-party software[149] Yes No Yes No No No Un­known Un­known Un­known Un­known
IBM HFS No No No No No No No No No Yes No Un­known Un­known Un­known Un­known
IBM zFS No No No No No No No No No Yes No Un­known Un­known Un­known Un­known
IBM GPFS[150] No Yes Yes No No No No No Yes No No Un­known Un­known Un­known Un­known
VMFS2 Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
VMFS3 Un­known Un­known Partial read-only with vmfs[151] No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
DECtape Un­known Un­known with AncientFS[152] No with AncientFS[152] with AncientFS[152] Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
Level-D Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
RT-11 Un­known Un­known Un­known No Un­known No Un­known Un­known Un­known Un­known Un­known No No Yes Un­known
ODS-2 Un­known Un­known Partial read-only with tool or kernel module[153] No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
ODS-5 Un­known Un­known Partial read-only with kernel module[153] No Un­known No Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known Un­known
LFS Un­known Un­known with logfs[154] and others No Un­known No Un­known Un­known Un­known Un­known Un­known No No Un­known Un­known
Btrfs No No Yes No No No No No No No No No No Un­known Un­known
LTFS Un­known Un­known Yes No Yes No No No No No No No No Un­known Un­known
File system Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX z/OS OS/2 Windows CE Windows Mobile VxWorks HP-UX
  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 Specifications for the Reliance file systems are available here.
  5. ^ 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.
  6. ^ 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).
  7. ^ a b "Maximum CP/M-80 2.2 volume size?", comp.os.cpm, Google Groups, retrieved 2009-10-09
  8. ^ SFS file system
  9. ^ 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.
  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 In these filesystems the directory entries named "." and ".." have special status. Directory entries with these names are not prohibited, and indeed exist as normal directory entries in the on-disk data structures. However, they are mandatory directory entries, with mandatory values, that are automatically created in each directory when it is created; and directories without them are considered corrupt.
  11. ^ 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 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. Most Windows programms will fail when full path exceeds 255 characters (including Explorer and CMD.EXE). Linux has a pathname limit of 4,096.
  12. ^ See manual http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/V/fs.html
  13. ^ 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.
  14. ^ Table "Limits" states a maximum of 255 Unicode characters for the filename [1]
  15. ^ "KB955704". 2009-01-27. Description of the exFAT file system driver update package [for 32-bit XP]
  16. ^ "msdn TexFAT File Naming Limitations". 2009-10-14.
  17. ^ 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. [2]
  18. ^ 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 /.
  19. ^ 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.
  20. ^ 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.
  21. ^ 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.
  22. ^ 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.
  23. ^ 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.
  24. ^ Docs, Apple.
  25. ^ Docs.
  26. ^ "Interviews/EricSandeen". FedoraProject. 2008-06-09. Retrieved 2009-10-09.
  27. ^ 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.
  28. ^ ReiserFS has a theoretical maximum file size of 1 EB, but "page cache limits this to 8TB on architectures with 32 bit int"[3]
  29. ^ Note that the filename can be much longer XFS#Extended_attributes
  30. ^ 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.
  31. ^ 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.
  32. ^ Varies wildly according to block size and fragmentation of block allocation groups.
  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 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.
  37. ^ ISO 9660#Restrictions
  38. ^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB in size. See ISO 9660#The 2/4 GiB file size limit
  39. ^ 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.
  40. ^ Joliet Specification
  41. ^ [4]
  42. ^ 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.
  43. ^ 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.
  44. ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  45. ^ 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.
  46. ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [5]
  47. ^ As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See
  48. ^ a b c d Access-control lists and MAC labels are layered on top of extended attributes.
  49. ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  50. ^ a b c d e f g h i 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.
  51. ^ ext4 has group descriptor and journal checksums only
  52. ^ Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
  53. ^ Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
  54. ^ a b c d e f Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
  55. ^ ocfs2 computes and validates checksums of metadata objects like inodes and directories. It also stores an error correction code capable to fixing single-bite errors.
  56. ^ a b CRCs are employed for certain types of metadata.
  57. ^ Record Management Services (RMS) attributes include record type and size, among many others.
  58. ^ 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.
  59. ^ 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.
  60. ^ 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
  61. ^ 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.
  62. ^ a b Not applicable to file systems on a read-only medium.
  63. ^ a b Available only if the file has an Extended Attribute block.
  64. ^ Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
  65. ^ 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.
  66. ^ a b c "6", Parted manual, GNU.
  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. ^ a b 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. ^ http://www.bleepingcomputer.com/tutorials/tutorial133.html
  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+
  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 journaling and consistency as an alternative to softdep.
  81. ^ OpenBSD growfs(8) manpage
  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. ^ FreeBSD growfs(8) manpage
  85. ^ a b c d UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  86. ^ Linux kernel versions 2.6.12 and newer.
  87. ^ a b c Offline growing/shrinking as well as online growing: "Linux man page for resize2fs(8) (from e2fsprogs 1.41.9)".
  88. ^ a b c Off by default.
  89. ^ 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
  90. ^ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.
  91. ^ a b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  92. ^ OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
  93. ^ a b File system implements reliability via atomic transactions.
  94. ^ Optionally no on IRIX.
  95. ^ 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.
  96. ^ http://www.linux.com/archive/feed/32002
  97. ^ 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.
  98. ^ 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)
  99. ^ a b Available only in the "NFS" namespace.
  100. ^ Limited capability. Volumes can span physical disks (volume segment)
  101. ^ a b These are referred to as "aliases".
  102. ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  103. ^ When used with venti.
  104. ^ 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.
  105. ^ "How to resize ZFS".
  106. ^ McPherson, Amanda (2009-06-22), A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, retrieved 2009-09-01
  107. ^ 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.
  108. ^ 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.
  109. ^ Only for "stuffed" inodes
  110. ^ Only if formatted with 4kB-sized clusters or smaller
  111. ^ a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  112. ^ a b c Fragments were planned, but never actually implemented on ext2 and ext3.
  113. ^ 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.
  114. ^ In "extents" mode.
  115. ^ "AIX documentation: JFS data compression". IBM.
  116. ^ 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.
  117. ^ Depends on UDF implementation.
  118. ^ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  119. ^ a b c Files, Databases, and Persistent Storage. MSDN.
  120. ^ a b c Via dosFs.
  121. ^ OS/2 and eComstation FAT32 Driver
  122. ^ NTFS for Windows 98
  123. ^ OS/2 NTFS Driver
  124. ^ Tuxera NTFS for Windows CE. See article and announcement.
  125. ^ a b c d Sharing Disks - Windows Products
  126. ^ hfsutils at FreshPorts
  127. ^ hfs at FreshPorts
  128. ^ OS/2 HFS Driver
  129. ^ Catacombae HFSExplorer
  130. ^ DOS/Win 9x HPFS Driver
  131. ^ Win NT 4.0 HPFS Driver
  132. ^ "How to mount FFS partition under Linux - NetBSD Wiki". Wiki.netbsd.se. Archived from the original on March 19, 2008. Retrieved 2009-10-09.
  133. ^ a b c Ext2Fsd is an open source linux ext2/ext3/ext4 file system driver for Windows systems (NT/2K/XP/VISTA, X86/AMD64). Currently does not support extents, a default feature of ext4. [6]
  134. ^ a b c Ext2 IFS for Windows provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista. Does not support inodes above 128.[7]
  135. ^ a b c Ext2Read is an explorer-like utility to explore ext2/ext3/ext4 file systems. It supports extents, large inodes, and LVM2 volumes.Ext2Read
  136. ^ a b c Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[8]
  137. ^ a b c Paragon ExtFS for Mac is a low-level file system driver specially developed to bridge file system incompatibility between Linux and Mac by providing full read/write access to the Ext2, Ext3 and Ext4 file systems under Mac OS X.[9]
  138. ^ Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[10]
  139. ^ OS/2 ext2 Driver
  140. ^ a b c d e f See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
  141. ^ http://wiki.lustre.org/index.php/Windows_Native_Client
  142. ^ http://wiki.lustre.org/index.php?title=Main_Page
  143. ^ http://wiki.lustre.org/index.php/FAQ_-_OS_Support
  144. ^ Using SAM-QFS on Linux Clients
  145. ^ ncpfs
  146. ^ "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.
  147. ^ Native ZFS for Linux
  148. ^ ZFS on FUSE
  149. ^ Mac ZFS
  150. ^ [11]
  151. ^ vmfs
  152. ^ a b c AncientFS
  153. ^ a b VMS2Linux
  154. ^ logfs
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=User:Engleman/sandbox&oldid=458389485"