Baike


中文
ChineseEnglishJapanese

文件系统的对比

维基媒体列表条目

下列表格对比了一系列文件系统的一般和技术资料，文件系统的具体信息参见链接文章。

一般资料编辑

文件系统开发者发布年份原操作系统许可
DECtapeDEC1964PDP-6 Monitor
Level-DDEC1968TOPS-10
George3ICT (即之后的 ICL)1968George 3
ODS-1DEC1972RSX-11
RT-11 file systemDEC1973RT-11
DOS (GEC)GEC1973Core Operating System
CP/M file system蓋瑞·基爾多1974CP/M
V6FSBell Labs1975Version 6 Unix
OS4000GEC1977OS4000
FAT (8-bit)Marc McDonald, Microsoft1977Microsoft Standalone Disk BASIC-80
DOS 3.xApple Computer1978Apple DOS
PascalApple Computer1978Apple Pascal
CBM DOSCommodore1978Microsoft BASIC (for CBM PET)
V7FSBell Labs1979Version 7 Unix
DOS 1.0Atari Corporation1979Atari 8-bit family
ODS-2DEC1979OpenVMS
FAT12Tim Paterson, Seattle Computer Products1980QDOS, 86-DOS
DOMAIN file systemApollo Computer1981Domain/OS (Aegis, Domain)
AFSCarnegie Mellon University1982Multiplatform MultoOS
DFSAcorn Computers Ltd1982Acorn BBC Micro MOS
ADFSAcorn Computers Ltd1983Acorn Electron (later Arthur RISC OS)
FFSKirk McKusick19834.2BSD
ProDOSApple Computer1983ProDOS 8
MFSApple Computer1984Mac OS
FAT16Microsoft, IBM1984PC DOS 3.0/MS-DOS 3.0
Elektronika BK tape formatNPO "Scientific centre" (now Sitronics)1985Vilnius Basic, BK monitor program
HFSApple Computer1985Mac OS
Amiga OFS[12]Metacomco for Commodore1985Amiga OS
High SierraEcma International1985MS-DOS, Mac OS
NWFSNovell1985NetWare 286
FAT16BCompaq1987Compaq MS-DOS 3.31, DR DOS 3.31
MINIX V1 FSAndrew S. Tanenbaum1987MINIX 1.0
Amiga FFSCommodore1988Amiga OS 1.3
HPFSIBM & Microsoft1988OS/2
ISO 9660:1988Ecma International, Microsoft1988MS-DOS, Mac OS, and AmigaOS
JFS1IBM1990AIX[1]
VxFSVERITAS, (now Symantec)1991为 Unix System Laboratories、HP-UX[2] 开发
extRémy Card1992Linux
WAFLNetApp1992Data ONTAP
MINIX V2 FSAndrew S. Tanenbaum1992MINIX 1.6 and 2.0
AdvFSDEC1993[3]Digital Unix
NTFS Version 1.0Microsoft, Tom Miller, Gary Kimura1993Windows NT 3.1proprietary
LFSMargo Seltzer1993Berkeley Sprite
ext2Rémy Card1993Linux, Hurd
UFS1Kirk McKusick19944.4BSD
XFSSGI1994IRIX
HFS (Hierarchical File System)IBM1994MVS/ESA (now z/OS)
Rock RidgeYoung Minds Inc.1994Linux, Mac OS, Amiga OS, and FreeBSD
Joliet ("CDFS")Microsoft1995Microsoft Windows, Linux, Mac OS, and FreeBSD
PFSMichiel Pelt1996AmigaOS
RomeoAdaptec1996Microsoft Windows
UDFISO/ECMA/OSTA1995-
FAT32Microsoft1996Windows 95b[4]
QFSLSC Inc, Sun Microsystems1996Solaris
IBM Spectrum ScaleIBM1998AIX, Linux, Windows
Be File SystemBe Inc., D. Giampaolo, C. Meurillon1996BeOS
HFS PlusApple Computer1998Mac OS 8.1
NSSNovell1998NetWare 5
PolyServe File System (PSFS)PolyServe1998Windows, Linux
ODS-5DEC1998OpenVMS 7.2
SFSJohn Hendrikx1998AmigaOS, AROS, MorphOS
ext3Stephen Tweedie1999Linux
ISO 9660:1999Ecma International, Microsoft1999Microsoft Windows, Linux, Mac OS X, FreeBSD, and AmigaOS
JFSIBM1999OS/2 Warp Server for e-business
GFSSistina (Red Hat)2000Linux
Melio FSSanbolic2001Windows
NTFS Version 3.1Microsoft2001Windows XPproprietary
ReiserFSNamesys2001Linux
zFSIBM2001z/OS (backported to OS/390)
FATXMicrosoft2002Xbox
UFS2Kirk McKusick2002FreeBSD 5.0
LustreCluster File Systems (later Oracle Corporation)2002Linux
OCFSOracle Corporation2002Linux
VMFS2VMware2002VMware ESX Server 2.0
ext3cowZachary Peterson2003Linux
FossilBell Labs2003Plan 9 from Bell Labs, 4th EditionLPL
Google File SystemGoogle2003Linux
PramFSMontaVista2003Linux
Reliance[5]Datalight2003Windows CE, VxWorks, custom ports
VxCFSVERITAS, (now Symantec)2004AIX, HP-UX, Solaris, Linux
ZFSSun Microsystems2004SolarisCDDL
Reiser4Namesys2004Linux
Non-Volatile File SystemPalm, Inc.2004Palm OS Garnet
MINIX V3 FSAndrew S. Tanenbaum2005MINIX 3
OCFS2Oracle Corporation2005Linux
NILFSNTT2005Linux
VMFS3VMware2005VMware ESX Server 3.0
GFS2Red Hat2006Linux
ext4Various2006Linux
exFATMicrosoft2006, 2009Windows CE 6.0, Windows XP SP3, Windows Vista SP1proprietary
TexFAT/TFATMicrosoft2006Windows CE 6.0
BtrfsOracle Corporation2007LinuxGPL
CephSage Weil, Inktank Storage, Red Hat2007, 2012Linux
WBFSkwiirk and Waninkoko (Wii homebrew)2008Nintendo WII
HAMMERMatthew Dillon2008DragonFly BSD
Tux3Various2008Linux
UBIFSNokia with help of University of Szeged2008Linux
Oracle ACFSOracle Corporation2009Linux - Red Hat Enterprise Linux 5 and Oracle Enterprise Linux 5 only
Reliance Nitro[5]Datalight2009Windows CE, Windows Mobile, VxWorks, Linux, custom portsproprietary
LTFSIBM2010Linux, Mac OS X, planned Microsoft Windows,LGPL
IlesfayFSIlesfay Technology Group2011Microsoft Windows, planned Red Hat Enterprise Linux
VMFS5VMware2011VMware ESXi 5.0tux 3 stats
ReFSMicrosoft2012, 2013Windows 2012 Serverproprietary
Lanyard FilesystemDan Luedtke2012Linux
F2FSSamsung2012LinuxGPLv2
File systemCreatorYear
introduced		Original operating systemLicense

限制编辑

