Editing List of file systems (section)

== Disk file systems ==
Disk file systems are usually block-oriented. Files in a block-oriented file system are sequences of blocks, often featuring fully random-access read, write, and modify operations.

* [[Advanced Disc Filing System|ADFS]] – [[Acorn Computers Ltd|Acorn]]'s Advanced Disc filing system, successor to [[Disc Filing System|DFS]].
* [[AdvFS]] – Advanced File System, designed by [[Digital Equipment Corporation]] for their Digital UNIX (now [[Tru64 UNIX]]) operating system.
* [[Apple File System|APFS]] – Apple File System is a file system for Apple products.
* [[AtheOS File System|AthFS]] – [[AtheOS]] File System, a [[64-bit computing|64-bit]] [[Journaling file system|journaled]] filesystem now used by [[Syllable Desktop (operating system)|Syllable]]. Also called AFS.
* [[Boot File System|BFS]] – the Boot File System used on System V release 4.0 and UnixWare.
* [[Be File System|BFS]] – the Be File System used on [[BeOS]], occasionally misnamed as BeFS. Open source implementation called OpenBFS is used by the [[Haiku (operating system)|Haiku]] operating system.
* [[VM (operating system)#Shared File System|Byte File System]] (BFS) - file system used by [[z/VM]] for Unix applications
* [[Btrfs]] – is a [[copy-on-write]] file system for [[Linux]] announced by [[Oracle Corporation|Oracle]] in 2007 and published under the [[GNU General Public License]] (GPL).
* [[Veritas Cluster File System|CFS]] – The Cluster File System from Veritas, a Symantec company.  It is the parallel access version of VxFS.
* [[CP/M]] file system — Native filesystem used in the CP/M (Control Program for Microcomputers) operating system which was first released in 1974.
* [[Disc Filing System|DFS]] – [[Acorn Computers Ltd|Acorn]]'s Disc filing system.
* [[Apple DOS|DOS 3.x]] – Original floppy operating system and file system developed for the [[Apple II]].
* [[Extent File System]] (EFS) – an older block filing system under [[IRIX]].
* [[Extended file system|ext]] – Extended file system, designed for [[Linux]] systems.
* [[ext2]] – Second extended file system, designed for [[Linux]] systems.
* [[ext3]] – A [[Journaling file system|journaled]] form of ext2.
* [[ext4]] – A follow-up for [[ext3]] and also a [[Journaling file system|journaled]] filesystem with support for [[extent (file systems)|extents]].
* [[ext3cow]] – A [[versioning file system]] form of ext3.
* [[File Allocation Table|FAT]] – File Allocation Table, initially used on [[DOS]] and [[Microsoft Windows]] and now widely used for portable USB storage and some other devices; [[FAT12]], [[FAT16]] and [[FAT32]] for 12-, [[16-bit|16-]] and [[32-bit]] table depths.
** [[Design of the FAT file system#VFAT|VFAT]] – Optional layer on [[Microsoft Windows]] FAT system to allow long (up to 255 character) filenames instead of only the [[8.3 filename]]s allowed in the plain FAT filesystem.
** [[FATX]] – A modified version of [[Microsoft Windows]] FAT system that is used on the original [[Xbox (console)|Xbox]] console.
* [[Amiga Fast File System|FFS (Amiga)]] – Fast File System, used on [[Amiga]] systems. This FS has evolved over time. Now counts FFS1, FFS Intl, FFS DCache, FFS2.
* [[Berkeley Fast File System|FFS]] – Berkeley Fast File System, used on *[[BSD]] systems
* [[Fossil (file system)|Fossil]] – [[Plan 9 from Bell Labs]] snapshot archival file system.
* [[Files-11]] – [[OpenVMS]] file system; also used on some [[PDP-11]] systems; supports record-oriented files
* [[Flex machine]] file system
* [[HAMMER (file system)|HAMMER]] — clustered [[DragonFly BSD]] filesystem, production-ready since DragonFly 2.2 (2009)<ref name=lwn-hammer-2010>{{cite web
|url=https://lwn.net/Articles/384200/
|title=DragonFly BSD 2.6: towards a free clustering operating system
|author= Koen Vervloesem
|website=[[LWN.net]]
|date=2010-04-21 |access-date=2019-03-07
}}</ref><ref name=hammer_disk.h>{{cite web|url=http://bxr.su/d/sys/vfs/hammer/hammer_disk.h|title=hammer_disk.h|author=Matt Dillon|author-link=Matt Dillon (computer scientist)|website=BSD Cross Reference|publisher=[[DragonFly BSD]]|date=2017-09-23|access-date=2019-03-06}}</ref>
* [[HAMMER2]] — recommended as the default root filesystem in DragonFly since 5.2 release in 2018<ref name=hammer2-release52>{{cite web|url=https://www.dragonflybsd.org/release52/|title=DragonFly BSD 5.2|publisher=[[DragonFly BSD]]|date=2018-06-18|access-date=2019-03-06|quote=We can now recommend H2 as the default root filesystem in non-clustered mode.}}</ref><ref name=hammer2_disk.h>{{cite web|url=http://bxr.su/d/sys/vfs/hammer2/hammer2_disk.h|title=hammer2_disk.h|author=Matt Dillon|author-link=Matt Dillon (computer scientist)|website=BSD Cross Reference|publisher=[[DragonFly BSD]]|date=2018-05-05|access-date=2019-03-06}}</ref><ref name="hammer2_design">{{cite web|url=http://bxr.su/d/sys/vfs/hammer2/DESIGN|title=hammer2/DESIGN|author=Matt Dillon|author-link=Matt Dillon (computer scientist)|date=2018-12-09|website=BSD Cross Reference|publisher=[[DragonFly BSD]]|access-date=2019-03-06}}</ref>
* [[Hierarchical File System (IBM MVS)|HFS]] – Hierarchical File System in IBM's [[MVS]] from [[MVS#MVS/ESA|MVS/ESA OpenEdition]] through [[z/OS]] V2R4; not to be confused with Apple's HFS. IBM stated that [[z/OS]] users should migrate from HFS to [[zFS (z/OS file system)|zFS]], and in z/OS V2R5 dropped support for HFS.
* [[Hierarchical File System (Apple)|HFS]] – Hierarchical File System, in use until HFS+ was introduced on Mac OS 8.1. Also known as Mac OS Standard format.  Successor to Macintosh File System (MFS) & predecessor to HFS+; not to be confused with IBM's HFS provided with [[z/OS]]
* [[HFS Plus|HFS+]] – Updated version of Apple's HFS, Hierarchical File System, supported on Mac OS 8.1 & above, including macOS.  Supports file system journaling, enabling recovery of data after a system crash.  Also referred to as 'Mac OS Extended format or HFS Plus
* [[High Performance File System|HPFS]] – High Performance File System, used on [[OS/2]]
* [[High Throughput File System|HTFS]] – High Throughput Filesystem, used on [[SCO OpenServer]]
* [[ISO 9660]] – Used on [[CD-ROM]] and [[DVD|DVD-ROM]] discs ([[Rock Ridge]] and [[Joliet (file system)|Joliet]] are extensions to this)
* [[IBM Journaled File System 2 (JFS2)|JFS]] – [[IBM]] [[Journaling file system]], provided in [[Linux]], [[OS/2]], and [[AIX operating system|AIX]].  Supports [[extent (file systems)|extents]].
* [[Log-structured File System (BSD)|LFS]] – 4.4BSD implementation of a [[log-structured file system]]
* [[Macintosh File System|MFS]] – Macintosh File System, used on early [[Classic Mac OS]] systems. Succeeded by Hierarchical File System (HFS).
* [[Next3]] – A form of [[ext3]] with snapshots support.<ref name="next3">{{cite web|last=Corbet|first=Jonathan|title=The Next3 filesystem|url=https://lwn.net/Articles/387231/|publisher=LWN}}</ref>
* [[TiVo Media File System|MFS]] – TiVo's Media File System, a proprietary fault tolerant format used on [[TiVo]] hard drives for real time recording from live TV.
* [[Minix file system]] – Used on [[Minix]] systems
* [[NILFS]] – Linux implementation of a [[log-structured file system]]
* [[NTFS]] – (New Technology File System) Used on [[Microsoft]]'s [[Windows NT]]-based operating systems
* [[NeXT]] - [[NeXTstation]] and [[NeXTcube]] file system
* [[NetWare File System]] – The original [[Novell NetWare|NetWare]] 2.x–5.x file system, used optionally by later versions.
* [[Novell Storage Services|NSS]] – Novell Storage Services.  This is a new 64-bit [[journaling file system]] using a balanced tree algorithm.  Used in [[Novell NetWare|NetWare]] versions 5.0-up and recently ported to [[Linux]].
* [[One File System|OneFS]] – One File System. This is a fully journaled, distributed file system used by [[Isilon Systems|Isilon]]. OneFS uses FlexProtect and [[Reed–Solomon error correction|Reed–Solomon]] encodings to support up to four simultaneous disk failures.
* [[Amiga Old File System|OFS]] – Old File System, on Amiga. Good for floppies, but fairly useless on hard drives.
* [[OS-9]] file system
* [[Professional File System|PFS]] – and PFS2, PFS3, etc. Technically interesting file system available for the [[Amiga]], performs very well under a lot of circumstances.
* [[Apple ProDOS|ProDOS]] – Successor to DOS 3.x, for [[Apple II]] computers, including the [[Apple IIGS|IIgs]]
* [[Qnx4fs]] – File system that is used in [[QNX]] version 4 and 6.
* [[ReFS|ReFS (Resilient File System)]] – File system by [[Microsoft]] with a particular focus on data resilience in server environments.
* [[ReiserFS]] – File system that uses [[journaling file system|journaling]]
* [[Reiser4]] – File system that uses [[journaling file system|journaling]], newest version of ReiserFS
* [[Reliance (file system)|Reliance]] – Datalight's transactional file system for high reliability applications
* [[Reliance Nitro]] – Tree-based transactional, [[copy-on-write]] file system developed for high-performance embedded systems, from Datalight (Acquired by [[Tuxera]] in 2019)<ref name=":0">{{Cite web |last=Tuxera |date=2019-06-05 |title=Tuxera acquires mission-critical embedded flash storage leader Datalight |url=https://www.tuxera.com/blog/tuxera-acquires-mission-critical-embedded-flash-storage-leader-datalight/ |access-date=2024-06-28 |website=Tuxera |language=en-US}}</ref>
* [[Remote File System|RFS]] – Native filesystem for [[RTEMS]]<ref name="rfs">{{cite web|title=RTEMS File System|url=http://www.rtems.org/wiki/index.php/RTEMS_File_System|access-date=20 April 2013}}</ref>
* [[SkyFS]] – Developed for [[SkyOS]] to replace BFS as the operating system's main file system. It is based on BFS, but contains many new features.
* [[Smart File System|SFS]] – Smart File System, [[journaling file system]] available for the Amiga platforms.
* [[Soup (Apple)]] – the "file system" for [[Newton (platform)|Apple Newton Platform]], structured as a shallow database
* [[Tux3]] – An experimental versioning file system intended as a replacement for ext3
* [[Universal Disk Format|UDF]] – Packet-based file system for WORM/RW media such as CD-RW and DVD, now supports hard drives and flash memory as well.
* [[Unix File System|UFS]] – Unix File System, used on [[Solaris (operating system)|Solaris]] and older [[BSD]] systems
* [[Unix File System|UFS2]] – Unix File System, used on newer [[BSD]] systems
* [[Vault File System|VaultFS]] – parallel distributed clusterable file system for Linux/Unix by Swiss Vault
* [[Veritas File System|VxFS]]   [[Veritas Software|Veritas]] file system, first commercial [[journaling file system]]{{Citation needed|date=September 2007}}; [[HP-UX]], [[Solaris (operating system)|Solaris]], [[Linux]], [[AIX operating system|AIX]], [[UnixWare]]
*[[Volume Table of Contents|VTOC]] (Volume Table Of Contents) -  Data structure on IBM mainframe [[direct-access storage device]]s (DASD) such as disk drives that provides a way of locating the data sets that reside on the [[DASD]] volume.
* [[XFS]] – Used on [[Silicon Graphics|SGI]] [[IRIX]] and [[Linux]] systems
* [[zFS (z/OS file system)|zFS]] – [[z/OS]] File System; not to be confused with other file systems named zFS or ZFS.
* [[zFS (IBM file system project)|zFS]] - an IBM research project to develop a distributed, decentralized file system; not to be confused with other file systems named zFS or ZFS.
* [[ZFS]]{{snd}} a combined file system and logical volume manager designed by [[Sun Microsystems]]

=== File systems with built-in fault-tolerance ===
These file systems have built-in checksumming and either mirroring or parity for extra redundancy on one or several block devices:
* [[Bcachefs]] – Full data and metadata checksumming,<ref>{{cite web|title=Bcachefs main site|last1=Overstreet|first1=Kent|url=https://bcachefs.org/}}</ref><ref>{{cite web|title=LWN - An update on bcachefs|last1=Edge|first1=Jake|url=https://lwn.net/Articles/755276/}}</ref> [[bcache]] is the bottom half of the filesystem. Included in Linux kernel since 6.7<ref>{{cite web|title=Bcachefs merged in linux 6.7|url=https://www.phoronix.com/news/Bcachefs-Merged-Linux-6.7}}</ref><ref>{{cite web|title=Bcachefs on Patreon|last1=Overstreet|first1=Kent|url=https://www.patreon.com/bcachefs/}}</ref>
* [[Btrfs]] – A file system based on [[B-Tree]]s, initially designed at [[Oracle Corporation]].
* [[HAMMER (file system)|HAMMER]] and [[HAMMER2]] – [[DragonFly BSD]]'s primary filesystems, created by [[Matt Dillon (computer scientist)|Matt Dillon]].<ref name=lwn-hammer-2010/><ref name=hammer_disk.h/><ref name=hammer2_disk.h/><ref name=hammer2_design/>
* [[NOVA_(filesystem)|NOVA]] – The "non-volatile memory accelerated" file system for persistent main memory.
* [[ReFS|ReFS (Resilient File System)]] – A file system by [[Microsoft]] with built-in resiliency features.
* [[Reliance (file system)|Reliance]] – A transactional file system with [[cyclic redundancy check|CRCs]], created by Datalight.
* [[Reliance Nitro]] – A tree-based transactional, [[copy-on-write]] file system with CRCs, developed for high performance and reliability in embedded systems, from Datalight (Acquired by [[Tuxera]] in 2019).<ref name=":0" />
* [[Vault File System|VaultFS]] – dynamically configurable any*Data + any*Parity EC (erasure coding) targets for any file or directory tree with checksum on every chunk
* [[ZFS]] – Has checksums for all data; important metadata is always redundant, additional redundancy levels are user-configurable; [[copy-on-write]] and transactional writing ensure metadata consistency; corrupted data can be automatically repaired if a redundant copy is available. Created by [[Sun Microsystems]] for use on [[Solaris (operating system)|Solaris]] 10 and [[OpenSolaris]], ported to [[FreeBSD]] 7.0, [[NetBSD]] (as of August 2009), [[Linux]] and to [[Filesystem in Userspace|FUSE]] (not to be confused with the two zFSes from [[IBM]])

=== File systems optimized for flash memory, solid state media ===
{{Main article|Flash file system}}

Solid state media, such as [[flash memory]], are similar to disks in their interfaces, but have different problems. At low level, they require special handling such as [[wear leveling]] and different [[error detection and correction]] algorithms. Typically a device such as a [[solid-state drive]] handles such operations internally and therefore a regular file system can be used. However, for certain specialized installations (embedded systems, industrial applications) a file system optimized for plain flash memory is advantageous.

* [[3FS]] – (Fire-Flyer File System) is a File System made by [[DeepSeek]] designed for AI Training and Inference workloads.<ref>{{Citation |title=deepseek-ai/3FS |date=2025-03-04 |url=https://github.com/deepseek-ai/3FS |access-date=2025-03-04 |publisher=DeepSeek}}</ref>
* [[APFS]] – Apple File System is a next-generation file system for Apple products.
* [[CHFS]] – a [[NetBSD]] filesystem for [[embedded system]]s optimised for raw flash media.
* [[exFAT]] – [[Microsoft]] proprietary system intended for flash cards (see also [[XCFiles]], an exFAT implementation for [[Wind River Systems|Wind River]] [[VxWorks]] and other embedded operating systems).
* [[ExtremeFFS]] – internal filesystem for SSDs.
* [[F2FS]] – Flash-Friendly File System. An open source Linux file system introduced by [[Samsung]] in 2012.<ref>{{cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=MTE5OTY |title=Samsung Introduces New Linux File-System: F2FS |publisher=phoronix.com |author=Michael Larabel |date=2011-10-05 |access-date=2012-12-07}}</ref>
* [[Flash memory#Flash file systems|FFS2]] (presumably preceded by FFS1), one of the earliest flash file systems.  Developed and patented by [[Microsoft]] in the early 1990s.<ref>{{cite web|url=http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PTXT&s1=5392427.PN.&OS=PN/5392427&RS=PN/5392427 |title=United States Patent: 5392427 |publisher=Patft.uspto.gov |access-date=2012-06-15}}</ref>
* [[JFFS]] – original log structured Linux file system for NOR flash media.
* [[JFFS2]] – successor of JFFS, for [[NAND flash#NAND flash|NAND]] and [[NOR flash]].
* [[LSFS]] – a [[Log-structured file system]] with writable snapshots and inline data deduplication created by [[StarWind Software]]. Uses DRAM and flash to cache spinning disks. 
* [[LogFS]] – intended to replace JFFS2, better scalability. No longer under active development.<ref>{{cite web |url=https://lkml.org/lkml/2016/9/11/58|title=Linux Kernel Mailing List: logfs: remove from tree|access-date=2017-03-31}}</ref>
* [[NILFS]] – a log-structured file system for Linux with continuous snapshots.
* [[Non-Volatile File System]] – the system for [[flash memory]] introduced by [[Palm, Inc.]]
* [[NOVA (filesystem)|NOVA]] – the "non-volatile memory accelerated" file system for persistent main memory.
* [[One File System|OneFS]] – a filesystem utilized by [[Isilon Systems|Isilon]]. It supports selective placement of meta-data directly onto flash SSD.
* [https://www.tuxera.com/products/reliance-velocity-flash-file-system/ Reliance Velocity] - a proprietary flash file system by [[Tuxera]] with high resilience (fail-safe technology) and built-in data integrity. This file system is best suited for embedded applications requiring heavy data workloads over long-term operations. Reliance Velocity can used for all block based media like [[MultiMediaCard|eMMC]], [[Universal Flash Storage|UFS]], eSD, [[SD card]], [[CompactFlash|CF card]], and [[Solid-state drive|SSD]]. It is compatible for [[Linux]], [[Android (operating system)|Android]] and [[QNX]] with portability to other embedded operating systems.
* [https://www.tuxera.com/products/reliance-edge/ Reliance Edge] - a proprietary file system by [[Tuxera]] for resource-constrained embedded systems. It has built-in [[data integrity]] with [[copy-on-write]] transactional technology and [[Deterministic algorithm|deterministic]] operations. This file system can be used for block based media and is configurable for Small [[POSIX]], Full POSIX and can be ported to many [[Real-time operating system|RTOS]] environments. Tuxera has a certified version of this file system called [https://www.tuxera.com/products/reliance-assure/ Reliance Assure]. The source code of Reliance Assure is complaint to [[MISRA C]] and developed following the [[Automotive SPICE|ASPICE]] framework.
* [[Segger Microcontroller Systems]] emFile – filesystem for deeply embedded applications which supports both NAND and NOR flash.  Wear leveling, fast read and write, and very low RAM usage.
* [[SPIFFS]] – SPI Flash File System, a wear-leveling filesystem intended for small NOR flash devices.
* [[Transaction-Safe FAT File System|TFAT]] – a transactional version of the FAT filesystem.
* [[TrueFFS]] – internal file system for SSDs, implementing error correction, bad block re-mapping and wear-leveling.
* [[UBIFS]] – successor of JFFS2, optimized to utilize [[NAND flash#NAND flash|NAND]] and [[NOR flash]].
* [[Write Anywhere File Layout]] (WAFL) – an internal file system utilized by [[NetApp]] within their DataONTAP OS, originally optimized to use non-volatile DRAM. WAFL uses [[Non-standard RAID levels#RAID-DP|RAID-DP]] to protect against multiple disk failures and NVRAM for transaction log replays.
* [[YAFFS]] – a log-structured file system designed for NAND flash, but also used with NOR flash.
*[https://github.com/ARMmbed/littlefs LittleFS] – a little fail-safe filesystem designed for microcontrollers.
* [[JesFS]] – Jo's embedded serial FileSystem.<ref>{{cite web |url=https://github.com/joembedded/JesFs|title=Jo's Embedded Serial File System (for Standard Serial NOR-Flash)|website=[[GitHub]]|date=2019-06-18}}</ref> A very small footprint and robust filesystem, designed for very small microcontroller (16/32 bit). Open Source and licensed under GPL v3.

=== Record-oriented file systems ===
In [[Record-oriented filesystem|record-oriented file systems]] files are stored as a collection of [[record (computer science)|records]]. They are typically associated with [[Mainframe computer|mainframe]] and [[minicomputer]] operating systems. Programs read and write whole records, rather than bytes or arbitrary byte ranges, and can seek to a record boundary but not within records. The more sophisticated record-oriented file systems have more in common with simple [[database]]s than with other file systems.

* [[CMS file system]] – The native file system of the [[Conversational Monitor System]] component of [[VM/370]]
* [[Files-11]] – early versions were record-oriented; support for "streams" was added later
* [[Michigan Terminal System]] (MTS) – provides "line files" where record lengths and line numbers are associated as metadata with each record in the file, lines can be added, replaced, updated with the same or different length records, and deleted anywhere in the file without the need to read and rewrite the entire file.<ref>{{cite journal|title=A file system for a general-purpose time-sharing environment|first=G. C.|last=Pirkola|journal=Proceedings of the IEEE|date=June 1975|volume=63|issue=6|pages=918–924|issn=0018-9219|doi=10.1109/PROC.1975.9856|s2cid=12982770}}</ref>
* [[OS4000]] for GEC's OS4000 operating system, on the [[GEC 4000 series]] minicomputers
* A [[FAT12]] and [[FAT16]] (and [[FAT32]]) extension to support database-like file types ''random file'', ''direct file'', ''keyed file'' and ''sequential file'' in Digital Research [[FlexOS]], IBM [[4680 OS]] and Toshiba [[4690 OS]].<ref name="IBM_4690_Programming_Guide">IBM. ''4690 OS Programming Guide Version 5.2'', IBM document SC30-4137-01, 2007-12-06 ([https://public.dhe.ibm.com/software/retail/pubs/sw/opsys/4690/ver5r2/bsi1_PG_mst.pdf]).</ref> The record size is stored on a file-by-file basis in [[Design of the FAT file system#DIR OFS 10h|special entries]] in the directory table.<ref name="Caldera_1997_DOSSRC">Caldera (1997). ''Caldera OpenDOS Machine Readable Source Kit 7.01''. The FDOS.EQU file in the machine readable source kit has equates for the corresponding directory entries.</ref>
* Sequential access methods for IBM's [[z/OS]] and [[z/VSE]] mainframe operating systems: [[Basic Sequential Access Method]] (BSAM), [[Basic Partitioned Access Method]] (BPAM) and [[Queued Sequential Access Method]] (QSAM); see [[Access methods]] and [[Data set (IBM mainframe)]] for more examples
* [[Pick Operating System]] – A record-oriented filesystem and database that uses hash-coding to store data.
* [[VM (operating system)#Shared File System|Shared File System]] (SFS) for IBM's [[VM (operating system)|VM]]
* [[Virtual Storage Access Method]] (VSAM){{snd}} for IBM's [[z/OS]] and [[z/VSE]] mainframe operating systems

=== {{Anchor|SHARED}}Shared-disk file systems ===
Shared-disk file systems (also called ''shared-storage file systems'', [[SAN file system]], [[Clustered file system]] or even ''cluster file systems'') are primarily used in a [[storage area network]] where all nodes directly access the [[Block (data storage)|block storage]] where the file system is located. This makes it possible for nodes to fail without affecting access to the file system from the other nodes. Shared-disk file systems are normally used in a [[high-availability cluster]] together with storage on hardware [[RAID]]. Shared-disk file systems normally do not scale over 64 or 128 nodes.

Shared-disk file systems may be [[symmetric]] where [[metadata]] is distributed among the nodes or [[asymmetry|asymmetric]] with centralized [[metadata]] servers.

* [[CXFS]] (Clustered XFS) from [[Silicon Graphics]] (SGI). Available for Linux, Mac, Windows, Solaris, AIX and IRIX. Asymmetric.
* [[Dell Fluid File System]] (formerly ExaFS) [[proprietary software]] sold by [[Dell]].  Shared-disk system sold as an appliance providing distributed file systems to clients. Running on Intel based hardware serving NFS v2/v3, SMB/CIFS and AFP to [[Microsoft Windows|Windows]], [[macOS]], [[Linux]] and other [[UNIX]] clients.
* [[Blue Whale Clustered file system]] (BWFS) from [[Tianjin Zhongke Blue Whale Information Technologies Co., Ltd.|Zhongke Blue Whale]]. Asymmetric. Available for [[Microsoft Windows]], [[Linux]], and [[macOS]].
* [[DataPlow SAN File System|SAN File System]] (SFS) from DataPlow. Available for Windows, Linux, Solaris, and macOS. Symmetric and Asymmetric.
* [[EMC Celerra HighRoad]] from [[EMC Corporation|EMC]]. Available for Linux, AIX, HP-UX, IRIX, Solaris and Windows. Asymmetric.{{Citation needed|date=May 2010}}
* [[Files-11]] on [[VMScluster]]s, released by [[Digital Equipment Corporation|DEC]] in 1983, now from [[Hewlett-Packard|HP]]. Symmetric.
* [[GFS2]] (''Global File System'') from [[Red Hat]]. Available for Linux under [[GNU General Public License|GPL]]. Symmetric ([[GDLM]]) or Asymmetric ([[GULM]]).
* [[IBM General Parallel File System]] (GPFS) Windows, Linux, AIX . Parallel
* [[Nasan]] Clustered File System from [[DataPlow]]. Available for Linux and Solaris. Asymmetric.
* [[Oracle ACFS]] from [[Oracle Corporation]]. Available for Linux ([[RHEL|Red Hat Enterprise Linux]] 5 and [[Oracle Enterprise Linux]] 5 only). Symmetric.
* [[OCFS2]] (''Oracle Cluster File System'') from [[Oracle Corporation]]. Available for Linux under [[GNU General Public License|GPL]]. Symmetric.
* [[QFS]] from [[Sun Microsystems]]. Available for Linux (client only) and Solaris (metadata server and client). Asymmetric.
* [[ScoutFS]] from [[Versity]]. Available for Linux under the [[GNU General Public License|GPL]]. Symmetric.
* [[StorNext File System]] from [[Quantum Corporation|Quantum]]. Asymmetric. Available for [[AIX operating system|AIX]], [[HP-UX]], [[IRIX]], [[Linux]], [[macOS]], [[Solaris (operating system)|Solaris]] and [[Microsoft Windows|Windows]]. Interoperable with [[Xsan]]. Formerly known as CVFS.
* [[Veritas Storage Foundation]] from [[NortonLifeLock|Symantec]]. Available for AIX, HP-UX, Linux and Solaris. Asymmetric.
* [[Xsan]] from [[Apple Inc.]] Available for macOS. Asymmetric. Interoperable with [[StorNext File System]].
* [[VMware VMFS|VMFS]] from [[VMware]]/[[EMC Corporation]]. Available for [[VMware ESX Server]]. Symmetric.