Comparison_of_file_systems

Comparison of file systems

Comparison of file systems

Add article description

The following tables compare general and technical information for a number of file systems.

General information

More information File system, Creator ...

Metadata

More information File system, Stores file owner ...

Features

File capabilities

More information File system, Hard links ...

Block capabilities

Note that in addition to the below table, block capabilities can be implemented below the file system layer in Linux (LVM, integritysetup, cryptsetup) or Windows (Volume Shadow Copy Service, SECURITY), etc.

More information File system, Internal snapshotting / branching ...

Resize capabilities

"Online" and "offline" are synonymous with "mounted" and "not mounted".

More information File system, Host OS ...

Allocation and layout policies

More information File system, Sparse files ...

OS support

More information File system, DOS ...

Limits

While storage devices usually have their size expressed in powers of 10 (for instance a 1 TB Solid State Drive will contain at least 1,000,000,000,000 (1012, 10004) bytes), filesystem limits are invariably powers of 2, so usually expressed with IEC prefixes. For instance, a 1 TiB limit means 240, 10244 bytes. Approximations (rounding down) using power of 10 are also given below to clarify.

More information File system, Maximum filename length ...

See also

Notes

  1. IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, 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.
  2. 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.
  3. Implemented in later versions as an extension
  4. 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.
  5. 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.
  6. The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
  7. 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.
  8. As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.[12]
  9. Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS
  10. Access-control lists and MAC labels are layered on top of extended attributes.
  11. Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
  12. 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.
  13. Metadata is mostly checksummed,[13] however Direct/indirect/triple-indirect block maps are not protected by checksums[14]
  14. Creation time stored since June 2015, xfsprogs version 3.2.3
  15. 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.
  16. 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.
  17. 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.
  18. Record Management Services (RMS) attributes include record type and size, among many others.
  19. 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.
  20. Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.
  21. Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.
  22. Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.
  23. libburnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.
  24. libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.
  25. 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.
  26. 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
  27. Optional journaling of data
  28. As of Windows Vista, NTFS fully supports symbolic links.[15] 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.
  29. NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
  30. 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.
  31. 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.
  32. Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS X 10.3 on the command newfs_hfs -s will create a case-sensitive new file system.[17] 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.[18][19]
  33. 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).[20]
  34. "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling)
  35. Journaled Soft Updates (SU+J) are the default as of FreeBSD 9.x-RELEASE [22][23]
  36. UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
  37. Linux kernel versions 2.6.12 and newer.
  38. Off by default.
  39. Full block journaling for ReiserFS was added to Linux 2.6.8.
  40. Optionally no on IRIX and Linux.
  41. 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.
  42. 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.
  43. 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.[26]
  44. Available only in the "NFS" namespace.
  45. These are referred to as "aliases".
  46. 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.
  47. 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.
  48. 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.
  49. Since Windows 10 Enterprise Insider Preview build 19536
  50. 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.
  51. only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[29]
  52. Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.
  53. 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.
  54. Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
  55. VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
  56. Applies to proprietary ZFS release 30 and ZFS On Linux. Encryption support is not yet available in all OpenZFS ports.[36][37][38]
  57. LZJB (optimized for performance while providing decent data compression)
    LZ4 (faster & higher ratio than lzjb)
    gzip levels: 1 (fastest) to 9 (best), default is 6
    zstd positive: 1 (fastest) to 19 (best), default is 3
    zstd negative: 1(best & default)-10, 20, 30, …, 100, 500, 1000(fastest)
    zle: compresses runs of zeros.[39]
  58. disabling copy-on-write (COW) to prevent fragmentation also disables data checksumming
  59. zlib levels: 1 to 9, default is 3
    LZO (no levels) faster than ZLIB, worse ratio
    zstd levels: 1 to 15 (higher levels are not available)[40]
  60. none
    CRC-32C (default)
    crc64
    chacha20/poly1305 (When encryption is enabled. Encryption can only be specified for the entire filesystem, not per file or directory)[41]
  61. none (default)
    The three currently supported algorithms are gzip, LZ4, zstd.
    The compression level may also be optionally specified, as an integer between 0 and 15, e.g. lz4:15. 0 specifies the default compression level, 1 specifies the fastest and lowest compression ratio, and 15 the slowest and best compression ratio.[42]
  62. By using the per-file "integrity stream" that internally stores a checksum per cluster. Those per cluster checksums are not accessible so it is actually a per file feature and not a per block feature. Integrity streams are not enabled by default.
  63. Some file system creation implementations reuse block references and support deduplication this way. This is not supported by the standard, but usually works well due to the file system's read-only nature.
  64. With software based on GNU Parted.
  65. 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.
  66. Only for "stuffed" inodes
  67. Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
  68. Fragments were planned, but never actually implemented on ext2 and ext3.
  69. Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.
  70. Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.
  71. In "extents" mode.
  72. 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.
  73. Depends on UDF implementation.
  74. ISO 9660 Level 3 only
  75. Supported using only EVMS; not currently supported using LVM
  76. Provided in Plan 9 from User Space
  77. FUSE based driver available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.
  78. Filesystem driver "Dokany" available that can eliminate need for iSCSI gateways or SMB shares, but the physical backend store BlueStore only runs on Linux.
  79. 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; operating systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
  80. 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 KiB (131.0 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 KiB (32.76 KB)).
  81. 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.
  82. The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. Limited by its Current Directory Structure (CDS), DOS does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 bytes for FAT, or 255 characters for LFNs. Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Older POSIX APIs which rely on the PATH_MAX constant have a limit of 4,096 bytes on Linux but this can be worked around. Linux itself has no hard path length limits.[119][120]
  83. Varies wildly according to block size and fragmentation of block allocation groups.
  84. Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, 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 OEM characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also must not contain lowercase letters. A few special device names (CON, NUL, AUX, PRN, LPT1, COM1, etc.) should be avoided, as some operating systems (notably DOS, OS/2 and Windows) reserve them.
  85. On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size.
  86. While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB (34.35 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.[101]
  87. Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). [103]
  88. Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). [104]
  89. Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB (2.199 TB). For 32-bit 2.6 kernels it is 16 TiB (17.59 TB). For 64-bit 2.6 kernels it is 8 EiB (9.223 EB).
  90. The "classic" 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.
  91. 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.
  92. 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.
  93. 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 GiB (68.71 GB).
  94. ISO 9660#Restrictions
  95. Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB (4.294 GB) in size. See ISO 9660#The 2 GiB (2.147 GB) (or 4 GiB (4.294 GB) depending on implementation) file size limit
  96. 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.
  97. Sparse files can be larger than the file system size, even though they can't contain more data.
  98. NSS allows files to have multiple names, in separate namespaces.
  99. 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 TiB (281.4 TB) and the file size to 16 TiB (17.59 TB) respectively; in Windows 10 version 1709, the limit is 8 PiB (9.007 PB) when using 2 MiB (2.097 MB) cluster size.
  100. 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.
  101. Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.
  102. Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.
  103. 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.
  104. ReiserFS has a theoretical maximum file size of 1 EiB (1.152 EB), but "page cache limits this to 8 Ti on architectures with 32 bit int"[116]
  105. This restriction might be lifted in newer versions.
  106. The file size in the inode is 1 8-bit byte followed by 1 16-bit word, for 24 bits. The actual maximum was 8,847,360 bytes, with 7 singly-indirect blocks and 1 doubly-indirect block; PWB/UNIX 1.0's variant had 8 singly-indirect blocks, making the maximum 524,288 bytes or half a MB.
  107. 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 GiB (4.294 GB).
  108. 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.
  109. Note that the filename can be much longer XFS#Extended attributes
  110. XFS has a limitation under Linux 2.4 of 64 TiB (70.36 TB) file size, but Linux 2.4 only supports a maximum block size of 2 TiB (2.199 TB). This limitation is not present under IRIX.