文件系统最大文件名称长度路径字符限制[6]最大路径名长度最大文件大小最大卷大小[7]
Acorn ADFS10 bytesAny ISO 8859-1 character except: SPACE $ & % @ \ ^ : . # * " ¦No limit defined512 MB or 4 GB[8]512 MB or 4 GB[9]
AdvFS226 charactersAny byte except NUL[10]No limit defined[11]16 TB16 TB
Apple DOS 3.x30 bytesAny byte except NUL30 B, no subdirectories (105 files per disk)未知140 kB DOS 3.3 (assuming standard 35 tracks)
113.75 kB DOS 3.1, 3.2
Apple ProDOS15 bytesA-Z, a-z, 0-9, and period64 B, including slashes[12][13]16 MB32 MB
BFS255 bytesAny byte except NUL[10]No limit defined[11]260 GB[14]2 EB
Btrfs255 bytesAny byte except NUL未知16 EB16 EB
CBM DOS16 bytesAny byte except NULNon-hierarchical16 MB16 MB
CP/M file system8.3any byte except: SPACE < > . , ; : = ? * [ ] % | ( ) / \[15]16 "user areas", no subdirectories8 MB[16]8 MB to 512 MB[16]
DECtape6.3A–Z, 0–9DTxN:FILNAM.EXT = 15369280 B (577 * 640)369920 B (578 * 640)
DOS (GEC)8 bytesA–Z, 0–9Non-hierarchical64 MB64 MB
Elektronika BK tape format16 bytes未知Non-hierarchical64 kB800 kB (approx) per side for 90 min cassette (limited only by tape length)
exFAT255 characters[17]Any Unicode except NULNo limit defined127 PB64 ZB, 512 TB recommended[18]
ext2255 bytesAny byte except NUL[10] and /No limit defined[11]2 TB[7]32 TB
ext3255 bytesAny byte except NUL[10] and /No limit defined[11]2 TB[7]32 TB
ext3cow255 bytesAny byte except NUL,[10] / and @No limit defined[11]2 TB[7]32 TB
ext4255 bytesAny byte except NUL[10] and /No limit defined[11]16 TB[7][19]1 EB[20]
TexFAT247 charactersAny Unicode except NULNo limit defined2 GB500 GB Tested[21]
F2FS255 bytes未知未知3.94 TB16 TB
FAT128.3 (255 UCS-2 code units with VFAT LFNs)[22]Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[10][22]No limit defined[11]32 MB (256 MB)32 MB (256 MB with 4K sectors and 64 KB clusters)
FAT168.3 (255 UCS-2 code units with VFAT LFNs)[22]Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[10][22]No limit defined[11]2 GB (4 GB with LFS)2 GB or 4 GB
FAT328.3 (255 UCS-2 code units with VFAT LFNs)[22]Any byte except for values 0-31, 127 (DEL) and: " * / : < > ? \ | + , . ; = [] (lowcase a-z are stored as A-Z). With VFAT LFN any Unicode except NUL[10][22]No limit defined[11]2 GB (4 GB with LFS)2 TB[23] (16 TB)
FATX42 bytes[22]ASCII. Unicode not permitted.No limit defined[11]2 GB2 GB
FFS255 bytesAny byte except NUL[10]No limit defined[11]8 ZB8 ZB
Fossil65535 bytes of UTF-8 charactersAny Unicode except 0-31No limit defined8 EB未知
GFS255Any byte except NUL[10]No limit defined[11]8 EB[24]8 EB[24]
IBM Spectrum Scale255 UTF-8 codepointsAny byte except NUL[10] and /No limit defined[11]8 EB8 YB (18 PB tested)
HAMMER未知未知未知未知1 EB
HFS31 bytesAny byte except :[25]Unlimited2 GB2 TB
HFS Plus255 UTF-16 code units[26]Any valid Unicode[10][27]Unlimited8 EB8 EB[28][29]
High Sierra未知未知未知未知未知|-
HPFS255 bytesAny byte except NUL[30]No limit defined[11]2 GB2 TB[31]
ISO 9660:1988Level 1: 8.3,
Level 2 & 3: ~ 180		Depends on Level[32]~ 180 bytes?4 GB (Level 1 & 2) to 8 TB (Level 3)[33]8 TB[34]
ISO 9660:1999未知 (207?)未知未知未知未知未知
Joliet ("CDFS")64 Unicode charactersAll UCS-2 code except * / \ : ; and ?[35]未知4 GB (same as ISO 9660:1988)8 TB (same as ISO 9660:1988)
Lanyard Filesystem255 bytesAny byte except NUL and /[10]No limit defined64 ZB128 kB to 64 ZB[36]
LEAN4,068 bytes[37]case sensitive, in UTF-8 (any Unicode codepoint)No limit defined8 EB8 EB
Level-D6.3A–Z, 0–9DEVICE:FILNAM.EXT[PROJECT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 6724 GB (34,359,738,368 words (235-1); 206,158,430,208 SIXBIT bytes)12 GB (approx; 64 * 178 MB)
LTFS未知未知未知未知未知
Lustre255 bytesAny byte except NUL[10] and /No limit defined[11]32 PB (on ext4)1 YB (55 PB tested)
JFS1255 bytesAny byte except NUL[10]No limit defined[11]8 EB4 PB
JFS255 bytesAny Unicode except NULNo limit defined[11]4 PB32 PB
MFS255 bytesAny byte except :No path (flat filesystem)226 MB226 MB
MicroDOS file system14 bytes未知未知16 MB32 MB
MINIX V1 FS14 or 30 bytes, set at filesystem creation timeAny byte except NUL[10]No limit defined[11]64 MB[38]64 MB[38]
MINIX V2 FS14 or 30 bytes, set at filesystem creation timeAny byte except NUL[10]No limit defined[11]4 GB[38]1 GB, then 2 TB[38]
MINIX V3 FS60 bytesAny byte except NUL[10]No limit defined[11]4 GB16 TB[38]
NILFS255 bytesAny byte except NUL[10]No limit defined[11]8 EB8 EB
NSS226 charactersDepends on namespace used[39]Only limited by client8 TB8 TB
NTFS255 characters[40][41][42]Depends on namespace used[40][41][42][43]32,767 Unicode characters with each path component (directory or filename) commonly up to 255 characters long[11]16 EB[44]16 EB[44]
NWFS80 bytes[45]Depends on namespace used[39]No limit defined[11]4 GB1 TB
OCFS255 bytesAny byte except NUL[10]No limit defined[11]8 TB8 TB
OCFS2255 bytesAny byte except NUL[10]No limit defined[11]4 PB4 PB
ODS-5236 bytes[46]未知4,096 bytes[47]2 TB2 TB
OS40008 bytesA–Z, 0–9
Period is directory separator		No limit defined[11]2 GB1 GB (at least)
PramFS31 bytesAny byte except NUL未知1 GB8 EB
QFS255 bytesAny byte except NUL[10]No limit defined[11]16 EB[48]4 PB[48]
ReFS 32,767 Unicode characters (255 Unicode characters in Windows 8/8.1)[49]未知 32,767 Unicode characters in each path component16 EB1 YB with 64 kB cluster size (264 × 64 × 210). Windows stack addressing allows 16 EB
ReiserFS4,032 bytes/226 charactersAny byte except NUL[10]No limit defined[11]8 TB[50] (v3.6), 2 GB (v3.5)16 TB
Reiser43,976 bytesAny byte except / and NULNo limit defined[11]8 TB on x86未知
Reliance260 bytesOS specific260 B4 GB2 TB
Reliance Nitro1,024 bytesOS specific1024 bytes32 TB32 TB
RT-116.3A–Z, 0–9, $Non-hierarchical32 MB (65536 * 512)32 MB
IBM SFS8.8未知Non-hierarchical[51]未知未知
UDF255 bytesAny Unicode except NUL1,023 bytes[52]16 EB2 TB (hard disk), 8 TB (optical disc)[53][54]
UFS1255 bytesAny byte except NUL[10]No limit defined[11]226 TB226 TB
UFS2255 bytesAny byte except NUL[10]No limit defined[11]32 PB1 YB
V6FS14 bytes[55]Any byte except NUL and /[10]No limit defined[11]16 MB[56]2 TB
V7FS14 bytes[57]Any byte except NUL and /[10]No limit defined[11]1 GB[58]2 TB
VxFS255 bytesAny byte except NUL[10]No limit defined[11]256 TB256 TB
VMFS2128Any byte except NUL and /[10]2,0484 TB[59]64 TB
VMFS3128Any byte except NUL and /[10]2,0482 TB[59]64 TB
XFS255 bytes[60]Any byte except NUL[10]No limit defined[11]8 EB[61]8 EB[61]
ZFS255 bytesAny Unicode except NULNo limit defined[11]16 EB256 ZB
File systemMaximum filename lengthAllowable characters in directory entries[6]Maximum pathname lengthMaximum file sizeMaximum volume size[7]

元数据编辑

文件系统Stores file ownerPOSIX file permissionsCreation timestampsLast access/ read timestampsLast content modification timestampsDisk copy createdLast metadata change timestampsLast archive timestampsAccess control listsSecurity/ MAC labelsExtended attributes/ Alternate data streams/ forksChecksum/ ECCMax Timestamp Resolution
AdvFS是是否是是未知是否是否是否未知
Be File System是是是否未知未知否否否否是否未知
Btrfs是是是是是未知是未知是是是是1 nanosecond
CBM DOS否否否否否否否否否否否否未知
CP/M file system否否是[62]否未知未知否否否否否否未知
DECtape否否是否未知未知否否否否否否未知
DOS (GEC)是否是是是未知否否否否否否未知
Elektronika BK tape format否否否否未知未知否否否否否是未知
ext2是是否是是未知是否是[63]是[63]是否1 second
ext3是是否是是否是否是[63]是[63]是否1 second
ext3cow是是否是是否是否是[63]是[63]是否1 second
ext4是是是是是未知是否是[63]是[63]是部份[64]1 nanosecond
exFAT否否是是是否未知否否未知未知部份10 milliseconds
FAT12否[65]否[66]部份[67]部份[67]是是否[68]否否否否[69]否10 milliseconds
FAT16否[65]否[66]部份[67]部份[67]是是否[68]否否否否[69]否10 milliseconds
FAT32否否部份[67]部份[67]是是否[68]否否否否否10 milliseconds
FFS是是否是是未知是否否否否否未知
Fossil是是[70]否是是未知是否否否否否1 second
GPFS是是是是是未知是否是是是是1 nanosecond
GFS是是否是未知未知是否是[63]是[63]是否未知
HFS否否是否是否否是否否是否未知
HFS Plus是是是是是否是是是是[71]是否1 second
HPFS是[72]否是是是未知否否否未知是否未知
High Sierra否否是否未知未知否否否否否否未知
ISO 9660:1988否否是[73]否[74]是[75]未知否否否否否否未知
ISO 9660:1999否否是否未知未知否否否否否否未知
JFS是是是是是未知是否是是是否1 second
Joliet ("CDFS")否否是[73]否[74]是[75]未知否否否否否否未知
Lanyard Filesystem否否是否是否是否否否否否1 nanosecond
Level-D是是是是未知未知是是是否否否未知
LFS是是否是是未知是否否否否否未知
Lustre是是部份[76]是是否是否是是是部份[77][78]未知
NILFS是是是否未知未知是否Planned否Planned是未知
NTFS是是[79]是是是否是否是是[80]是否100 nanoseconds
NSS是是是[81]是[81]未知未知是是[81]是未知是[82][83]否未知
NWFS是未知是[81]是[81]未知未知是是[81]是未知是[82][83]否未知
OCFS否是否否未知未知是是否否否否未知
OCFS2是是否是未知未知是否是否是部份[84]未知
ODS-5是是是未知未知未知未知是是未知是[85]否未知
OS4000是否是是是未知否否否否否否未知
PramFS是是否是是未知是否是是是是1 second
QFS是是是是未知未知是是是否是否未知
ReiserFS是是否是是否否否否否否否未知
Reiser4是是否是是未知是否否否否否未知
Reliance否否是否是否否否否否否部份[86]未知
Reliance NitroLinux portLinux port是是是否否否Linux port否是部份[86]未知
UDF是是是是未知未知是是是否是否未知
UFS1是是否是是未知是否是[87]是[87]否[88]否未知
UFS2是是是是是未知是否是[87]是[87]是否未知
V6FS是是否是是未知是否否否否否未知
V7FS是是否是是未知是否否否否否未知
VMFS2是是否是未知未知是否否否否否未知
VMFS3是是否是未知未知是否否否否否未知
VxFS是是是是是未知是否是未知是[63]否未知
XFS是是否是是未知是否是是[63]是部份1 nanosecond
ZFS是是是是是未知是是是是[89]是[90]是1 nanosecond
File systemStores file ownerPOSIX file permissionsCreation timestampsLast access/read timestampsLast content modification timestampsDisk copy createdLast metadata change timestampsLast archive timestampsAccess control listsSecurity/ MAC labelsExtended attributes/ Alternate data streams/ forksChecksum/ ECCMax Timestamp Resolution

特点编辑

File systemHard linksSymbolic linksBlock journalingMetadata-only journalingCase-sensitiveCase-preservingFile Change LogSnapshotXIPEncryptionCOWIntegrated LVMData deduplicationVolumes are resizeable
Be File System否是否是是是未知否否否否否否未知
Btrfs是是否否是是是是否Planned[91]是是是 (via bedup)[92]Online
CBM DOS否否否否是是否否否否否否否否
CP/M file system否否否否否否否否否否否否否未知
DECtape否否否否否否否否否否否否否未知
DOS (GEC)否否否否否否否否否否否否否未知
ext2是是否否是是否否是[93]否否否否Offline[94]
ext3是是是[95]是是是否否是是[來源請求]否否否Online (can only be shrunk offline)[94]
ext3cow是是是[95]是是是未知是未知是是否否未知
ext4是是是[95]是是是否否是是[來源請求]否否否Online (can only be shrunk offline)[94]
exFAT否否否否否是否未知未知否未知未知未知未知
FAT12否否否否否部份否否否否否否否Offline[96]
FAT16否否否否否部份否否否否否否否Offline[96]
FAT32否否否否否部份否否否否否否否Offline[96]
FFS是是否否[97]是是否否否否否否否Offline (cannot be shrunk)[98]
Fossil否否否否是是是是否否是[99]否是[99]Offline[99]
GFS是是[100]是是[101]是是否否否否未知未知未知Online
GPFS是是否是是是是是是是是是否Online
HAMMER是是未知未知是是未知是未知未知未知未知On demand未知
HFS否是[102]否否否是否否否否否否否未知
HFS Plus是[103]是否是[104]部份[105]是是[106]否否是[107]否否否是[108]
HPFS否否否否否是否未知否否未知未知否未知
JFS是是否是是[109]是否是否否否未知未知Online (cannot be shrunk)[110]
Lanyard Filesystem否否否否是是否否否否否否否Offline (cannot be shrunk)
Level-D否否否否否否否否否否未知未知未知未知
LFS是是是[111]否是是否否否否未知未知未知未知
Lustre是是是[95]是是是是 in 2.0 and later否[78]否否否[78]否[78]否[78]Online[112]
NILFS是是是[111]否是是是是否否是未知未知Online (since Linux-3.x and nilfs-utils 2.1)
NSS是是未知是是[113]是[113]是[114]是否是未知未知未知未知
NTFS是是[115]否[116]是[116]是[117]是是部份[118]是是部份否是 (Windows Server 2012)[119]Online[120]
NWFS是[121]是[121]否否是[113]是[113]是[114]未知否否否是[122]未知未知
OCFS否是否否是是否否否否未知未知未知未知
OCFS2是是是是是是否部份[123]否否未知否否Online for version 1.4 and higher
ODS-2是是[124]否是否否是是否否未知未知未知未知
ODS-5是是[124]否是否是是是未知否未知未知未知未知
OS4000否是[125]否否否否否否否否否否否未知
PramFS否是否否是是否否是否否否否否
QFS是是否是是是否否否否未知未知未知未知
ReiserFS是是否[126]是是是否否否否否否否Online
Reiser4是是是否是是否未知否是[127]是否未知Online (can only be shrunk offline)
Reliance否否否[128]否否是否否否否是否否未知
Reliance Nitro是是否[128]否依情況 on OS是否否否否是否否未知
RT-11否否否否否否否否否否否否否未知
UDF是是是[111]是[111]是是否否是否否否否未知
UFS1是是否否是是否否否否否否否未知
UFS2是是否否[129][130][131]是是否是未知否否否否Offline (cannot be shrunk)[132]
V6FS是否否否是是否否否否否否否未知
V7FS是否[133]否否是是否否否否否否否未知
VxFS是是是否是是是是[134]未知否未知未知是未知
VMFS2是是否是是是否否否否未知未知未知未知
VMFS3是是否是是是否否否否未知未知未知未知
XFS是是是是是[135]是否否否否否否否Online (cannot be shrunk)
ZFS是是是[136]否[136]是是否是否是是是是Online (cannot be shrunk)[137]
File systemHard linksSymbolic linksBlock journalingMetadata-only journalingCase-sensitiveCase-preservingFile Change LogSnapshottingXIPEncryptionCOWIntegrated LVMData deduplicationVolumes are resizeable

Allocation and layout policies编辑

File systemBlock suballocationVariable file block size[138]ExtentsAllocate-on-flushSparse filesTransparent compression
Be File System否否是否未知否
Btrfs部份[139]否是是是是
CBM DOS否部份[140]否否否否
CP/M filesystem否否是否是否
DECtape否否否否否否
DOS (GEC)否是是否否否
ext2否[141]否否否是否[142]
ext3否[141]否否否是否
ext3cow否[141]否否否是否
ext4否[141]否是是是否
exFAT未知否否未知否否
FAT12否否否否否否[143]
FAT16否否否否否否[143]
FAT32否否否否否否
FFS8:1[144]否否否是否
Fossil否否否否否是[99]
GFS部份[145]否否否是否
GPFS是是否否是否
HFS Plus否否是是否是
HPFS否否是否否否
JFS是否是否是only in JFS1 on AIX[146]
Level-D是否是否否否
LFS8:1[144]否否否是否
Lustre否否是是是否
NSS否否是否未知是
NILFS否否Planned是是否
NTFS部份否是否是部份[147]
NWFS是[148]否否否未知是
OCFS否否是否未知否
OCFS2否否是否是否
ODS-5否否是否未知否
OS4000否是是否否否
PramFS否否否否是否
QFS是否否否未知否
ReiserFS是否否否是否
Reiser4是否是[149]是是是[127]
Reliance否否否否否否
Reliance Nitro否否是否是否
UDF否否是依情況[150]否否
UFS18:1[144]否否否是否
UFS28:1[144]是否否是否
V6FS否否否否是否
V7FS否否否否是否
VMFS2是否否否是否
VMFS3是否是否是否
VxFS未知否是否是否
XFS否否是是是否
ZFS部份[151]是否是是是
File systemBlock suballocationVariable file block size[138]ExtentsAllocate-on-flushSparse filesTransparent compression

支持的操作系统编辑

文件系统DOSWindows 9xWindows NTLinuxMac OSMac OS XFreeBSDBeOSSolarisAIXz/OSOS/2Windows CEWindows MobileVxWorksHP-UXPlan 9
BFS否部份 - 需使用第三方驅動程式，只讀部份 - 需使用第三方驅動程式，只讀部份 - 只讀否未知否是未知未知未知未知否否未知未知否
Btrfs否否With WinBtrfs是: 內核版本 2.6.29 至 3.9 不穩定; 內核版本 3.10 後穩定否否否否否否否否否否未知未知否
DECtape否未知未知with AncientFS[152]否with AncientFS[152]with AncientFS[152]未知未知未知未知未知否否未知未知否
exFAT否部份 需使用第三方驅動程式，只讀是 : Win7, Vista SP1, can be added to XP SP2, SP3是 since kernel 5.4否部份 10.6.5+, 限制簇大小為 1024 位元組否否是否否否是否未知未知未知
ext2未知未知with Ext2Fsd (complete)[153] or Ext2 IFS (partial, no large inodes)[154] or Ext2Read (read-only, also on LVM2)[155]是 since kernel 0.99否with ExtFS,[156] fuse-ext2,[157] and ext2fsx[158]是只讀未知未知未知third-party app[159]with 3rd-party app[160]with 3rd-party app[160]未知未知是
ext3未知未知with Ext2Fsd (complete)[153] or Ext2 IFS (partial, no large inodes)[154] or Ext2Read (read-only, also on LVM2)[155]是 since kernel 2.4.15否with ExtFS[156] and fuse-ext2[157]部份 read-only[161]未知是未知未知未知with 3rd-party app[160]with 3rd-party app[160]未知未知否
ext3cow未知未知未知是 Kernel 2.6.20未知未知未知未知未知未知未知未知未知未知未知未知否
ext4否否部份 with Ext2Fsd (partial, extents limited)[153] or Ext2Read (read-only, also on LVM2)[155]是 since kernel 2.6.28否with ExtFS (full read/write), [156] fuse-ext2 (partial),[157] and ext4fuse (read-only)[162]部份 support in kernel since version 10.1 (read-only)[161] or with ext4fuse (read-only)[162]未知未知未知未知未知否未知未知未知否
FAT12是是是是是是是是否部份 on diskettes only, through dos* commands未知是是[163]未知是[164]未知是
FAT16是 since DOS 3.0, FAT16B since DOS 3.31是是是是是是是是部份 on diskettes only, through dos* commands未知是是[163]是是[164]未知是
FAT32是 since DOS 7.1[165]是 since Windows 95 OSR2是 since Windows 2000是是是是是是部份 on diskettes only, through dos* commands未知with third-party app[166]是[163]是是[164]未知是
FFS否未知未知是[167]否是是未知未知未知未知未知未知未知未知未知未知
Fossil否否否with 3rd-party software[168]否with 3rd-party software[168]with 3rd-party software[168]否with 3rd-party software[168]否否否否否否否是
GFS否未知未知是 since kernel 2.6.19否未知否未知未知未知未知未知否否未知未知否
HFS否with third-party app[169]with third-party app[169][170]是是部份: read-only since OSX 10.6[171]with third-party app[172][173]未知未知未知否with third-party app[174]否否否未知否
HFS Plus否with third-party app[169]with third-party app[169][170]部份 - write support occurs if journal is empty, but requires a force mount.是 since Mac OS 8.1是部份 read-only third-party app[175]未知未知未知否with third-party app否否否未知否
HPFSwith third-party driver部份 read-only third-party driver[176]included until v3.51, third-party driver until 4.0[177]是否未知是未知未知未知未知是否未知未知未知否
IBM Spectrum Scale[178]否否是是 since 2001否否否否否是否否否否否否否
IBM HFS否否否否否否否否否否是否未知未知未知未知否
IBM zFS否否否否否否否否否否是否未知未知未知未知否
JFS否未知未知是否否否未知未知是未知是否否未知否否
Level-D否未知未知未知否未知否未知未知未知未知未知未知未知未知未知否
LFS否未知未知with logfs[179] and others否未知否未知未知未知未知未知否否未知未知未知
LTFS否未知未知是否是否否否否否否否否未知未知否
Lustre否否部份 - under development[180]是[181]否部份 - via FUSE部份 - via FUSE否部份 - under development[182]否否否否否未知未知否
NILFS否未知未知是 since kernel 2.6.30否未知否未知未知未知未知未知否否未知未知否
NSS未知未知未知with Novell OES2[來源請求]否未知否未知未知未知未知未知否否未知未知否
NTFSwith third-party driverwith third-party driver[183]是是 Kernel 2.2 or newer, or with NTFS-3G or ntfsprogswith NTFS-3G or MacFUSEwith NTFS-3G or partial read-only in kernelwith NTFS-3Gread-onlywith NTFS-3G on Opensolaris未知未知部份 read-only third-party driver[184]with 3rd-party driver[185]否未知未知未知
NWFS未知未知未知via ncpfs client software[186]否未知是未知未知未知未知未知否否未知未知否
OCFS否未知未知是否未知否未知未知未知未知未知否否未知未知否
OCFS2否未知未知是否未知否未知未知未知未知未知否否未知未知否
ODS-2否未知未知部份 read-only with tool or kernel module[187]否未知否未知未知未知未知未知未知未知未知未知否
ODS-5否未知未知部份 read-only with kernel module[187]否未知否未知未知未知未知未知未知未知未知未知否
PramFS否否否是否否否否否否否否否否否否否
QFS否未知未知via client software[188]否未知否未知是未知未知未知否否未知未知否
ReFS否否是 since Windows Server 2012 and Windows 8.1未知未知未知未知未知未知未知未知未知未知未知未知未知未知
Reiser4否未知部份 with DiskInternals Linux Reader[170] (read-only)with a kernel patch否否否未知未知未知未知未知未知未知未知未知否
ReiserFS否未知部份 with DiskInternals Linux Reader[170] (read-only)是 since kernel 2.4.1否否部份 - read only部份 - read only未知未知未知未知with 3rd-party app[160]with 3rd-party app[160]未知未知否
Reliance否否否否否否否否否否否否是否是未知否
Reliance Nitro否否否是否否否否否否否否是是是未知否
RT-11否未知未知未知否未知否未知未知未知未知未知否否是未知否
UDF未知部份 read-only support of UDF 1.02 since Win95 OSR2是[189]是是 since Mac OS 9是是部份是未知未知未知是未知未知未知否
UFS1否未知未知部份 - read only否是是未知未知未知未知未知未知未知否未知未知
UFS2否未知部份 - with DiskInternals Linux Reader[170] (read-only)部份 - read only否否是未知未知未知未知未知未知未知否未知未知
VMFS2未知未知未知未知否未知否未知未知未知未知未知未知未知未知否否
VMFS3否未知未知部份 read-only with vmfs[190]未知未知否未知未知未知未知未知未知未知未知未知否
VxFS否未知未知是否未知否未知是是未知未知否否未知是否
XFS否未知未知是 since kernel 2.4否未知部份: read-only未知未知未知未知未知否否未知未知否
ZFS否否否with 3rd Party kernel module[191] or FUSE[192]否with free 3rd-party software[193]是否是否否否未知未知未知未知否
File systemDOSWindows 9xWindows NTLinuxMac OSMac OS XFreeBSDBeOSSolarisAIXz/OSOS/2Windows CEWindows MobileVxWorksHP-UXPlan 9

参见编辑

注释编辑

  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. ^ through OEM agreement
  3. ^ Polycenter File System — HELP, Tru64 Unix managers, ORNL, （原始内容存档于2012年3月9日） 
  4. ^ 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.
  5. ^ 5.0 5.1 Specifications for the Reliance file systems are available here [1][失效連結].
  6. ^ 6.0 6.1 These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; and particular and operating systems may also place restrictions of their own, across all filesystems. MS-DOS, Microsoft Windows, and OS/2 disallow the characters \ / : ? * " > < | and NUL in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
  7. ^ 7.0 7.1 7.2 7.3 7.4 7.5 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).
  8. ^ While the on-disk filesystem structure uses a 4-byte file length, which allows files up to 4G, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum file size to 512M.
  9. ^ While the on-disk filesystem structure uses a 3-byte sector number, which allows access to 4G of disk space, the usual disk access APIs use the top three bits of the sector number to specify the drive number, effectively limiting the maximum disk size to 512M.
  10. ^ 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 10.11 10.12 10.13 10.14 10.15 10.16 10.17 10.18 10.19 10.20 10.21 10.22 10.23 10.24 10.25 10.26 10.27 10.28 10.29 10.30 10.31 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. ^ 11.00 11.01 11.02 11.03 11.04 11.05 11.06 11.07 11.08 11.09 11.10 11.11 11.12 11.13 11.14 11.15 11.16 11.17 11.18 11.19 11.20 11.21 11.22 11.23 11.24 11.25 11.26 11.27 11.28 11.29 11.30 11.31 11.32 11.33 11.34 11.35 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/PC DOS do not support full pathnames longer than 66 bytes for FAT12, FAT16 and FAT32 volumes. This limit exists because these operating systems were designed around a fixed-length internal data structure named Current Directory Structure, which holds the absolute paths of the current working directories of all volumes.The FAT12/FAT16 file system implementation under Concurrent DOS and DR DOS 3.31 to 6.0 (prior to 1992 updates) did not impose any such limits on the directory depth due to their internal representation of current working directories as dynamically updated chain of double-linked relative directories. The introduction of a DOS-like CDS (instead of only an emulation thereof) for compatibility purposes with BDOS 7.0 in 1992 imposed the same length limits on PalmDOS, DR DOS 6.0 (since 1992 update), Novell DOS, OpenDOS, etc. as known from MS-DOS/PC DOS.Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Most Windows programs will fail when full path exceeds 255 characters (including Explorer and CMD.EXE). Linux has a pathname limit of 4,096.
  12. ^ ProDOS 8 Technical Reference Manual. [31 May 2013]. （原始内容存档于2021-02-11）. 
  13. ^ Beneath Apple ProDOS (PDF). Quality Software. 1985: 2–8 [2015-05-31]. ISBN 0-912985-05-4. （原始内容存档 (PDF)于2020-12-03）. 
  14. ^ Varies wildly according to block size and fragmentation of block allocation groups.
  15. ^ The CP/M filesystem itself does have limitations in regard to the allowed filename characters to be used, but officially the following characters are not allowed: SPACE < > . , ; : = ? * [ ] % | ( ) / \. CCP reserves the following characters for special purposes: SPACE , = _ . : ;, PIP additionally reserves: < > [ ].
  16. ^ 16.0 16.1 Maximum CP/M-80 2.2 volume size?, comp.os.cpm, Google Groups, [2009-10-09] [失效連結]
  17. ^ Table "Limits" states a maximum of 255 Unicode characters for the filename [2] （页面存档备份，存于互联网档案馆）
  18. ^ KB955704. 2009-01-27 [2015-05-31]. （原始内容存档于2011-05-24）. Description of the exFAT file system driver update package [for 32-bit XP] 
  19. ^ Interviews/EricSandeen. FedoraProject. 2008-06-09 [2009-10-09]. （原始内容存档于2018-12-15）. 
  20. ^ ext4 1.42 （页面存档备份，存于互联网档案馆） "This release of e2fsprogs has support for file systems > 16 TB"
  21. ^ msdn TexFAT File Naming Limitations. 2009-10-14 [2015-05-31]. （原始内容存档于2016-05-10）. 
  22. ^ 22.0 22.1 22.2 22.3 22.4 22.5 22.6 Depends on whether the FAT12, FAT16 or 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). Short names also do not normally contain lowercase letters. Also note that a few special device names should be avoided, as some operating systems (notably DOS and Windows) effectively reserve them.
  23. ^ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GB. This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid. [3] （页面存档备份，存于互联网档案馆）
  24. ^ 24.0 24.1 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.
  25. ^ 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 /.
  26. ^ 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.
  27. ^ 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.
  28. ^ Docs, Apple, [2015-05-31], （原始内容存档于2008-03-17） 
  29. ^ Docs, [2015-05-31], （原始内容存档于2012-06-05） 
  30. ^ 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.
  31. ^ 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.
  32. ^ ISO 9660#Restrictions
  33. ^ 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/4 GB file size limit
  34. ^ 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.
  35. ^ Joliet Specification 互联网档案馆的存檔，存档日期2009-04-14.
  36. ^ https://raw.github.com/danrl/lanyfs-docs/master/lanyfs-1.4.txt
  37. ^ LEAN file system. Freedos-32.sourceforge.net. [2013-02-05]. （原始内容存档于2021-03-02）. 
  38. ^ 38.0 38.1 38.2 38.3 38.4 File, file system, and memory size limits in Minix. Minix1.woodhull.com. [2013-02-05]. （原始内容存档于2020-02-12）. 
  39. ^ 39.0 39.1 NSS allows files to have multiple names, in separate namespaces.
  40. ^ 40.0 40.1 NTFS allows files to have multiple names, in separate namespaces: Win32, DOS, Win32&DOS, and Posix. Windows APIs create files with Win32 "long" names (1–255 characters), sometimes with an additional "short"/"alias" DOS name in the "8.3" format (12 characters).
  41. ^ 41.0 41.1 Richard Russon and Yuval Fledel. NTFS Documentation (PDF). [2011-06-26]. （原始内容存档 (PDF)于2020-07-04）. 
  42. ^ 42.0 42.1 Naming Files, Paths, and Namespaces (MSDN Library article). [2015-05-31]. （原始内容存档于2018-06-01）.  NB: This article includes discussion of the NT & Win32 namespaces used by Windows APIs; these are distinct from the NTFS filename namespaces.
  43. ^ In the Win32 namespace, any UTF-16 code unit (case insensitive) except NUL and \ / : * ? " < > | is allowed; in the Posix namespace, any UTF-16 code unit (case sensitive) except NUL and / is allowed; in the DOS namespace, any character in the U+0021–U+007E range except \ / : * ? " < > | is allowed. Windows APIs require Win32 namespace compatibility, which prevents access to folders & files having only Posix names containing Win32-incompatible characters.
  44. ^ 44.0 44.1 This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TB and the file size to 16 TB respectively.How NTFS Works. [2015-05-31]. （原始内容存档于2017-07-07）. 
  45. ^ 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.
  46. ^ Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  47. ^ Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  48. ^ 48.0 48.1 QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.
  49. ^ MSDN Blogs - Resilient File System, Windows 8 RC's filename length reduced (from 32K to 255) with Windows 8 RTM for NTFS compatibility. Blogs.msdn.com. 2012-01-16 [2013-02-05]. （原始内容存档于2013-05-15）. 
  50. ^ ReiserFS has a theoretical maximum file size of 1 EB, but "page cache limits this to 8TB on architectures with 32 bit int"[4] （页面存档备份，存于互联网档案馆）
  51. ^ SFS file system. Publib.boulder.ibm.com. [2013-02-05]. [永久失效連結]
  52. ^ This restriction might be lifted in newer versions.
  53. ^ 232 × block size
  54. ^ Wenguang's Introduction to Universal Disk Format (UDF). Google Sites. Section 5.1 Highlight of the UDF Format. 1 February 2009 [17 July 2014]. （原始内容存档于2021-03-08）. 
  55. ^ See manual 存档副本. [2015-05-31]. （原始内容存档于2016-03-07）. 
  56. ^ See manual 存档副本. [2015-05-31]. （原始内容存档于2016-03-04）. 
  57. ^ See "dir (5)" in Volume 1 of the manual 存档副本. [2004-08-26]. （原始内容存档于2004-08-26）. 
  58. ^ 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.
  59. ^ 59.0 59.1 Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.
  60. ^ Note that the filename can be much longer XFS#Extended attributes
  61. ^ 61.0 61.1 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.
  62. ^ Implemented in later versions as an extension
  63. ^ 63.00 63.01 63.02 63.03 63.04 63.05 63.06 63.07 63.08 63.09 63.10 63.11 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.
  64. ^ ext4 has group descriptor, journal and, starting from Linux kernel 3.5, metadata checksumming
  65. ^ 65.0 65.1 Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store file owner information in reserved fields of directory entries on FAT12 and FAT16 volumes, if the optional multi-user security module is loaded. If loaded, most external commands invoke support for special /U:owner/group command line options to deal with this extra information.
  66. ^ 66.0 66.1 Concurrent DOS, FlexOS, Multiuser DOS, REAL/32, DR DOS, PalmDOS, Novell DOS, OpenDOS, and DR-DOS can store read/write/delete/execute access permissions and file/directory passwords in reserved fields of directory entries on FAT12 and FAT16 volumes. This is an integral part of the design, therefore passwords can be appended to file or directory names with semicolon (for example: dirname;dirpwd\filename;filepwd), the PASSWORD command can be used to control permissions and some commands support a special /P:pwd option to deal with this feature.
  67. ^ 67.0 67.1 67.2 67.3 67.4 67.5 File creation and file access timestamps are supported only by DOS 7.0 and higher, and typically only when explicitly enabled.
  68. ^ 68.0 68.1 68.2 Some FAT implementations, such as in Linux, show file modification timestamp (mtime) in the metadata change timestamp (ctime) field. This timestamp is however, not updated on file metadata change.
  69. ^ 69.0 69.1 Particular Installable File System drivers and operating systems may not support extended attributes on FAT12 and FAT16. The OS/2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes (using a "EA DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.
  70. ^ File permission in 9P are a variation of the traditional Unix permissions with some minor changes, e.g. the suid bit is replaced by a new 'exclusive access' bit.
  71. ^ As of 10.5 Leopard, Mac OS X has support for Mandatory Labels. See. Trustedbsd.org. [2013-02-05]. （原始内容存档于2010-01-23）. 
  72. ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  73. ^ 73.0 73.1 Time the file was recorded on the volume always available; "File Creation Date and Time" available only if the file has an Extended Attribute block.
  74. ^ 74.0 74.1 Not applicable to file systems on a read-only medium.
  75. ^ 75.0 75.1 Available only if the file has an Extended Attribute block.
  76. ^ Creation time is stored in the backing ext4 filesystem, but is not yet sent to clients.
  77. ^ Lustre has checksums for data over the network, but depends on backing filesystem and hardware for checksums of persistent data
  78. ^ 78.0 78.1 78.2 78.3 78.4 Not available with ext3/4, but will be available with ZFS OST/MDT backing filesystems.
  79. ^ 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.
  80. ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control. See [5] （页面存档备份，存于互联网档案馆）
  81. ^ 81.0 81.1 81.2 81.3 81.4 81.5 The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
  82. ^ 82.0 82.1 Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.
  83. ^ 83.0 83.1 Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.
  84. ^ 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.
  85. ^ Record Management Services (RMS) attributes include record type and size, among many others.
  86. ^ 86.0 86.1 CRCs are employed for certain types of metadata.
  87. ^ 87.0 87.1 87.2 87.3 Access-control lists and MAC labels are layered on top of extended attributes.
  88. ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  89. ^ 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.
  90. ^ 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
  91. ^ McPherson, Amanda, A Conversation with Chris Mason on BTRfs: the next generation file system for Linux, Linux Foundation, 2009-06-22 [2009-09-01], （原始内容存档于2012-06-24） 
  92. ^ Wiki, BTRFS, Deduplication, [2015-05-31], （原始内容存档于2021-03-13） 
  93. ^ Linux kernel versions 2.6.12 and newer.
  94. ^ 94.0 94.1 94.2 Offline growing/shrinking as well as online growing: Linux man page for resize2fs(8) (from e2fsprogs 1.41.9). [2015-05-31]. （原始内容存档于2023-03-25）. 
  95. ^ 95.0 95.1 95.2 95.3 Off by default.
  96. ^ 96.0 96.1 96.2 6, Parted manual, GNU, [2015-05-31], （原始内容存档于2020-02-25） 
  97. ^ "Write Ahead Physical Block Logging" in NetBSD, provides metadata journaling and consistency as an alternative to softdep.
  98. ^ OpenBSD growfs(8) manpage. Openbsd.org. 2008-11-28 [2013-02-05]. 
  99. ^ 99.0 99.1 99.2 99.3 When used with venti.
  100. ^ 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
  101. ^ Optional journaling of data
  102. ^ 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.
  103. ^ Hard Links on HFS. Developer.apple.com. [2013-02-05]. （原始内容存档于2009-07-01）. 
  104. ^ 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.
  105. ^ 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 互联网档案馆的存檔，存档日期2008-10-06. (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).
  106. ^ 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 （页面存档备份，存于互联网档案馆）.
  107. ^ As of OS X 10.7, HFS+ supports full volume file encryption known as Filevault 2.
  108. ^ Since Mac OS X Snow Leopard, online resizing is supported.How to resize a live partition in Snow Leopard and Lion. [2015-05-31]. （原始内容存档于2013-09-22）. 
  109. ^ 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.
  110. ^ 存档副本. [2015-05-31]. （原始内容存档于2010-02-02）. 
  111. ^ 111.0 111.1 111.2 111.3 UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  112. ^ 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
  113. ^ 113.0 113.1 113.2 113.3 Case-sensitivity/Preservation depends on client. Windows, DOS, and OS/2 clients don't see/keep case differences, whereas clients accessing via NFS or AFP may.
  114. ^ 114.0 114.1 The file change logs, last entry change timestamps, and other filesystem metadata, are all part of the extensive suite of auditing capabilities built into NDS/eDirectory called NSure Audit. (Filesystem Events tracked by NSure （页面存档备份，存于互联网档案馆）)
  115. ^ 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.
  116. ^ 116.0 116.1 NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  117. ^ 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.
  118. ^ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
  119. ^ Rick Vanover. Windows Server 8 data deduplication. [2011-12-02]. （原始内容存档于2012-07-04）. 
  120. ^ How to Shrink and Extend NTFS Volumes in Windows. Bleepingcomputer.com. [2013-02-05]. （原始内容存档于2011-09-03）. 
  121. ^ 121.0 121.1 Available only in the "NFS" namespace.
  122. ^ Limited capability. Volumes can span physical disks (volume segment)
  123. ^ OCFS2 supports creating multiple write-able snapshots of regular files using REFLINK.
  124. ^ 124.0 124.1 These are referred to as "aliases".
  125. ^ Symlinks only visible to NFS clients. References and Off-Disk Pointers (ODPs) provide local equivalent.
  126. ^ Full block journaling for ReiserFS was not added to Linux 2.6.8 for obvious reasons.[為何？]
  127. ^ 127.0 127.1 Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  128. ^ 128.0 128.1 File system implements reliability via atomic transactions.
  129. ^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling).
  130. ^ Block level journals can be added by using gjournal module in FreeBSD.
  131. ^ 存档副本. [2015-05-31]. （原始内容存档于2017-05-30）. 
  132. ^ FreeBSD growfs(8) manpage. Freebsd.org. 2012-04-30 [2013-02-05]. （原始内容存档于2016-03-04）. 
  133. ^ 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.
  134. ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  135. ^ Optionally no on IRIX and Linux.
  136. ^ 136.0 136.1 ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.
  137. ^ How to resize ZFS. [2015-05-31]. （原始内容存档于2020-02-16）. 
  138. ^ 138.0 138.1 Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.
  139. ^ Btrfs can only inline files smaller than 3916B with its metadataMailing list discussion. [2015-05-31]. （原始内容存档于2015-06-27）. 
  140. ^ only for .REL (record structured) files, up to 254 bytes/record
  141. ^ 141.0 141.1 141.2 141.3 Fragments were planned, but never actually implemented on ext2 and ext3.
  142. ^ 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.
  143. ^ 143.0 143.1 SuperStor in DR DOS 6.0 and PC DOS 6.1, DoubleSpace in MS-DOS 6.0, DriveSpace in MS-DOS 6.22, Windows 95 and Windows 98, and Stacker in Novell DOS 7, OpenDOS 7.01, DR-DOS 7.02/7.03 and PC DOS 7.0/2000 were data compression schemes for FAT.
  144. ^ 144.0 144.1 144.2 144.3 Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  145. ^ Only for "stuffed" inodes
  146. ^ AIX documentation: JFS data compression. IBM. [2015-05-31]. （原始内容存档于2020-04-18）. 
  147. ^ Only if formatted with 4kB-sized clusters or smaller
  148. ^ 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.
  149. ^ In "extents" mode.
  150. ^ Depends on UDF implementation.
  151. ^ When enabled, ZFS's logical-block based compression behaves much like tail-packing for the last block of a file.
  152. ^ 152.0 152.1 152.2 AncientFS. [2015-05-31]. （原始内容存档于2015-02-02）. 
  153. ^ 153.0 153.1 153.2 Ext2Fsd is an open source ext2/ext3/ext4 kernel-level file system driver for Windows systems (NT/2K/XP/VISTA/7, X86/AMD64) that provides both read/write access to the file system. Currently, does not fully support extents (no size truncating/extending, no file deletion), a default feature of ext4. [6] （页面存档备份，存于互联网档案馆）
  154. ^ 154.0 154.1 Ext2 IFS for Windows provides kernel-level read/write access to ext2 and ext3 volumes in Windows NT4, 2000, XP, Vista and Windows 2008. Does not support inodes size above 128 bytes and does not support ext4.[7] （页面存档备份，存于互联网档案馆）
  155. ^ 155.0 155.1 155.2 Ext2Read is an explorer-like utility to explore ext2/ext3/ext4 file systems that provides read-only access to the file system. It supports extents, large inodes, and LVM2 volumes.Ext2Read （页面存档备份，存于互联网档案馆）
  156. ^ 156.0 156.1 156.2 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.[8] （页面存档备份，存于互联网档案馆）
  157. ^ 157.0 157.1 157.2 Fuse-ext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices and/or images with read and write support.[9][失效連結]
  158. ^ Ext2fsx is the first and old implementation of the Ext2 (Linux) filesystem for Mac OS X.[10] （页面存档备份，存于互联网档案馆）
  159. ^ OS/2 ext2 Driver. [2020-01-31]. （原始内容存档于2016-03-04）. 
  160. ^ 160.0 160.1 160.2 160.3 160.4 160.5 See Total Commander, which supports accessing ext2, ext3, and ReiserFS from Windows, Windows CE, and Windows Mobile.
  161. ^ 161.0 161.1 存档副本. [2015-05-31]. （原始内容存档于2019-01-18）. 
  162. ^ 162.0 162.1 ext4fuse is a free software multi OS FUSE module to mount ext4 file system devices and/or images with read-only support. [11] （页面存档备份，存于互联网档案馆）
  163. ^ 163.0 163.1 163.2 Files, Databases, and Persistent Storage （页面存档备份，存于互联网档案馆）. MSDN.
  164. ^ 164.0 164.1 164.2 Via dosFs.
  165. ^ Native FAT32 support with MS-DOS 7.10 and 8.0. Loadable FAT32 support for any DOS since 3.31 with DRFAT32 redirector driver. Native FAT32 support since OEM DR-DOS 7.04, bootable FAT32 support since OEM DR-DOS 7.06. Native FAT32 support with OEM PC DOS 7.10.
  166. ^ OS/2 and eComstation FAT32 Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）. 
  167. ^ How to mount FFS partition under Linux - NetBSD Wiki. Wiki.netbsd.se. [2009-10-09]. （原始内容存档于2008年3月19日）. 
  168. ^ 168.0 168.1 168.2 168.3 Via Plan 9 from User Space; initial checkin fossil: import from plan 9. [2013-11-24]. （原始内容存档于2013-12-03）. 
  169. ^ 169.0 169.1 169.2 169.3 Cross-platform Drive Solutions. Sharing Disks - Windows Products. Macwindows.com. [2013-02-05]. （原始内容存档于2011-06-20）. 
  170. ^ 170.0 170.1 170.2 170.3 170.4 DiskInternals Linux Reader （页面存档备份，存于互联网档案馆） is an application for Windows NT that allows reading of Ext2/3/4, ReiserFS, Reiser4, HFS/HFS+, FAT/exFAT, NTFS, ReFS, and UFS2 filesystems.
  171. ^ Gagne, Ken. Losing legacy data to Snow Leopard. Computerworld. 2009-08-31 [2009-09-07]. （原始内容存档于2009-09-03）. 
  172. ^ hfsutils at FreshPorts. Freshports.org. [2013-02-05]. （原始内容存档于2018-02-18）. 
  173. ^ hfs at FreshPorts. Freshports.org. [2013-02-05]. （原始内容存档于2019-01-18）. 
  174. ^ OS/2 HFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）. 
  175. ^ Catacombae HFSExplorer. Hem.bredband.net. [2013-02-05]. （原始内容存档于2013-02-02）. 
  176. ^ DOS/Win 9x HPFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-03-04）. 
  177. ^ Win NT 4.0 HPFS Driver. [2020-01-31]. （原始内容存档于2016-03-04）. 
  178. ^ IBM GPFS Product Page. [2015-05-31]. （原始内容存档于2014-04-30）. 
  179. ^ logfs. [2015-05-31]. （原始内容存档于2021-03-22）. 
  180. ^ 存档副本. [2015-05-31]. （原始内容存档于2011-03-14）. 
  181. ^ 存档副本. [2015-05-31]. （原始内容存档于2018-12-15）. 
  182. ^ 存档副本. [2015-05-31]. （原始内容存档于2011-07-27）. 
  183. ^ NTFS for Windows 98. Download.chip.eu. [2013-02-05]. （原始内容存档于2016-03-04）. 
  184. ^ OS/2 NTFS Driver. Hobbes.nmsu.edu. [2013-02-05]. （原始内容存档于2016-08-07）. 
  185. ^ Tuxera NTFS for Windows CE. See article. [2015-05-31]. （原始内容存档于2012-09-18）.  and announcement 互联网档案馆的存檔，存档日期2011-05-22..
  186. ^ ncpfs. [2015-05-31]. （原始内容存档于2008-05-15）. 
  187. ^ 187.0 187.1 VMS2Linux. [2015-05-31]. （原始内容存档于2021-01-18）. 
  188. ^ Using SAM-QFS on Linux Clients 互联网档案馆的存檔，存档日期2011-10-02.
  189. ^ Understanding the difference between the Live File System and Mastered disc formats. Which CD or DVD format should I use?. Microsoft. [2008-11-22]. （原始内容存档于2016-03-02）. 
  190. ^ vmfs. [2015-05-31]. （原始内容存档于2009-03-02）. 
  191. ^ Native ZFS for Linux. [2015-05-31]. （原始内容存档于2019-05-22）. 
  192. ^ ZFS on FUSE 互联网档案馆的存檔，存档日期2013-05-13.
  193. ^ Mac ZFS. [2015-05-31]. （原始内容存档于2014-02-11）. 

