SUPPORT THE WORK
GetWiki
comparison of file systems#Metadata
ARTICLE SUBJECTS
being →
database →
ethics →
fiction →
history →
internet →
language →
linux →
logic →
method →
news →
policy →
purpose →
religion →
science →
software →
truth →
unix →
wiki →
ARTICLE TYPES
essay →
feed →
help →
system →
wiki →
ARTICLE ORIGINS
critical →
forked →
imported →
original →
comparison of file systems#Metadata
please note:
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
{{Short description|None}}{{Incomplete list|date=July 2015}}The following tables compare general and technical information for a number of file systems.- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
General information {| class“wikitable sortable” style@width: auto; text-align: center; table-layout: fixed;”
! scope=“col” | File system! scope=“col” | Creator! scope=“col” | Year of introduction! scope=“col” | Original operating system| DECtape | Digital Equipment Corporation>DEC| 1964| PDP-6 Monitor |
| OS/3x0 FS| IBM| 1964| OS/360 |
| Level-D | Digital Equipment Corporation>DEC| 1968| TOPS-10 |
| George 3 | International Computers and Tabulators>ICT (later ICL)| 1968 | GEORGE (operating system)>George 3 |
| Version 6 Unix file system (V6FS)| Bell Labs| 1972| Version 6 Unix |
| RT-11 file system | Digital Equipment Corporation>DEC| 1973| RT-11 |
| Disk Operating System (GEC DOS) | The General Electric Company plc>GEC| 1973| Core Operating System |
| CP/M file system| Digital Research (Gary Kildall)| 1974 | CP/MHTTP://WWW.COMPUTERHISTORY.ORG/ATCHM/IN-HIS-OWN-WORDS-GARY-KILDALL/ | AUTHOR-FIRST=LEN | DATE=2016-08-02 | PUBLISHER=COMPUTER HISTORY MUSEUM, 1993>DATE=2016-08-02 | AUTHOR-FIRST=GARY ARLEN | AUTHOR-LINK=GARY KILDALL | EDITOR-LAST1=KILDALL | EDITOR-FIRST2=KRISTIN | PUBLISHER=KILDALL FAMILY | URL=HTTP://WWW.COMPUTERHISTORY.ORG/ATCHM/COMPUTER-HISTORY-MUSEUM-LICENSE-AGREEMENT-FOR-THE-KILDALL-MANUSCRIPT/, 2016-11-17, |
| ODS-1 | Digital Equipment Corporation>DEC| 1975| RSX-11 |
| GEC DOS filing system extended | The General Electric Company plc>GEC| 1977| OS4000 |
| FAT (8-bit) | Microsoft (Marc McDonald) for National Cash Register>NCR| 1977| Microsoft Standalone Disk BASIC-80 (later Microsoft Standalone Disk BASIC-86) |
| DOS 3.x | Apple Inc.>Apple| 1978| Apple DOS |
| UCSD p-System| UCSD| 1978| UCSD p-System |
| CBM DOS | Commodore International>Commodore| 1978| Commodore BASIC |
| Atari DOS| Atari| 1979| Atari 8-bit |
| Version 7 Unix file system (V7FS)| Bell Labs| 1979| Version 7 Unix |
| ODS-2 | Digital Equipment Corporation>DEC| 1979| OpenVMS |
| FAT12| Seattle Computer Products (Tim Paterson)| 1980 | QDOS (SCP)>QDOS/86-DOS (later IBM PC DOS 1.0) |
| ProDOS | Apple Inc.>Apple| 1980 | Apple SOS (later PRODOS>ProDOS 8) |
| DFS| Acorn Computers Ltd| 1982 | BBC Micro>Acorn BBC Micro MOS |
| ADFS| Acorn Computers Ltd| 1983 | Acorn Electron (later RISC OS>Arthur/RISC OS) |
| FFS | Marshall Kirk McKusick>Kirk McKusick| 1983| 4.2BSD |
| FAT16| IBM, Microsoft| 1984| PC DOS 3.0, MS-DOS 3.0 |
| MFS | Apple Inc.>Apple| 1984| System 1 |
| Elektronika BK tape format| NPO “Scientific centre” (now Sitronics)| 1985| Vilnius Basic, BK monitor program |
| HFS | Apple Inc.>Apple| 1985| System 2.1 |
| Amiga Old File System | {{ref>54}} | Metacomco for Commodore International>Commodore| 1985| Amiga OS |
| GEMDOS| Digital Research| 1985| Atari TOS |
| NWFS| Novell| 1985| NetWare 286 |
| High Sierra| Ecma International| 1986 | MSCDEX for MS-DOS 3.1/3.2EXTENSIONS TO MS-DOS RUN CD-ROM | AUTHOR-LAST=MACE | INFOWORLD >VOLUME=8 | DATE=1986-09-22 | URL=HTTPS://BOOKS.GOOGLE.COM/BOOKS?ID=ZS8EAAAAMBAJ&PG=PA1, 2016-11-09, |
| FAT16B| Compaq| 1987 | Compaq MS-DOS 3.31 |
| Minix V1 FS| Andrew S. Tanenbaum| 1987| MINIX 1.0 |
| Amiga FFS | Commodore International>Commodore| 1988| Amiga OS 1.3 |
| (ISO 9660:1988)| Ecma International, ISO| 1988| MS-DOS, “classic” Mac OS, and AmigaOS |
| HPFS| IBM & Microsoft| 1989 | OS/2 1.2 |
| Rock Ridge| IEEE | 1990|sortable=yes}}| Unix |
| JFS1| IBM| 1990 | IBM AIX>AIX{{efn | IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, on which the Linux port was based, was first shipped in OS/2 Warp Server for e-Business in 1999. The same sourcebase was also used for release JFS2 on AIX 5L.}} |
| VxFS | Veritas Software>VERITAS| 1991 | System V>SVR4.0 |
| ext| Rémy Card| 1992| Linux |
| AdvFS | Digital Equipment Corporation>DEC | DATE=20 OCTOBER 1993 | URL=HTTP://WWW.ORNL.GOV/LISTS/MAILING-LISTS/TRU64-UNIX-MANAGERS/1993/10/MSG00043.HTML | ARCHIVE-DATE=9 MARCH 2012, dead, | Digital Unix |
| NTFS | Microsoft (Gary Kimura, Tom Miller (computer programmer)>Tom Miller)| 1993| Windows NT 3.1 |
| LFS| Margo Seltzer| 1993 | Sprite operating system>Berkeley Sprite |
| ext2| Rémy Card| 1993| Linux, Hurd |
| Xiafs| Q. Frank Xia| 1993| Linux |
| UFS1 | Marshall Kirk McKusick>Kirk McKusick| 1994| 4.4BSD |
| XFS | Silicon Graphics>SGI| 1994| IRIX |
| HFS| IBM| 1994| MVS/ESA (now z/OS) |
| FAT16X| Microsoft| 1995| MS-DOS 7.0 / Windows 95 |
| Joliet (“CDFS“)| Microsoft| 1995| Microsoft Windows, Linux, “classic” Mac OS, and FreeBSD |
| UDF | International Organization for Standardization>ISO/Ecma International | /Optical Storage Technology Association>OSTA| 1995| {{n/a}} |
| FAT32, FAT32X| Microsoft| 1996 | MS-DOS 7.10 / Windows 95 OSR2{{efn >name=note-10 |Microsoft first introduced FAT32 in MS-DOS 7.1 / 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.}} |
| QFS| Sun Microsystems| 1996 | Solaris (operating system)>Solaris |
| GPFS| IBM| 1996 | IBM AIX>AIX, Linux |
| Be File System | Be Inc. (Dominic Giampaolo>D. Giampaolo, Cyril Meurillon)| 1996| BeOS |
| Minix V2 FS| Andrew S. Tanenbaum| 1997| MINIX 2.0 |
| HFS Plus | Apple Inc.>Apple| 1998| Mac OS 8.1 |
| NSS| Novell| 1998| NetWare 5 |
| PolyServe File System (PSFS)| PolyServe| 1998| Windows, Linux |
| ODS-5 | Digital Equipment Corporation>DEC| 1998| OpenVMS V7.2 |
| WAFL| NetApp| 1998 | NetApp filer>Data ONTAP |
| ext3| Stephen Tweedie| 1999| Linux |
| (ISO 9660:1999)| Ecma International, ISO| 1999| Microsoft Windows, Linux, “classic” Mac OS, FreeBSD, and AmigaOS |
| JFS| IBM| 1999| OS/2 Warp Server for e-business |
| GFS | Sistina Software>Sistina (Red Hat)| 2000| Linux |
| ReiserFS| Namesys| 2001| Linux |
| zFS| IBM| 2001| z/OS (backported to OS/390) |
| FATX| Microsoft| 2002| Xbox |
| UFS2 | Marshall Kirk McKusick>Kirk McKusick| 2002| FreeBSD 5.0 |
| OCFS| Oracle Corporation| 2002| Linux |
| SquashFS| Phillip Lougher, Robert Lougher| 2002| Linux |
| VMFS2| VMware| 2002| VMware ESX Server 2.0 |
| Lustre | Cluster File SystemsSUN MICROSYSTEMS EXPANDS HIGH PERFORMANCE COMPUTING PORTFOLIO WITH DEFINITIVE AGREEMENT TO ACQUIRE ASSETS OF CLUSTER FILE SYSTEMS, INCLUDING THE LUSTRE FILE SYSTEM | DATE=12 SEPTEMBER 2007 | URL=HTTP://WWW.SUN.COM/ABOUTSUN/PR/2007-09/SUNFLASH.20070912.2.XML | ARCHIVE-DATE=2 OCTOBER 2007, | 2002| Linux |
| Fossil| Bell Labs| 2003 | Plan 9 from Bell Labs>Plan 9 version 4 |
| Google File System| Google| 2003| Linux |
| ZFS| Sun Microsystems| 2004 | Solaris (operating system)>Solaris |
| Reiser4| Namesys| 2004| Linux |
| Non-Volatile File System| Palm, Inc.| 2004| Palm OS Garnet |
| BeeGFS|Fraunhofer/ ThinkParQ|2005|Linux |
| GlusterFS| Gluster Inc.| 2005| Linux |
| Minix V3 FS| Andrew S. Tanenbaum| 2005| MINIX 3 |
| OCFS2| Oracle Corporation| 2005| Linux |
| NILFS | Nippon Telegraph and Telephone>NTT| 2005| Linux |
| VMFS3| VMware| 2005| VMware ESX Server 3.0 |
| GFS2| Red Hat| 2006| Linux |
| ext4| various | 2006| Linux |
| exFAT| Microsoft| 2006| Windows CE 6.0 |
| Btrfs| Chris Mason| 2007| Linux |
| JXFS| Hyperion Entertainment| 2008| AmigaOS 4.1 |
| HAMMER | Matthew Dillon (computer scientist)>Matthew Dillon| 2008 | DragonFly BSD#2.0>DragonFly BSD 2.0 |
| LSFS| StarWind Software| 2009| Linux, FreeBSD, Windows |
| UniFS| Nasuni| 2009| Cloud |
| CASL| Nimble Storage| 2010| Linux |
| OrangeFS|Omnibond and others|2011| Linux |
| VMFS5| VMware| 2011| vSphere 5.0+ |
| CHFS| University of Szeged| 2011| NetBSD 6.0+ |
| ReFS| Microsoft| 2012| Windows Server 2012 |
| F2FS| Samsung Electronics| 2012| Linux |
| bcachefs| Kent Overstreet| 2015| Linux |
| APFS | Apple Inc.>Apple| 2016| macOS High Sierra, iOS 10.3 |
| NOVA | University of California, San Diego>UC, San Diego| 2017| Linux |
| BlueStore/Cephfs| Red Hat, University of California, Santa Cruz|2017|Linux |
| HAMMER2 | Matthew Dillon (computer scientist)>Matthew DillonHTTP://BXR.SU/D/SYS/VFS/HAMMER2/DESIGN>TITLE=HAMMER2/DESIGN | AUTHOR-LINK=MATTHEW DILLON (COMPUTER SCIENTIST) | PUBLISHER=DRAGONFLY BSD | ACCESS-DATE=2019-03-06, | 2017 | DragonFly BSD#5.0>DragonFly BSD 5.0 |
| EROFS | HuaweiHTTPS://WWW.XDA-DEVELOPERS.COM/HUAWEI-EROFS-LINUX-FILE-SYSTEM-ANDROID/ | DATE=JUNE 1, 2018, XDA Developer, |2018 | Android (operating system)>Android |
Metadata
{| class=“wikitable sortable” style="width: auto; text-align: center; table-layout: fixed; margin: 0;“! File system! Stores file owner! POSIX file permissions! Creation timestamps! Last access/ read timestamps! Last metadata change timestamps! Last archive timestamps! Access control lists! Security/ MAC labels! Extended attributes/ Alternate data streams/ forks! Metadata checksum/ ECC! File system| Bcachefs| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| Bcachefs |
| BeeGFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{dunno}}| {{yes}}| {{yes}}| BeeGFS |
| CP/M file system| {{no}}| {{no}} | Implemented in later versions as an extension}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| CP/M file system |
| DECtapeWEB
,bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf , | {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| DECtape, RT–11 Volume and File Formats Manual , Digital Equipment Corporation , August 1991 , 1–26 .. 1–32 |
| Elektronika BK tape format| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{yes}}| Elektronika BK |
| Level-D| {{yes}}| {{yes}}| {{yes}}| {{yes}} (date only)| {{yes}}| {{yes}}| {{yes}} (FILDAE)| {{no}}| {{no}}| {{no}}| Level-D |
| RT-11WEB
,bitsavers.trailing-edge.com/pdf/dec/pdp11/rt11/v5.6_Aug91/AA-PD6PA-TC_RT-11_Volume_and_File_Formats_Manual_Aug91.pdf , | {{no}}| {{no}}| {{yes}} (date only)| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{yes}}| RT-11, RT–11 Volume and File Formats Manual , Digital Equipment Corporation , August 1991 , 1–4 .. 1–12 |
| Version 6 Unix file system (V6FS)WEB
,www.utdallas.edu/~venky/os/Proj/disk.pdf
, Format of the Unix 6 file system , 2016-02-21 ,www.utdallas.edu/~venky/os/Proj/disk.pdf" title="web.archive.org/web/20160921012843www.utdallas.edu/~venky/os/Proj/disk.pdf">web.archive.org/web/20160921012843www.utdallas.edu/~venky/os/Proj/disk.pdf , 2016-09-21 , dead , | {{yes}}| {{yes}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| Version 6 Unix file system (V6FS) |
| Version 7 Unix file system (V7FS)See dinode structure on page 355 (FILESYS(5)) of WEB
,web.cuzuco.com/~cuzuco/v7/v7vol1.pdf
, Unix Programmers Manual , Bell Telephone Laboratories , Murray Hill, New Jersey , Seventh , January 1979 , 2016-02-21 , | {{yes}}| {{yes}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| Version 7 Unix file system (V7FS) |
| exFAT| {{no}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| exFAT |
| FAT12/FAT16/FAT32| {{no}}| {{no}}| {{yes}}| {{yes}} | name=fat-ctime |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.}}| {{no}}| {{no}}| {{no}} | name=note-22 |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.}}| {{no}}| FAT12/FAT16/FAT32 |
| HPFS | name=note-14 | f-node contains a field for a user identifier. This is not used except by OS/2>OS/2 Warp Server, however.}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{dunno}}| {{yes}}| {{no}} | High Performance File System>HPFS |
| NTFS| {{yes}} | name=note-5 |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.}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}} | As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.HTTPS://DOCS.MICROSOFT.COM/EN-US/WINDOWS/WIN32/SECAUTHZ/MANDATORY-INTEGRITY-CONTROL>TITLE=MANDATORY INTEGRITY CONTROL | MICROSOFT DOCS>DATE=25 MARCH 2021, 2022-08-14, }}| {{yes}}| {{no}}| NTFS |
| ReFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{dunno}} | Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS}}| {{yes}}| ReFS |
| HFS| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{no}} | Hierarchical File System (Apple)>HFS |
| HFS Plus| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{dunno}}| {{yes}}| {{no}}| HFS Plus |
| FFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | Berkeley Fast File System>FFS |
| UFS1| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}} | name=note-33 |Access-control lists and MAC labels are layered on top of extended attributes.}} | name=note-33}} | name=note-32 | UFS1 (file system)>UFS1 with a parallel backing file (e.g., FreeBSD 4.x).}}| {{no}} | UFS1 (file system)>UFS1 |
| UFS2| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}} | name=note-33}} | name=note-33}}| {{yes}}| {{partial}} | UFS2 (file system)>UFS2 |
| HAMMER| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{dunno}}| {{yes}}| {{yes}}| {{no}}| {{yes}} | HAMMER (file system)>HAMMER |
| LFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | Log-structured File System (BSD)>LFS |
| ext| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | extended file system>ext |
| Xiafs| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| Xiafs |
| ext2| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}} | name=note-23 | 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 (computing)>patch.}} | name=note-23}}| {{yes}}| {{no}}| ext2 |
| ext3| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}} | name=note-23}} | name=note-23}}| {{yes}}| {{no}}| ext3 |
| ext4| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}} | name=note-23}} | name=note-23}}| {{yes}} | Metadata is mostly checksummed,EXT4 DISK LAYOUT > URL=HTTPS://EXT4.WIKI.KERNEL.ORG/INDEX.PHP/EXT4_DISK_LAYOUT#CHECKSUMS, however Direct/indirect/triple-indirect block maps are not protected by checksumsEXT4 METADATA CHECKSUMS > URL=HTTPS://EXT4.WIKI.KERNEL.ORG/INDEX.PHP/EXT4_METADATA_CHECKSUMS#METADATA_NOT_BEING_UPGRADED, }}| ext4 |
| NOVA| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{yes}} | NOVA (filesystem)>NOVA |
| Lustre| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{no}} | Lustre (file system)>Lustre |
| F2FS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}} | name=note-23}} | name=note-23}}| {{yes}}| {{no}}| F2FS |
| GPFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| GPFS |
| GFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}} | name=note-23}} | name=note-23}}| {{yes}}| {{no}} | Global File System>GFS |
| NILFS| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{yes}}| NILFS |
| ReiserFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}} | name=note-23}} | name=note-23}}| {{yes}}| {{no}}| ReiserFS |
| Reiser4| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| Reiser4 |
| OCFS| {{no}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| OCFS |
| OCFS2| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| OCFS2 |
| XFS| {{yes}}| {{yes}} | name=note-35 |Creation time stored since June 2015, xfsprogs version 3.2.3}}| {{yes}}| {{yes}}| {{no}}| {{yes}} | name=note-23}}| {{yes}}| {{yes}}| XFS |
| JFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{no}} | JFS file system>JFS |
| QFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{no}}| QFS |
| BFS| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{yes}}| {{no}} | Be File System>BFS |
| AdvFS| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{no}}| {{yes}}| {{no}}| AdvFS |
| NSS| {{yes}}| {{yes}} | name=note-31 |The local time, time zone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.}} | name=note-31}}| {{yes}} | name=note-31}}| {{yes}}| {{dunno}} | name=note-19 | name=note-29 | Novell Directory Services>NDS/eDirectory, like file/object permissions, ownership, etc.}}| {{no}}
| NSS
|
| NWFS| {{yes}}| {{dunno}} | name=note-31}} | name=note-31}}| {{yes}} | name=note-31}}| {{yes}}| {{dunno}} | name=note-19}}{{efn |name=note-29}}| {{no}} | NetWare File System>NWFS |
| ODS-5| {{yes}}| {{yes}}| {{yes}}| {{dunno}}| {{dunno}}| {{yes}}| {{yes}}| {{dunno}} | name=note-17 |Record Management Services (RMS) attributes include record type and size, among many others.}}| {{no}}| ODS-5 |
| APFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| APFS |
| VxFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{dunno}} | name=note-23}}| {{no}} | Veritas File System>VxFS |
| UDF| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}} | Universal Disk Format>UDF |
| Fossil| {{yes}} | name=note-61 | 9P (protocol)>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.}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | Fossil (file system)>Fossil |
| ZFS| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}} | name=note-69 |Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.}} | name=note-60 |Solaris “extended attributes” are really full-blown alternate data streams, in both the Solaris UFS and ZFS.}}| {{yes}}| ZFS |
| Btrfs| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| Btrfs |
| Minix V1| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | MINIX file system>Minix V1 |
| Minix V2| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | MINIX file system>Minix V2 |
| Minix V3| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | MINIX file system>Minix V3 |
| VMFS2| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| VMFS2 |
| VMFS3| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| VMFS3 |
| (ISO 9660:1988)| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| (ISO 9660:1988) |
| Rock Ridge| {{yes}}| {{yes}}| {{no}} | Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.}}| {{yes}}| {{no}} | libburnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.}} | name=note-78|libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.}} | name=note-78}}| {{no}}| Rock Ridge |
| Joliet (“CDFS“)| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | Joliet (file system)>Joliet (“CDFS“) |
| (ISO 9660:1999)| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| (ISO 9660:1999) |
| High Sierra| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} | High Sierra Format>High Sierra |
| SquashFS| {{yes}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{yes}}| {{no}}| SquashFS |
| BlueStore/Cephfs| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{dunno}}| {{no}}| {{yes}}| {{yes}}| {{yes}}| {{yes}} | Ceph (software)>BlueStore/Cephfs |
Features
File capabilities
{| class=“wikitable sortable” style="width: auto; text-align: center; table-layout: fixed; margin: 0;“! File system! Hard links! Symbolic links! Block journaling! Metadata-only journaling! Case-sensitive! Case-preserving! File Change Log! XIP!Resident files (inline data)| Optional}}| {{yes}}| {{dunno}}| {{dunno}}| {{dunno}} |
| name=note-59 |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.}}| {{no}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{no}} |
| Transaction-Safe FAT File System>TexFAT only)| {{no}}| {{yes}}| {{no}}| {{no}}| {{no}} |
| 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}}| {{yes}} | Optional journaling of data}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{dunno}} |
| As of Windows Vista, NTFS fully supports symbolic links.HTTPS://DOCS.MICROSOFT.COM/EN-US/PREVIOUS-VERSIONS/TECHNET-MAGAZINE/CC162494(V=MSDN.10)>TITLE=WINDOWS ADMINISTRATION: INSIDE THE WINDOWS VISTA KERNEL: PART 1 | AUTHOR-LINK=MARK RUSSINOVICH | MAGAZINE=MICROSOFT TECHNET, TechNet, NTFS 3.0 (Windows 2000) and higher can create junctions, which allow entire directories (but not individual files) to be mapped to elsewhere in the directory tree of the same partition (file system). These are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.}} | name=note-37 |NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.}} | name=note-37}} (2000) | name=note-36 |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.}}| {{yes}}| {{yes}}| {{dunno}} | Yes}} (approximately 700 bytes) |
| TITLE=MAC OS X 10.7 LION: THE ARS TECHNICA REVIEW | WEBSITE=ARS TECHNICA | QUOTE=TO KEEP TRACK OF HARD LINKS, HFS+ CREATES A SEPARATE FILE FOR EACH HARD LINK INSIDE A HIDDEN DIRECTORY AT THE ROOT LEVEL OF THE VOLUME., 2011-07-20, | {{yes}}| {{no}} | name=note-48 |Metadata-only journaling was introduced in the Mac OS X 10.2.2 HFS Plus driver; journaling is enabled by default on Mac OS X 10.3 and later.}} | Optional}}{{efn | newfs_hfs -s will create a case-sensitive new file system.{{man>8 | Darwin}} 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.APPLE >URL=HTTPS://DEVELOPER.APPLE.COM/DOCUMENTATION/MACOSX/CONCEPTUAL/BPFILESYSTEM/ARTICLES/COMPARISONS.HTML | ARCHIVE-URL=HTTPS://WEB.ARCHIVE.ORG/WEB/20081006205615/HTTPS://DEVELOPER.APPLE.COM/DOCUMENTATION/MACOSX/CONCEPTUAL/BPFILESYSTEM/ARTICLES/COMPARISONS.HTML | URL-STATUS=DEAD, (hasn’t been updated to discuss HFSX)APPLE >URL=HTTPS://DEVELOPER.APPLE.COM/LIBRARY/ARCHIVE/TECHNOTES/TN/TN1150.HTML, Technical Note TN1150: HFS Plus Volume Format, (Very technical overview of HFS Plus and HFSX.)}}| {{yes}} | Mac OS X 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).HTTP://WWW.KERNELTHREAD.COM/SOFTWARE/FSLOGGER/ >TITLE=FSLOGGER | ARCHIVE-URL=HTTPS://WEB.ARCHIVE.ORG/WEB/20080918004451/HTTP://WWW.KERNELTHREAD.COM/SOFTWARE/FSLOGGER/ | URL-STATUS=DEAD, }}| {{no}}| {{dunno}} |
| name=note-66 | Soft dependencies” (softdep) in NetBSD, called “soft updates” in FreeBSD provide meta-data consistency at all times without double writes (journaling file system>journaling)}} HTTPS://WWW.MCKUSICK.COM/SOFTDEP/SUJ.PDF>TITLE=JOURNALED SOFT-UPDATES | LAST1=MCKUSICK | LAST2=ROBERSON, {{efn |
| name=note-38 |UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{dunno}} |
| name=note-65 |Linux kernel versions 2.6.12 and newer.}}| {{dunno}} |
| name=note-62 |Off by default.}}| {{yes}} (2001)| {{yes}}| {{yes}}| {{no}}| {{yes}}| {{dunno}} |
| name=note-62}}| {{yes}} | ACCESS-DATE=2022-12-24, www.kernel.org, |
| name=note-38}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{dunno}} |
| name=note-62}}| {{yes}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{dunno}} |
| name=note-38}}| {{no}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{dunno}} |
| name=note-44 |Full block journaling for ReiserFS was added to Linux 2.6.8.}}| {{yes}}| {{yes}}| {{yes}}| {{no}}| {{dunno}}| {{dunno}} |
| name=note-40 |Optionally no on IRIX and Linux.}}| {{yes}}| {{yes}}| {{dunno}}| {{dunno}} |
| name=note-30 |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.}}| {{yes}}| {{no}}| {{dunno}}| {{dunno}} |
| name=note-20 |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.}} | name=note-20}} | name=note-6 |
| name=note-53 |Available only in the “NFS” namespace.}} | name=note-53}}| {{no}}| {{no}} | name=note-20}} | name=note-20}} | name=note-6}}| {{no}}| {{dunno}} |
| name=note-18 |These are referred to as “aliases”.}}| {{no}}| {{yes}}| {{no}}| {{no}}| {{yes}}| {{no}}| {{dunno}} |
| name=note-18}}| {{no}}| {{yes}}| {{no}}| {{yes}}| {{yes}}| {{dunno}}| {{dunno}} |
| name=note-38}} | name=note-38}}| {{yes}}| {{yes}}| {{no}}| {{yes}} | PAGE=34, This file, when small, can be embedded in the [Information Control Block] that describes it., |
| name=note-56 |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.}} | name=note-56}}| {{yes}}| {{yes}}| {{no}}| {{no}}| {{dunno}} |
| name=note-80 |Btrfs is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. It keeps track of last five transactions and uses checksums to find problematic drives, making write intent logs unnecessary.}}| {{no}}| {{yes}}| {{yes}}| {{dunno}}| {{dunno}}| {{dunno}} |
| Bcachefs is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. Journal commits are fairly expensive operations as they require issuing FLUSH and FUA operations to the underlying devices. By default, a journal flush is issued one second after a filesystem update has been done, which primarily records btree updates ordered by when they occurred. This option may be useful on a personal workstation or laptop, and perhaps less appropriate on a server.}}| {{no}}| {{yes}}| {{yes}}| {{dunno}}| {{dunno}}| {{dunno}} |
| Since Windows 10 Enterprise Insider Preview build 19536}}| {{yes}}| {{dunno}}| {{dunno}} | name=note-36}}| {{yes}}| {{dunno}}| {{dunno}}| {{dunno}} |
Block capabilities
Note that in addition to the below table, block capabilities can be implemented below the file system layer in Linux (LVM, {{proper name|integritysetup}}, cryptsetup) or Windows (Volume Shadow Copy Service, SECURITY), etc.{| class=“wikitable sortable” style="width: auto; text-align: center; table-layout: fixed; margin: 0;“! File system! Internal snapshotting / branching! Encryption! Deduplication! Data checksum/ ECC! Persistent Cache! Multiple Devices! Compression! Self-healing{{efn |name=note-82|A file system is self-healing if its capable to proactively autonomously detect and correct all but grave errors, faults and corruptions online both in internal metadata AND data. See US7694191B1 as example. This usually requires full checksumming as well as internal redundancy as well as corresponding logic.}}| QUOTE=THE CLONED FILE DST SHARES ITS DATA BLOCKS WITH THE SRC FILE [..], | {{no}}| {{no}}| {{no}}| {{yes}}| {{no}} |
| name=FATcompress | Stacker 3/Stacker 4>4 and DriveSpace 3 compressed volumesDMSDOS CVF MODULE >TYPE=DMSDOC.DOC | DATE=1998-11-19 | ACCESS-DATE=2016-11-01 | ARCHIVE-URL=HTTPS://WEB.ARCHIVE.ORG/WEB/20161102123812/HTTP://CMP.FELK.CVUT.CZ/~PISA/DMSDOS/DMSDOS.HTML | QUOTE=USUALLY ALL DATA FOR ONE CLUSTER ARE STORED IN CONTIGUOUS SECTORS, BUT IF THE FILESYSTEM IS TOO FRAGMENTED THERE MAY NOT BE A ‘FREE HOLE’ THAT IS LARGE ENOUGH FOR THE DATA. […] DRIVESPACE 3 AND STACKER KNOW A HACK FOR THAT SITUATION: THEY ALLOW STORING THE DATA OF ONE CLUSTER IN SEVERAL FRAGMENTS ON THE DISK., }}| {{no}} |
| name=FATcompress}}| {{no}} |
| name=note-NTFS-Dedup | DATE=31 MAY 2018, | {{no}}| {{no}}| {{no}}| {{yes}}| {{no}} |
| name=note-77 |HFS+ does not actually encrypt files: to implement FileVault, OS X creates an HFS+ filesystem in a sparse, encrypted disk image that is automatically mounted over the home directory when the user logs in.}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}}| {{no}} |