下列表格對比了一系列檔案系統的一般和技術資料，檔案系統的具體資訊參見連結文章。 一般資料 檔案系統 開發者 釋出年份 原作業系統 許可 DECtape DEC 1964 PDP6 Monitor LevelD DEC 1968 TOPS10 George3 ICT 即之後的 ICL 1968 George 3 ODS1 DEC 1972 RSX11 RT11 file system DEC 1973 RT11 DOS GEC GEC 1973 Core Operating System CPM file system 蓋瑞基爾多 1974 CPM V6FS Bell Labs 1975 Version 6 Unix OS4000 GEC 1977 OS4000 FAT 8bit Marc McDonald Microsoft 1977 Microsoft Standalone Disk BASIC80 DOS 3x Apple Computer 1978 Apple DOS Pascal Apple Computer 1978 Apple Pascal CBM DOS Commodore 1978 Microsoft BASIC for CBM PET V7FS Bell Labs 1979 Version 7 Unix DOS 10 Atari Corporation 1979 Atari 8bit family ODS2 DEC 1979 OpenVMS FAT12 Tim Paterson Seattle Computer Products 1980 QDOS 86DOS DOMAIN file system Apollo Computer 1981 DomainOS Aegis Domain AFS Carnegie Mellon University 1982 Multiplatform MultoOS DFS Acorn Computers Ltd 1982 Acorn BBC Micro MOS ADFS Acorn Computers Ltd 1983 Acorn Electron later Arthur RISC OS FFS Kirk McKusick 1983 42BSD ProDOS Apple Computer 1983 ProDOS 8 MFS Apple Computer 1984 Mac OS FAT16 Microsoft IBM 1984 PC DOS 30MSDOS 30 Elektronika BK tape format NPO Scientific centre now Sitronics 1985 Vilnius Basic BK monitor program HFS Apple Computer 1985 Mac OS Amiga OFS Metacomco for Commodore 1985 Amiga OS High Sierra Ecma International 1985 MSDOS Mac OS NWFS Novell 1985 NetWare 286 FAT16B Compaq 1987 Compaq MSDOS 331 DR DOS 331 MINIX V1 FS Andrew S Tanenbaum 1987 MINIX 10 Amiga FFS Commodore 1988 Amiga OS 13 HPFS IBM Microsoft 1988 OS2 ISO 96601988 Ecma International Microsoft 1988 MSDOS Mac OS and AmigaOS JFS1 IBM 1990 AIXIBM introduced JFS with the initial release of AIX Version 31 in 1990 This file system now called JFS1 The new JFS ported from OS2 to AIX and Linux was first shipped in OS2 Warp Server for eBusiness in 1999 It was released as JFS2 on AIX 5L VxFS VERITAS now Symantec 1991 為 Unix System Laboratories、HPUXthrough OEM agreement 開發 ext Rémy Card 1992 Linux WAFL NetApp 1992 Data ONTAP MINIX V2 FS Andrew S Tanenbaum 1992 MINIX 16 and 20 AdvFS DEC 1993 Digital Unix NTFS Version 10 Microsoft Tom Miller Gary Kimura 1993 Windows NT 31 proprietary LFS Margo Seltzer 1993 Berkeley Sprite ext2 Rémy Card 1993 Linux Hurd UFS1 Kirk McKusick 1994 44BSD XFS SGI 1994 IRIX HFS Hierarchical File System IBM 1994 MVSESA now zOS Rock Ridge Young Minds Inc 1994 Linux Mac OS Amiga OS and FreeBSD Joliet CDFS Microsoft 1995 Microsoft Windows Linux Mac OS and FreeBSD PFS Michiel Pelt 1996 AmigaOS Romeo Adaptec 1996 Microsoft Windows UDF ISOECMAOSTA 1995 FAT32 Microsoft 1996 Windows 95bMicrosoft first introduced FAT32 in Windows 95 OSR2 OEM Service Release 2 and then later in Windows 98 NTbased Windows did not have any support for FAT32 up to Windows NT4 Windows 2000 was the first NTbased Windows OS that received the ability to work with it QFS LSC Inc Sun Microsystems 1996 Solaris IBM Spectrum Scale IBM 1998 AIX Linux Windows Be File System Be Inc D Giampaolo C Meurillon 1996 BeOS HFS Plus Apple Computer 1998 Mac OS 81 NSS Novell 1998 NetWare 5 PolyServe File System PSFS PolyServe 1998 Windows Linux ODS5 DEC 1998 OpenVMS 72 SFS John Hendrikx 1998 AmigaOS AROS MorphOS ext3 Stephen Tweedie 1999 Linux ISO 96601999 Ecma International Microsoft 1999 Microsoft Windows Linux Mac OS X FreeBSD and AmigaOS JFS IBM 1999 OS2 Warp Server for ebusiness GFS Sistina Red Hat 2000 Linux Melio FS Sanbolic 2001 Windows NTFS Version 31 Microsoft 2001 Windows XP proprietary ReiserFS Namesys 2001 Linux zFS IBM 2001 zOS backported to OS390 FATX Microsoft 2002 Xbox UFS2 Kirk McKusick 2002 FreeBSD 50 Lustre Cluster File Systems later Oracle Corporation 2002 Linux OCFS Oracle Corporation 2002 Linux VMFS2 VMware 2002 VMware ESX Server 20 ext3cow Zachary Peterson 2003 Linux Fossil Bell Labs 2003 Plan 9 from Bell Labs 4th Edition LPL Google File System Google 2003 Linux PramFS MontaVista 2003 Linux RelianceSpecifications for the Reliance file systems are available here Datalight 2003 Windows CE VxWorks custom ports VxCFS VERITAS now Symantec 2004 AIX HPUX Solaris Linux ZFS Sun Microsystems 2004 Solaris CDDL Reiser4 Namesys 2004 Linux NonVolatile 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 VMFS3 VMware 2005 VMware ESX Server 30 GFS2 Red Hat 2006 Linux ext4 Various 2006 Linux exFAT Microsoft 2006 2009 Windows CE 60 Windows XP SP3 Windows Vista SP1 proprietary TexFATTFAT Microsoft 2006 Windows CE 60 Btrfs Oracle Corporation 2007 Linux GPL Ceph Sage Weil Inktank Storage Red Hat 2007 2012 Linux WBFS kwiirk and Waninkoko Wii homebrew 2008 Nintendo WII HAMMER Matthew Dillon 2008 DragonFly BSD Tux3 Various 2008 Linux UBIFS Nokia with help of University of Szeged 2008 Linux Oracle ACFS Oracle Corporation 2009 Linux Red Hat Enterprise Linux 5 and Oracle Enterprise Linux 5 only Reliance Nitro Datalight 2009 Windows CE Windows Mobile VxWorks Linux custom ports proprietary LTFS IBM 2010 Linux Mac OS X planned Microsoft Windows LGPL IlesfayFS Ilesfay Technology Group 2011 Microsoft Windows planned Red Hat Enterprise Linux VMFS5 VMware 2011 VMware ESXi 50tux 3 stats ReFS Microsoft 2012 2013 Windows 2012 Server proprietary Lanyard Filesystem Dan Luedtke 2012 Linux F2FS Samsung 2012 Linux GPLv2 File system Creator Yearintroduced Original operating system License 限制 檔案系統 最大檔名稱長度 and NUL in file and directory names across all filesystems Unixlike systems disallow the characters and NUL in file and directory names across all filesystems 最大路徑名長度 最大檔案大小 最大卷大小 For filesystems that have variable allocation unit blockcluster 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 eg 512 bytes and 128 kB for FAT which is the cluster size range allowed by the ondisk data structures although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 kB Acorn ADFS 10 bytes Any ISO 88591 character except SPACE No limit defined or While the ondisk filesystem structure uses a 4byte 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 or While the ondisk filesystem structure uses a 3byte 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 AdvFS characters Any byte except NUL No limit defined Apple DOS 3x bytes Any byte except NUL no subdirectories 105 files per disk DOS 33 assuming standard 35 tracks DOS 31 32 Apple ProDOS bytes AZ az 09 and period B including slashes BFS bytes Any byte except NUL No limit defined Varies wildly according to block size and fragmentation of block allocation groups Btrfs bytes Any byte except NUL CBM DOS bytes Any byte except NUL Nonhierarchical CPM file system 83 The CPM 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 user areas no subdirectories to 512 MB DECtape 63 AZ 09 DTxNFILNAMEXT 15 577 640 578 640 DOS GEC bytes AZ 09 Nonhierarchical Elektronika BK tape format bytes Nonhierarchical approx per side for 90 min cassette limited only by tape length exFAT 255 charactersTable Limits states a maximum of 255 Unicode characters for the filename Any Unicode except NUL No limit defined 512 TB recommended ext2 bytes Any byte except NUL and No limit defined ext3 bytes Any byte except NUL and No limit defined ext3cow bytes Any byte except NUL and No limit defined ext4 bytes Any byte except NUL and No limit defined ext4 142 This release of e2fsprogs has support for file systems 16 TB TexFAT 247 characters Any Unicode except NUL No limit defined Tested F2FS bytes FAT12 83 255 UCS2 code units with VFAT LFNs Depends on whether the FAT12 FAT16 or FAT32 implementation has support for long filenames LFNs Where it does not as in OS2 MSDOS Windows 95 Windows 98 in DOSonly mode and the Linux msdos driver file names are limited to 83 format of 8bit characters space padded in both the basename and extension parts and may not contain NUL endofdirectory 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 lowcase az are stored as AZ With VFAT LFN any Unicode except NUL No limit defined with 4K sectors and 64 KB clusters FAT16 83 255 UCS2 code units with VFAT LFNs lowcase az are stored as AZ With VFAT LFN any Unicode except NUL No limit defined with LFS or 4 GB FAT32 83 255 UCS2 code units with VFAT LFNs lowcase az are stored as AZ With VFAT LFN any Unicode except NUL No limit defined with LFS While FAT32 partitions this large work fine once created some software wont 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 FATX bytes ASCII Unicode not permitted No limit defined FFS bytes Any byte except NUL No limit defined Fossil 65535 bytes of UTF8 characters Any Unicode except 031 No limit defined 8 EB GFS Any byte except NUL No limit defined Depends on kernel version and arch For 24 kernels the max is 2 TB For 32bit 26 kernels it is 16 TB For 64bit 26 kernels it is 8 EB IBM Spectrum Scale UTF8 codepoints Any byte except NUL and No limit defined 18 PB tested HAMMER HFS bytes Any byte except As Mac OS X is a Unixlike 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 Unlimited HFS Plus 255 UTF16 code unitsThe 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 Any valid UnicodeHFS 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 Unlimited High Sierra HPFS bytes Any byte except NULThe and directory entries in HPFS that are seen by applications programs are a partial fiction created by the Installable File System drivers The ondisk data structure for a directory does not contain entries by those names but instead contains a special start entry Whilst ondisk directory entries by those names are not physically prohibited they cannot be created in normal operation and a directory containing such entries is corrupt No limit defined This is the limit of the ondisk structures The HPFS Installable File System driver for OS2 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 ISO 96601988 Level 1 83Level 2 3 180 Depends on LevelISO 9660Restrictions 180 bytes Level 1 2 to 8 TB Level 3 Through the use of multiextents a file can consist of multiple segments each up to 4 GB in size See ISO 9660The 24 GB file size limit Assuming the typical 2048 Byte sector size The volume size is specified as a 32bit value identifying the number of sectors on the volume ISO 96601999 207 Joliet CDFS 64 Unicode characters All UCS2 code except and Joliet Specification same as ISO 96601988 same as ISO 96601988 Lanyard Filesystem bytes Any byte except NUL and No limit defined to httpsrawgithubcomdanrllanyfsdocsmasterlanyfs14txt LEAN bytes case sensitive in UTF8 any Unicode codepoint No limit defined LevelD 63 AZ 09 DEVICEFILNAMEXT PROJECTPROGRM 7 10 15 32 57 for SFDs 67 34359738368 words 2351 206158430208 SIXBIT bytes approx 64 178 MB LTFS Lustre bytes Any byte except NUL and No limit defined on ext4 55 PB tested JFS1 bytes Any byte except NUL No limit defined JFS bytes Any Unicode except NUL No limit defined MFS bytes Any byte except No path flat filesystem MicroDOS file system bytes MINIX V1 FS 14 or 30 bytes set at filesystem creation time Any byte except NUL No limit defined MINIX V2 FS 14 or 30 bytes set at filesystem creation time Any byte except NUL No limit defined then 2 TB MINIX V3 FS bytes Any byte except NUL No limit defined NILFS bytes Any byte except NUL No limit defined NSS characters Depends on namespace usedNSS allows files to have multiple names in separate namespaces Only limited by client NTFS 255 charactersNTFS allows files to have multiple names in separate namespaces Win32 DOS Win32DOS and Posix Windows APIs create files with Win32 long names 1255 characters sometimes with an additional shortalias DOS name in the 83 format 12 characters NB This article includes discussion of the NT Win32 namespaces used by Windows APIs these are distinct from the NTFS filename namespaces is allowed in the Posix namespace any UTF16 code unit case sensitive except NUL and is allowed in the DOS namespace any character in the U0021U007E range except is allowed Windows APIs require Win32 namespace compatibility which prevents access to folders files having only Posix names containing Win32incompatible characters 32767 Unicode characters with each path component directory or filename commonly up to 255 characters long This is the limit of the ondisk 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 NWFS bytesSome namespaces had lower name length limits LONG had an 80byte limit NWFS 80 bytes NFS 40 bytes and DOS imposed 83 filename Depends on namespace used No limit defined OCFS bytes Any byte except NUL No limit defined OCFS2 bytes Any byte except NUL No limit defined ODS5 bytesMaximum combined filenamefiletype length is 236 bytes each component has an individual maximum length of 255 bytes 4096 bytesMaximum pathname length is 4096 bytes but quoted limits on individual components add up to 1664 bytes OS4000 bytes AZ 09Period is directory separator No limit defined at least PramFS bytes Any byte except NUL QFS bytes Any byte except NUL No limit defined 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 ReFS 32767 Unicode characters 255 Unicode characters in Windows 881 32767 Unicode characters in each path component with 64 kB cluster size 264 64 210 Windows stack addressing allows 16 EB ReiserFS bytes226 characters Any byte except NUL No limit defined ReiserFS has a theoretical maximum file size of 1 EB but page cache limits this to 8TB on architectures with 32 bit int v36 2 GB v35 Reiser4 bytes Any byte except and NUL No limit defined on x86 Reliance bytes OS specific Reliance Nitro bytes OS specific 1024 bytes RT11 63 AZ 09 Nonhierarchical 65536 512 IBM SFS 88 Nonhierarchical UDF bytes Any Unicode except NUL 1023 bytesThis restriction might be lifted in newer versions hard disk 8 TB optical disc 232 block size UFS1 bytes Any byte except NUL No limit defined UFS2 bytes Any byte except NUL No limit defined V6FS bytesSee manual Any byte except NUL and 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 ondisk 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 No limit definedThe ondisk structures have no inherent limit Particular Installable File System drivers and operating systems may impose limits of their own however MSDOSPC 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 fixedlength internal data structure named Current Directory Structure which holds the absolute paths of the current working directories of all volumes The FAT12FAT16 file system implementation under Concurrent DOS and DR DOS 331 to 60 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 doublelinked relative directories The introduction of a DOSlike CDS instead of only an emulation thereof for compatibility purposes with BDOS 70 in 1992 imposed the same length limits on PalmDOS DR DOS 60 since 1992 update Novell DOS OpenDOS etc as known from MSDOSPC DOS Windows NT does not support full pathnames longer than 32767 bytes for NTFS Most Windows programs will fail when full path exceeds 255 characters including Explorer and CMDEXE Linux has a pathname limit of 4096 See manual V7FS bytesSee dir 5 in Volume 1 of the manual Any byte except NUL and No limit defined The actual maximum was 1082201088 bytes with 10 direct blocks 1 singly indirect block 1 doubly indirect block and 1 triply indirect block The 40BSD and 41BSD versions and the System V version used 1024byte blocks rather than 512byte blocks making the maximum 4311812608 bytes or approximately 4 GB VxFS bytes Any byte except NUL No limit defined VMFS2 Any byte except NUL and 2048 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 VMFS3 Any byte except NUL and 2048 XFS bytesNote that the filename can be much longer XFSExtended attributes Any byte except NUL No limit defined XFS has a limitation under Linux 24 of 64 TB file size but Linux 24 only supports a maximum block size of 2 TB This limitation is not present under IRIX ZFS bytes Any Unicode except NUL No limit defined File system Maximum filename length Allowable characters in directory entries Maximum pathname length Maximum file size Maximum volume size 元資料 檔案系統 儲存檔案所有者 POSIX 檔案許可權 建立時間戳 上次訪問 讀取時間戳 上次修改時間戳 Disk copy created 上次元資料更改時間戳 上次存檔時間戳 訪問控制表 安全 MAC 標籤 Extended attributes Alternate data streamsforks 元資料校驗和 ECC 最大時間戳解析度 AdvFS Be File System Btrfs 1 nanosecond CBM DOS CPM file system Implemented in later versions as an extension DECtape DOS GEC Elektronika BK tape format ext2 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 26x may either be missing support for these altogether or require a patch 1 second ext3 1 second ext3cow 1 second ext4 ext4 has group descriptor journal and starting from Linux kernel 35 metadata checksumming 1 nanosecond exFAT 10 milliseconds FAT12 Concurrent DOS FlexOS Multiuser DOS REAL32 PalmDOS Novell DOS OpenDOS and DRDOS can store file owner information in reserved fields of directory entries on FAT12 and FAT16 volumes if the optional multiuser security module is loaded If loaded most external commands invoke support for special Uownergroup command line options to deal with this extra information Concurrent DOS FlexOS Multiuser DOS REAL32 DR DOS PalmDOS Novell DOS OpenDOS and DRDOS can store readwritedeleteexecute access permissions and filedirectory 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 dirnamedirpwdfilenamefilepwd the PASSWORD command can be used to control permissions and some commands support a special Ppwd option to deal with this feature File creation and file access timestamps are supported only by DOS 70 and higher and typically only when explicitly enabled 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 Particular Installable File System drivers and operating systems may not support extended attributes on FAT12 and FAT16 The OS2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes using a EA DATA SF pseudofile to reserve the clusters allocated to them Other filesystem drivers for other operating systems do not 10 milliseconds FAT16 10 milliseconds FAT32 10 milliseconds FFS Fossil 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 1 second GPFS 1 nanosecond GFS HFS HFS Plus 1 second HPFS The fnode contains a field for a user identifier This is not used except by OS2 Warp Server however High Sierra ISO 96601988 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 Not applicable to file systems on a readonly medium Available only if the file has an Extended Attribute block ISO 96601999 JFS 1 second Joliet CDFS Lanyard Filesystem 1 nanosecond LevelD LFS Lustre Creation time is stored in the backing ext4 filesystem but is not yet sent to clients Lustre has checksums for data over the network but depends on backing filesystem and hardware for checksums of persistent data NILFS Planned Planned NTFS NTFS access control lists can express any access policy possible using simple POSIX file permissions and far more but use of a POSIXlike interface is not supported without an addon such as Services for UNIX or Cygwin As of Vista NTFS has support for Mandatory Labels which are used to enforce Mandatory Integrity Control See 100 nanoseconds NSS The local time timezoneUTC offset and date are derived from the time settings of the referencesingle timesync source in the NDS tree 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 bothSome file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not like datetime of creation file size purge status etc and some file and directory metadata is stored in NDSeDirectory like fileobject permissions ownership etc NWFS OCFS OCFS2 ocfs2 computes and validates checksums of metadata objects like inodes and directories It also stores an error correction code capable to fixing singlebite errors ODS5 Record Management Services RMS attributes include record type and size among many others OS4000 PramFS 1 second QFS ReiserFS Reiser4 Reliance CRCs are employed for certain types of metadata Reliance Nitro Linux port Linux port Linux port UDF UFS1 Accesscontrol lists and MAC labels are layered on top of extended attributes Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file eg FreeBSD 4x UFS2 V6FS V7FS VMFS2 VMFS3 VxFS XFS 1 nanosecond ZFS MACSensitivity labels are per filesystem A label per file are not out of the question as a future compatible change but arent part of any available version of ZFS Solaris extended attributes are really fullblown alternate data streams in both the Solaris UFS and ZFS ZFS also has system attributes used for storing MSDOSNTFS compatible attributes for use by CIFS as well as some attributes ported from FreeBSD 1 nanosecond File system Stores file owner POSIX file permissions Creation timestamps Last accessread 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 streamsforks Checksum ECC Max Timestamp Resolution 特點 檔案系統 硬連結 符號連結 Block journaling Metadataonly journaling 大小寫敏感 保留大小寫 檔案更改日誌 Snapshot XIP 寫時複製 Integrated LVM Data deduplication 卷可調整大小 Be File System Btrfs Planned via bedup CBM DOS CPM file system DECtape DOS GEC ext2 Linux kernel versions 2612 and newer Offline growingshrinking as well as online growing ext3 Off by default ext3cow Off by default ext4 exFAT FAT12 FAT16 FAT32 FFS Write Ahead Physical Block Logging in NetBSD provides metadata journaling and consistency as an alternative to softdep Fossil When used with venti When used with venti When used with venti GFS 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 Optional journaling of data GPFS HAMMER HFS 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 HFS Plus Metadataonly journaling was introduced in the Mac OS 1022 HFS Plus driver journaling is enabled by default on Mac OS 103 and later Although often believed to be case sensitive HFS Plus normally is not The typical default installation is casepreserving only From Mac OS 103 on the command newfs_hfs s will create a casesensitive new file system HFS Plus version 5 optionally supports casesensitivity However since casesensitivity is fundamentally different from caseinsensitivity a new signature was required so existing HFS Plus utilities would not see casesensitivity 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 Apples File System Comparisons which hasnt been updated to discuss HFSX and Technical Note TN1150 HFS Plus Volume Format which provides a very technical overview of HFS Plus and HFSX Mac OS Tiger 104 and late versions of Panther 103 provide file change logging its a feature of the file system software not of the volume format actually See fslogger As of OS X 107 HFS supports full volume file encryption known as Filevault 2 Since Mac OS X Snow Leopard online resizing is supported HPFS JFS Particular Installable File System drivers and operating systems may not support case sensitivity for JFS OS2 does not and Linux has a mount option for disabling case sensitivity Lanyard Filesystem LevelD LFS UDF LFS and NILFS are logstructured file systems and behave as if the entire file system were a journal Lustre in 20 and later Not available with ext34 but will be available with ZFS OSTMDT backing filesystems Can be shrunk online by migrating files off an OST and removing the OST or offline with ext34 backing filesystems by shrinking the OST filesystem NILFS NSS CasesensitivityPreservation depends on client Windows DOS and OS2 clients dont seekeep case differences whereas clients accessing via NFS or AFP may The file change logs last entry change timestamps and other filesystem metadata are all part of the extensive suite of auditing capabilities built into NDSeDirectory called NSure Audit Filesystem Events tracked by NSure NTFS As of Windows Vista NTFS fully supports soft links See this Microsoft article on Vista kernel improvements NTFS 50 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 neednt be NTFS Junctions are implemented through reparse points which allow the normal process of filename resolution to be extended in a flexible manner NTFS stores everything even the file data as metadata so its log is closer to block journaling 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 caseinsensitive 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 casesensitivity NTFS does not internally support snapshots but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots Windows Server 2012 NWFS Available only in the NFS namespace Limited capability Volumes can span physical disks volume segment OCFS OCFS2 OCFS2 supports creating multiple writeable snapshots of regular files using REFLINK ODS2 These are referred to as aliases ODS5 OS4000 Symlinks only visible to NFS clients References and OffDisk Pointers ODPs provide local equivalent PramFS QFS ReiserFS Full block journaling for ReiserFS was not added to Linux 268 for obvious reasons Reiser4 Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 41 Reliance File system implements reliability via atomic transactions Reliance Nitro on OS RT11 UDF UFS1 UFS2 Soft dependencies softdep in NetBSD called soft updates in FreeBSD provide metadata consistency at all times without double writes journalingBlock level journals can be added by using gjournal module in FreeBSD V6FS V7FS 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 didnt support them VxFS VxFS provides an optional feature called Storage Checkpoints which allows for advanced file system snapshots VMFS2 VMFS3 XFS Optionally no on IRIX and Linux ZFS ZFS is a transactional filesystem using copyonwrite semantics guaranteeing an alwaysconsistent ondisk 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 File system Hard links Symbolic links Block journaling Metadataonly journaling Casesensitive Casepreserving File Change Log Snapshotting XIP Encryption COW Integrated LVM Data deduplication Volumes are resizeable Allocation and layout policies 檔案系統 Block suballocation Variable file block sizeVariable block size refers to systems which support different block sizes on a perfile basis This is similar to extents but a slightly different implementational choice The current implementation in UFS2 is readonly Extents Allocateonflush 稀疏檔案 Transparent compression Be File System Btrfs Btrfs can only inline files smaller than 3916B with its metadata CBM DOS only for REL record structured files up to 254 bytesrecord CPM filesystem DECtape DOS GEC ext2 Fragments were planned but never actually implemented on ext2 and ext3 e2compr a set of patches providing blockbased compression for ext2 has been available since 1997 but has never been merged into the mainline Linux kernel ext3 ext3cow ext4 exFAT FAT12 SuperStor in DR DOS 60 and PC DOS 61 DoubleSpace in MSDOS 60 DriveSpace in MSDOS 622 Windows 95 and Windows 98 and Stacker in Novell DOS 7 OpenDOS 701 DRDOS 702703 and PC DOS 702000 were data compression schemes for FAT FAT16 FAT32 FFS 81Other blockfragment size ratios supported 81 is typical and recommended by most implementations Fossil When used with venti GFS Only for stuffed inodes GPFS HFS Plus HPFS JFS only in JFS1 on AIX LevelD LFS 81 Lustre NSS NILFS Planned NTFS Only if formatted with 4kBsized clusters or smaller NWFS 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 OCFS OCFS2 ODS5 OS4000 PramFS QFS ReiserFS Reiser4 In extents mode Reliance Reliance Nitro UDF Depends on UDF implementation UFS1 81 UFS2 81 V6FS V7FS VMFS2 VMFS3 VxFS XFS ZFS When enabled ZFSs logicalblock based compression behaves much like tailpacking for the last block of a file File system Block suballocation Variable file block size Extents Allocateonflush Sparse files Transparent compression 支援的作業系統 檔案系統 DOS Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX zOS OS2 Windows CE Windows Mobile VxWorks HPUX Plan 9 BFS 需使用第三方驅動程式，只讀 需使用第三方驅動程式，只讀 只讀 Btrfs With WinBtrfs 核心版本 2629 至 39 不穩定；核心版本 310 後穩定 DECtape with AncientFS with AncientFS with AncientFS exFAT 需使用第三方驅動程式，只讀 Win7 Vista SP1 can be added to XP SP2 SP3 since kernel 54 1065 限制簇大小為 1024 位元組 ext2 with Ext2Fsd complete Ext2Fsd is an open source ext2ext3ext4 kernellevel file system driver for Windows systems NT2KXPVISTA7 X86AMD64 that provides both readwrite access to the file system Currently does not fully support extents no size truncatingextending no file deletion a default feature of ext4 or Ext2 IFS partial no large inodes Ext2 IFS for Windows provides kernellevel readwrite 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 or Ext2Read readonly also on LVM2 Ext2Read is an explorerlike utility to explore ext2ext3ext4 file systems that provides readonly access to the file system It supports extents large inodes and LVM2 volumesExt2Read since kernel 099 with ExtFSParagon ExtFS for Mac is a lowlevel file system driver specially developed to bridge file system incompatibility between Linux and Mac by providing full readwrite access to the Ext2 Ext3 and Ext4 file systems under Mac OS X fuseext2Fuseext2 is a multi OS FUSE module to mount ext2 and ext3 file system devices andor images with read and write support and ext2fsxExt2fsx is the first and old implementation of the Ext2 Linux filesystem for Mac OS X 只讀 thirdparty app with 3rdparty appSee Total Commander which supports accessing ext2 ext3 and ReiserFS from Windows Windows CE and Windows Mobile with 3rdparty app ext3 with Ext2Fsd complete or Ext2 IFS partial no large inodes or Ext2Read readonly also on LVM2 since kernel 2415 with ExtFS and fuseext2 readonly with 3rdparty app with 3rdparty app ext3cow Kernel 2620 ext4 with Ext2Fsd partial extents limited or Ext2Read readonly also on LVM2 since kernel 2628 with ExtFS full readwrite fuseext2 partial and ext4fuse readonly ext4fuse is a free software multi OS FUSE module to mount ext4 file system devices andor images with readonly support support in kernel since version 101 readonly or with ext4fuse readonly FAT12 on diskettes only through dos commands Files Databases and Persistent Storage MSDN Via dosFs FAT16 since DOS 30 FAT16B since DOS 331 on diskettes only through dos commands FAT32 since DOS 71Native FAT32 support with MSDOS 710 and 80 Loadable FAT32 support for any DOS since 331 with DRFAT32 redirector driver Native FAT32 support since OEM DRDOS 704 bootable FAT32 support since OEM DRDOS 706 Native FAT32 support with OEM PC DOS 710 since Windows 95 OSR2 since Windows 2000 on diskettes only through dos commands with thirdparty app Via dosFs FFS Fossil with 3rdparty softwareVia Plan 9 from User Space initial checkin with 3rdparty software with 3rdparty software with 3rdparty software GFS since kernel 2619 HFS with thirdparty app with thirdparty app readonly since OSX 106 with thirdparty app with thirdparty app HFS Plus with thirdparty app with thirdparty app write support occurs if journal is empty but requires a force mount since Mac OS 81 readonly thirdparty app with thirdparty app HPFS with thirdparty driver readonly thirdparty driver included until v351 thirdparty driver until 40 IBM Spectrum Scale since 2001 IBM HFS IBM zFS JFS LevelD LFS with logfs and others LTFS Lustre under development via FUSE via FUSE under development NILFS since kernel 2630 NSS with Novell OES2 NTFS with thirdparty driver with thirdparty driver Kernel 22 or newer or with NTFS3G or ntfsprogs with NTFS3G or MacFUSE with NTFS3G or partial readonly in kernel with NTFS3G readonly with NTFS3G on Opensolaris readonly thirdparty driver with 3rdparty driverTuxera NTFS for Windows CE See and announcement NWFS via ncpfs client software OCFS OCFS2 ODS2 readonly with tool or kernel module ODS5 readonly with kernel module PramFS QFS via client softwareUsing SAMQFS on Linux Clients ReFS since Windows Server 2012 and Windows 81 Reiser4 with DiskInternals Linux Reader readonly with a kernel patch ReiserFS with DiskInternals Linux Reader readonly since kernel 241 read only read only with 3rdparty app with 3rdparty app Reliance Reliance Nitro RT11 UDF readonly support of UDF 102 since Win95 OSR2 since Mac OS 9 UFS1 read only UFS2 with DiskInternals Linux ReaderDiskInternals Linux Reader is an application for Windows NT that allows reading of Ext234 ReiserFS Reiser4 HFSHFS FATexFAT NTFS ReFS and UFS2 filesystems readonly read only VMFS2 VMFS3 readonly with vmfs VxFS XFS since kernel 24 readonly ZFS with 3rd Party kernel module or FUSEZFS on FUSE with free 3rdparty software File system DOS Windows 9x Windows NT Linux Mac OS Mac OS X FreeBSD BeOS Solaris AIX zOS OS2 Windows CE Windows Mobile VxWorks HPUX Plan 9 參見 壓縮檔案格式列表 壓縮軟體比較 壓縮軟體列表 檔案系統列表 註釋 外部連結 A speed comparison of filesystems on Linux 245 archived Filesystems ext3 reiser xfs jfs comparison on Debian Etch April 23 2006 Category 檔案系統