外部链接编辑

取自“https:https://www.duhocchina.com/baike/index.php?lang=zh&q=文件系统的对比&oldid=80226656”
🔥 Top keywords: Baike: 首页Special:搜索胖猫跳江事件背着善宰跑九龍城寨之圍城逆天奇案2璩静淚之女王歌手2024Energy (組合)新生 (网络剧)习近平匈牙利邊佑錫劉俊謙 (香港)金智媛神耆小子塞尔维亚金秀賢 (男演員)母亲节猩球崛起：王國誕生九龍寨城馴鹿寶貝家族榮耀之繼承者Seventeen (組合)六四事件不夠善良的我們张维为楊佩潔TripleS支配物种庆余年郭葦昀洪若潭命案金惠奫2024年英雄联盟季中邀请赛春色寄情人BABYMONSTER笑看風雲乘風2024排球少年！！角色列表破墓徐巧芯中华人民共和国中華民國打天下2WIND BREAKER—防風少年—习明泽排球少年！！彭丽媛磁暴ILLIT贾斯汀·比伯逆天奇案BOYNEXTDOOR猿人爭霸戰：猩凶革命張書偉我的婆婆怎麼那麼可愛我獨自升級怪獸8號謝坤達IVE (組合)與鳳行關於我轉生變成史萊姆這檔事角色列表黃道十二宮福建號航空母艦虽然不是英雄葉乃文五月天張員瑛草榴社区張文傑2024年花蓮地震极光香緹·摩爾迷宮飯呂家愷搜查班長1958日本劉德華海莉·鮑德溫蕭景鴻越位 (足球)葬送的芙莉蓮周處除三害 (電影)毛泽东願榮光歸香港林峯周雨彤伍允龍羅毓儀香港Baike: 分類索引沒有秘密猩球崛起：終極決戰角質層唐振剛柯佳嬿文化大革命