References

  1. [1]
    Shustek, Len (2016-08-02). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.
  2. [2]
    Kildall, Gary Arlen (2016-08-02) [1993]. Kildall, Scott; Kildall, Kristin (eds.). "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family. Retrieved 2016-11-17.
  3. [3]
    Mace, Scott (1986-09-22). "Extensions to MS-DOS Run CD-ROM". InfoWorld. 8 (38): 1, 8. Retrieved 2016-11-09.
  4. [4]
    Warren, David (20 October 1993). "Polycenter File System - - HELP". Archived from the original on 9 March 2012.
  5. [5]
    "Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System" (Press release). Santa Clara, Calif.: Sun Microsystems, Inc. 12 September 2007. Archived from the original on 2 October 2007.
  6. [6]
    Matthew Dillon (2018-12-09). "hammer2/DESIGN". BSD Cross Reference. DragonFly BSD. Retrieved 2019-03-06.
  7. [7]
    "Huawei announces the EROFS Linux file system intended for Android devices". XDA Developer. June 1, 2018.
  8. [8]
    "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–26 .. 1–32.
  9. [9]
    "RT–11 Volume and File Formats Manual" (PDF). Digital Equipment Corporation. August 1991. pp. 1–4 .. 1–12.
  10. [10]
    "Format of the Unix 6 file system" (PDF). Archived from the original (PDF) on 2016-09-21. Retrieved 2016-02-21.
  11. [11]
    See dinode structure on page 355 (FILESYS(5)) of "Unix Programmers Manual" (PDF) (Seventh ed.). Murray Hill, New Jersey: Bell Telephone Laboratories. January 1979. Retrieved 2016-02-21.
  12. [12]
    "Mandatory Integrity Control". Microsoft Docs. 25 March 2021. Retrieved 2022-08-14.
  13. [13]
    "Ext4 Disk Layout".
  14. [14]
    "Ext4 Metadata Checksums".
  15. [15]
    Mark Russinovich (February 2007). "Windows Administration: Inside the Windows Vista Kernel: Part 1". TechNet.
  16. [16]
    Siracusa, John (2011-07-20). "Mac OS X 10.7 Lion: the Ars Technica review". Ars Technica. Retrieved 14 December 2017. 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.
  17. [17]
    newfs_hfs(8) – Darwin and macOS System Manager's Manual
  18. [18]
    "File System Comparisons". Apple. Archived from the original on 2008-10-06. (hasn't been updated to discuss HFSX)
  19. [19]
    "Technical Note TN1150: HFS Plus Volume Format". Apple. (Very technical overview of HFS Plus and HFSX.)
  20. [20]
    "fslogger". Archived from the original on 2008-09-18. Retrieved 2006-08-03.
  21. [21]
    McKusick, Marshall Kirk; Roberson, Jeff. "Journaled Soft-updates" (PDF).
  22. [22]
    "NewFAQs - FreeBSD Wiki".
  23. [23]
    "FreeBSD 9.0-RELEASE Announcement".
  24. [24]
    "EXT4 Case-Insensitive Directories/File-Name Lookups Coming With Linux 5.2".
  25. [25]
    "2. High Level Design — The Linux Kernel documentation § 2.10. Inline Data". www.kernel.org. Retrieved 2022-12-24.
  26. [26]
    "Filesystem Events tracked by NSure".
  27. [27]
    "Universal Disk Format Specification – Revision 2.60" (PDF). p. 34. This file, when small, can be embedded in the [Information Control Block] that describes it.
  28. [28]
    "clonefile(2)". The cloned file dst shares its data blocks with the src file [..]
  29. [29]
    "DMSDOS CVF module" (dmsdoc.doc). 0.9.2.0. 1998-11-19. Archived from the original on 2016-11-02. Retrieved 2016-11-01. 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.
  30. [30]
    "About Data Deduplication". 31 May 2018.
  31. [31]
    "Ext4 encryption".
  32. [32]
    "Red Hat: What is bitrot?".
  33. [33]
    "F2FS encryption".
  34. [34]
    "mkfs.xfs(8) from xfsprogs 5.10.0-4". By default, mkfs.xfs [..] will enable the reflink [=deduplication] feature.
  35. [35]
    "JFS data compression". IBM. Retrieved 2020-07-26.
  36. [36]
    Moffat, Darren (July 2012). "How to Manage ZFS Data Encryption". Retrieved 2022-08-14.
  37. [37]
    "Release zfs-0.8.0". GitHub. 2020-01-21.
  38. [38]
    "Feature Flags - OpenZFS".
  39. [39]
    "zfsprops.7 — OpenZFS documentation". GitHub. 2023-08-26. Retrieved 2023-09-14.
  40. [40]
    "Compression — BTRFS documentation". GitHub. 2023-07-26. Retrieved 2023-09-14.
  41. [41]
    Overstreet, Kent (18 Dec 2021). "bcachefs: Principles of Operation" (PDF). Retrieved 10 May 2023.
  42. [42]
    "bcachefs/ Compression". 11 Sep 2023. Retrieved 14 Jan 2024.
  43. [43]
    "IBM's Journaled File System (JFS) for Linux".
  44. [44]
    "Growing an XFS File System".
  45. [45]
    "Shrinking Support - xfs.org". XFS Wiki. 2022-07-17. Archived from the original on 2022-07-17. Retrieved 2022-12-18.
  46. [46]
    "Frequently Asked Questions (Old Wiki)". Retrieved 5 May 2018.
  47. [47]
    "Kernel/Git/Jaegeuk/F2fs-tools.git - Userland tools for the f2fs filesystem".
  48. [48]
    "ntfsresize(8)".
  49. [49]
    resize2fs(8) – Linux Programmer's Manual – Administration and Privileged Commands
  50. [50]
    "Resizing File Systems".
  51. [51]
    "Resize reiserfs". Reiserfs wiki.
  52. [52]
    "Just Enough Operating System (JeOS): Technical Information | SUSE". www.suse.com. Retrieved 28 April 2018.
  53. [53]
    "nilfs-resize(8)".
  54. [54]
    Mirror and single-disk vdevs can be wholly removed from a pool, but not RAID-Z vdevs. "OpenZFS 7614 - zfs device evacuation/removal". GitHub.
  55. [55]
    "Resizing and Growing Disks".
  56. [56]
    "Mac users, meet APFS: macOS's new file system - ZDNet". ZDNet.
  57. [57]
    "Apple File System Guide - FAQ".
  58. [58]
    "CVF Region: MDFAT".
  59. [59]
    "Mapping DOS FAT to MDFAT".
  60. [60]
    "[base] Revision 216796".
  61. [61]
    "Newfs(8)".
  62. [62]
    Jaeguk Kim (2014-09-22). "[PATCH 2/3] f2fs: Introduce FITRIM in f2fs_ioctl". linux-kernel (Mailing list).
  63. [63]
    "Reiser4 discard support". Reiser4 FS Wiki.
  64. [64]
    "XFS Adds Shared Data Extents For Linux 4.9".
  65. [65]
    Android Kernel File System Support (Documentation). Android Open Source Project. Retrieved 2023-01-11.
  66. [66]
    "GitHub - sgan81/Apfs-fuse: FUSE driver for APFS (Apple File System)". GitHub. 2020-01-18.
  67. [67]
    "APFS module for linux, with experimental write support. This tree is just for development, please use linux-apfs-oot instead.: Linux-apfs/Linux-apfs". GitHub. 2019-12-14.
  68. [68]
    Namjae Jeon (20 January 2020). "[PATCH v12 00/13] add the latest exfat driver". linux-kernel (Mailing list). Retrieved 18 December 2021.
  69. [69]
    "NTFS3 Pull Request acceptance".
  70. [70]
    "Paragon HFS+ for Windows 10".
  71. [71]
    "Porting an Ancient Filesystem to Modern Linux". Time To Pull The Plug. Archived from the original on 2017-06-21. Retrieved 2016-04-22.
  72. [72]
    "A port of the xiafs filesystem to modern Linux kernels". Github (cdtk). 2019-06-28.
  73. [73]
    "Paragon ExtFS for Mac".
  74. [74]
    "Explore2fs". chrysocome.net.
  75. [75]
    "Paragon ExtFS for Windows".
  76. [76]
    "FAQ". Ext2 Installable File System For Windows. (Provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.)
  77. [77]
    Branten, Bo. "Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)". Archived from the original on 2012-07-23. Retrieved 2012-07-24.
  78. [78]
    "FreeBSD Handbook".
  79. [79]
    Hanselman, Scott (2021-11-02). "WSL2 can now mount Linux ext4 disks directly". Newsletter of Wonderful Things. Retrieved 2023-10-01.
  80. [80]
    Microsoft Corp. (2023-07-17). "Windows technical documentation: Windows development environment: Windows Subsystem for Linux". Microsoft Learn (published 2021-12-09). Archived from the original on 2021-12-27. Retrieved 2023-10-01.
  81. [81]
    "Lustre Wiki".
  82. [82]
    "FreeBSD 10.4 MAN page - reiserfs". www.freebsd.org. Retrieved 2019-08-05.
  83. [83]
    "FreeBSD 11 and Reiserfs". www.linuxquestions.org. 2016-12-19. Retrieved 2019-08-05.
  84. [84]
    "'svn commit: r300062 - in head/sys: gnu/fs modules modules/reiserfs' - MARC". marc.info. Retrieved 2019-08-05.
  85. [85]
    "About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide". Retrieved 2016-03-14.
  86. [86]
    "ZFS Filesystem for FUSE/Linux". Wizy Wiki. 30 November 2009. Archived from the original on 13 May 2013.
  87. [87]
    "ZFS on Linux". Lawrence Livermore National Laboratory.
  88. [88]
    Kim, Arnold (4 October 2007). "Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard". Mac Rumors.
  89. [89]
    "OpenZFS on Windows".
  90. [90]
    "WinBtrfs". Github (maharmstone). 2020-11-22.
  91. [91]
    "squashfs-tools". Freshports.
  92. [92]
    "fusefs-squashfuse". Freshports.
  93. [93]
    "Frequently Asked Questions".
  94. [94]
    "Volume Format Comparison".
  95. [95]
    "CephFS Maximum File Sizes and Performance".
  96. [96]
    "CephFS Directory Fragmentation".
  97. [97]
    "ExFAT: File Name Directory Entry".
  98. [98]
    "File System Functionality Comparison". Microsoft Docs. Microsoft. 2021-01-07. Retrieved 2022-08-14.
  99. [99]
    Vimal A.R (16 July 2016). "Max file-name length in an EXT4 file system". arvimal.blog. Archived from the original on 28 February 2021.
  100. [100]
    "Interviews/EricSandeen". Fedora Project Wiki. 9 June 2008.
  101. [101]
    "Limitations of the FAT32 File System in Windows XP". Microsoft. Archived from the original on 2014-03-30.
  102. [102]
    "GEMDOS Overview".
  103. [103]
    "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2023-03-21.
  104. [104]
    "What are the file and file system size limitations for Red Hat Enterprise Linux?". Red Hat. 2023-03-21.
  105. [105]
    Matthew Dillon. "HAMMER2 Design Document". we can allow filenames up to 1023 bytes long
  106. [106]
    Matthew Dillon (June 21, 2008). "The HAMMER Filesystem" (PDF).
  107. [107]
    "Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits". support.apple.com. July 26, 2016. Archived from the original on 2019-04-08.
  108. [108]
    "Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits". support.apple.com. February 20, 2012.
  109. [109]
    "SFS file system". www.ibm.com. 2015-06-03. Archived from the original on 2022-09-13. Retrieved 2022-09-13.
  110. [110]
    "Joliet Specification". 22 May 1995. Archived from the original on 14 April 2009.
  111. [111]
    Russon, Richard; Fledel, Yuval. "NTFS Documentation" (PDF).
  112. [112]
    "NTFS overview". Microsoft Docs. 2022-05-26. Archived from the original on 2022-05-26. Retrieved 2022-06-05.
  113. [113]
    Steven Sinofsky (January 16, 2012). "Building the next generation file system for Windows: ReFS".
  114. [114]
    Amigo (2015-04-02). "Invalid Characters in File Names". Amigo's Technical Notes. Retrieved 2020-10-20.
  115. [115]
    "Resilient File System (ReFS) overview". Microsoft Docs. Retrieved 2017-11-07.
  116. [116]
    "FAQ". namesys. 15 October 2003. Archived from the original on 19 July 2006.
  117. [117]
    "Maximum Number of UFS Subdirectories". Oracle. Retrieved 2019-02-12.
  118. [118]
    "Frequently Asked Questions for FreeBSD 9.X and 10.X". FreeBSD Documentation Project. Retrieved 2016-03-20. If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KiB (32.76 KB) => 16 Exa * 32 KiB (32.76 KB) => 512 ZettaBytes.
  119. [119]
    "PATH_MAX Is Tricky". Evan Klitzke’s web log.
  120. [120]
    "PATH_MAX simply isn't". Insane Coding. 2007-11-03.
Share this article:

This article uses material from the Wikipedia article Comparison_of_file_systems, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.