Editing List of file systems (section)

== Distributed file systems ==
{{See also|Comparison of distributed file systems}}

[[Distributed file system]]s are also called network file systems. Many implementations have been made, they are location dependent and they have [[access control lists]] (ACLs), unless otherwise stated below.

* [[9P (protocol)|9P]], the [[Plan 9 from Bell Labs]] and [[Inferno (operating system)|Inferno]] distributed file system protocol. One implementation is [[v9fs]]. No ACLs.
* [[Amazon S3]]
* [[Andrew File System]] (AFS) is scalable and location independent, has a heavy client [[cache (computing)|cache]] and uses [[Kerberos (protocol)|Kerberos]] for authentication. Implementations include the original from [[IBM]] (earlier [[Transarc]]), Arla and [[OpenAFS]].
* [[Avere Systems]] has AvereOS that creates a [[Network-attached storage|NAS]] protocol file system in [[object storage]].
* [[DCE Distributed File System]] ([[distributed computing environment|DCE]]/DFS) from [[IBM]] (earlier [[Transarc]]) is similar to AFS and focus on full [[POSIX]] file system semantics and [[high availability]]. Available for [[AIX operating system|AIX]] and [[Solaris (operating system)|Solaris]] under a [[proprietary software]] license.
* [[File Access Listener]] (FAL) is an implementation of the [[Data Access Protocol]] (DAP) which is part of the [[DECnet]] suite of [[network protocols]] created by [[Digital Equipment Corporation]].
* [[MagmaFS|Magma]], developed by Tx0.
* [[MapR FS]] is a distributed high-performance file system that exhibits file, table and messaging APIs.
* [[Microsoft Office Groove]] shared workspace, used for DoHyki
* [[NetWare Core Protocol]] (NCP) from [[Novell]] is used in networks based on [[Novell NetWare|NetWare]].
* [[Network File System (protocol)|Network File System]] (NFS) originally from [[Sun Microsystems]] is the standard in UNIX-based networks. NFS may use [[Kerberos (protocol)|Kerberos]] authentication and a client [[cache (computing)|cache]].
* [[OS4000]] Linked-OS provides distributed filesystem across OS4000 systems.
* [[Self-certifying File System]] (SFS), a global network file system designed to securely allow access to file systems across separate administrative domains.
* [[Server Message Block]] (SMB) originally from [[IBM]] (but the most common version is modified heavily by [[Microsoft]]) is the standard in Windows-based networks. SMB is also known as ''Common Internet File System (CIFS)''. SMB may use [[Kerberos (protocol)|Kerberos]] authentication.
* [[Vault File System|VaultFS]] – parallel distributed clusterable file system for Linux/Unix by Swiss Vault

=== {{Anchor|DISTRIBUTED-FAULT-TOLERANT}}Distributed fault-tolerant file systems ===
Distributed [[fault-tolerant]] replication of data between nodes (between servers or servers/clients) for [[high availability]] and [[offline]] (disconnected) operation.
* [[Coda (file system)|Coda]] from [[Carnegie Mellon University]] focuses on bandwidth-adaptive operation (including disconnected operation) using a client-side cache for mobile computing. It is a descendant of AFS-2. It is available for [[Linux]] under the [[GNU General Public License|GPL]].
* [[Distributed File System (Microsoft)|Distributed File System]] (Dfs) from [[Microsoft]] focuses on location transparency and [[high availability]]. Available for [[Microsoft Windows|Windows]] under a [[proprietary software]] license.
* [[HAMMER (file system)|HAMMER]] and [[HAMMER2]] – [[DragonFly BSD]]'s filesystems for clustered storage, created by [[Matt Dillon (computer scientist)|Matt Dillon]].<ref name=lwn-hammer-2010/><ref name=hammer2_design/>
* [[InterMezzo (file system)|InterMezzo]] from [[Cluster File Systems]] uses synchronization over [[HTTP]]. Available for [[Linux]] under [[GNU General Public License|GPL]] but no longer in development since the developers are working on [[Lustre (file system)|Lustre]].
* [[LizardFS]] a networking, distributed file system based on MooseFS<ref>[https://lizardfs.org LizardFS.org]</ref>
* [[Moose File System]] (MooseFS) is a networking, distributed file system. It spreads data over several physical locations (servers), which are visible to a user as one resource. Works on Linux, FreeBSD, NetBSD, OpenSolaris and macOS. Master server and chunkservers can also run on Solaris and Windows with Cygwin.
* [[Scality]] is a distributed fault-tolerant filesystem.
* [[Tahoe-LAFS]] is an open source secure, decentralized, fault-tolerant filesystem utilizing encryption as the basis for a least-authority replicated design.
* A [[FAT12]] and [[FAT16]] (and [[FAT32]]) extension to support automatic file distribution across nodes with extra attributes like ''local'', ''mirror on update'', ''mirror on close'', ''compound on update'', ''compound on close'' in IBM [[4680 OS]] and Toshiba [[4690 OS]]. The distribution attributes are stored on a file-by-file basis in [[Design of the FAT file system#DIR|special entries]] in the directory table.<ref name="IBM_4690_OS_Distribution_Attributes_1">IBM (2003). ''Information about 4690&nbsp;OS unique file distribution attributes'', IBM document R1001487, 2003-07-30. ({{cite web |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1001487 |title=IBM Information about 4690 OS unique file distribution attributes - United States |access-date=2014-05-20 |url-status=dead |archive-url=https://web.archive.org/web/20140521070339/http://www-01.ibm.com/support/docview.wss?uid=pos1R1001487 |archive-date=2014-05-21 }}): "[...] file types are stored in the "Reserved bits" portion of the PC-DOS file directory structure [...] only 4690 respects and preserves these attributes. Various non-4690 operating systems take different actions if these bits are turned on [...] when copying from a diskette created on a 4690 system. [...] PC-DOS and Windows 2000 Professional will copy the file without error and zero the bits. OS/2 [...] 1.2 [...] will refuse to copy the file unless [...] first run CHKDSK /F on the file. After [...] CHKDSK, it will copy the file and zero the bits. [...] when [...] copy [...] back to the 4690 system, [...] file will copy as a local file."</ref><ref name="IBM_4690_OS_Distribution_Attributes_2">IBM. ''4690 save and restore file distribution attributes''. IBM document R1000622, 2010-08-31 ({{cite web |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1000622 |title=IBM 4690 save and restore file distribution attributes - United States |access-date=2014-05-20 |url-status=dead |archive-url=https://web.archive.org/web/20140521070536/http://www-01.ibm.com/support/docview.wss?uid=pos1R1000622 |archive-date=2014-05-21 }}).</ref>
* [[OpenHarmony]] Distributed File System (HMDFS) used for [[Huawei]]'s [[HarmonyOS]] with [[HarmonyOS NEXT]] base and [[OpenHarmony]]-based operating systems, alongside [[EulerOS|openEuler]] server OS that is a cross-device file access where devices can read and edit files on transparently when the two devices are connected to the same network with [[Access token manager]]. Multiple embedded devices connected to the network can automatically synchronise file data with the edge server.<ref>{{Cite web |title=distributed-fs-overview |url=https://docs.openeuler.org/en/docs/22.03_LTS_SP3/docs/Distributed/distributed-fs-overview.html |access-date=2024-05-23 |website=docs.openeuler.org}}</ref>
* [[Vault File System|VaultFS]] – parallel distributed clusterable filesystem using dynamically configurable any*Data + any*Parity EC (erasure coding) and dynamically tolerates bitrot, media & server failures

=== Distributed parallel file systems ===
Distributed [[Parallel computing|parallel]] file systems stripe data over multiple servers for high performance. They are normally used in [[high-performance computing|high-performance computing (HPC)]].

Some of the distributed parallel file systems use an [[object storage device]] (OSD) (in Lustre called OST) for chunks of data together with centralized [[metadata]] servers.

*[[BeeGFS]] is a hardware-independent parallel file system that features distributed metadata and striping of files across multiple targets, such as NVMe devices or logical volumes.
*[[Lustre (file system)|Lustre]] is an [[Open-source software|open-source]] high-performance distributed parallel file system for Linux, used on many of the largest computers in the world. 
*[[Parallel Virtual File System]] (PVFS, PVFS2, [[OrangeFS]]).  Developed to store virtual system images, with a focus on non-shared writing optimizations. Available for [[Linux]] under [[GNU General Public License|GPL]].
* [[Vault File System|VaultFS]] – configurable any*Data + any*Parity EC (erasure coding) chunks are widely distributed on D+P disks across the cluster

=== {{Anchor|DISTRIBUTED-PARALLEL-FAULT-TOLERANT}}Distributed parallel fault-tolerant file systems ===
Distributed file systems, which also are [[Parallel computing|parallel]] and [[fault tolerant]], stripe and replicate data over multiple servers for high performance and to maintain [[data integrity]]. Even if a server fails no data is lost. The file systems are used in both [[high-performance computing|high-performance computing (HPC)]] and [[high-availability cluster]]s.

All file systems listed here focus on [[high availability]], [[scalability]] and high performance unless otherwise stated below.
{| class="wikitable sortable"
! Name
! By
! License
! OS
! class=unsortable|Description
|-
| [[Alluxio]]
| [[UC Berkeley]], [[Alluxio]]
| [[Apache License 2.0|Apache License]]
| [[Cross-platform]]
| An open-source virtual distributed file system (VDFS).
|-
| [[BeeGFS]] (formerly FhGFS)
| [[Fraunhofer Society]]
| GNU [[GPL v2]] for client, other components are [[Proprietary software|proprietary]]
| [[Linux]]
| A free to use file system with optional professional support, designed for easy usage and high performance, used on some of the fastest [[computer cluster]]s in the world. BeeGFS allows replication of storage volumes with automatic failover and self-healing.
|-
| [[Ceph (software)#File system storage|CephFS]]
| [[Inktank Storage]], a company acquired by [[Red Hat]] <!--which was later acquired by IBM-->
| GNU [[LGPL]]
| [[Linux kernel]], [[FreeBSD]] via [[Filesystem in Userspace|FUSE]]<ref>{{cite web |title=net/ceph14: Ceph delivers object, block, and file storage in a unified system |url=https://www.freshports.org/net/ceph14/ |website=FreshPorts |access-date=2021-07-11}}</ref>
| A massively scalable object store. CephFS was merged into the Linux kernel in 2010. Ceph's foundation is the [[reliable autonomic distributed object store]] (RADOS), which provides object storage via programmatic interface and S3 or Swift REST APIs, block storage to QEMU/KVM/Linux hosts, and POSIX filesystem storage which can be mounted by Linux kernel and FUSE clients.
|-
| [[Chiron FS]]
| 
| GNU [[GPL v3]]
| Linux
| A [[Filesystem in Userspace|FUSE]]-based, transparent replication file system, layering on an existing file system and implementing at the file system level what [[RAID]] 1 does at the device level. A notably convenient consequence is the possibility of picking single target directories, without the need of replicating entire partitions. (The project has no visible activity after 2008; a status request in Oct. 2009 in the chironfs-forum is unanswered.)
|-
| [[CloudStore]]
| [[Kosmix]]
| [[Apache License 2.0|Apache License]]
|
| [[Google File System]] workalike.  Replaced by [[Quantcast File System (QFS)]]
|-
| [[dCache]]
| [[DESY]] and others
| [[Proprietary software|Proprietary]] (free for non-commercial usage)<ref>{{cite web| url = https://dcache.org/old/manuals/dCacheSoftwareLicence.html |title = dCache Software License}}</ref>
| Linux
| A write once filesystem, accessible via various protocols.
|-
| [[General Parallel File System]] (GPFS)
| [[IBM]]
| [[Proprietary software|Proprietary]]
| Linux, Windows and AIX
| A [[POSIX]]-compliant, high-performance, [[Parallel File System|parallel filesystem]]. Support synchronous [[replication (computer science)|replication]] between attached block storage, and asynchronous replication to remote filesystems. Also support erasure coding on dual homed SAS attached storage, and distributed over multiple storage nodes.
|-
| [[Gfarm file system]]
| [http://oss-tsukuba.org/en/ NPO Tsukuba OSS Technical Support Center]
| [[X11 License]]
| [[Linux]], [[macOS]], [[FreeBSD]], [[NetBSD]] and [[Solaris (operating system)|Solaris]]
| Uses [[PostgreSQL]] for metadata and [[FUSE (Linux)|FUSE]] for mounting.
|-
| [[GlusterFS]]
| Gluster, a company acquired by Red Hat
| GNU [[GPL v3]]
| <!--OS--> [[Linux]], [[NetBSD]], [[FreeBSD]], [[OpenSolaris]]
| A general purpose distributed file system for scalable storage. It aggregates various storage bricks over Infiniband [[remote direct memory access|RDMA]] or TCP/IP interconnect into one large parallel network file system. [[GlusterFS]] is the main component in Red Hat Storage Server.
|-
| [[Google File System]] (GFS)
| [[Google]]
| Internal software
| 
| Focus on [[fault tolerance]], high [[throughput]] and [[scalability]].
|-
| [[Hadoop Distributed File System]]
| [[Apache Software Foundation]]
| [[Apache License 2.0|Apache License]]
| Cross-platform
| Open source GoogleFS clone.
|-
| [[IBRIX Fusion]]
| [[IBRIX]]
| [[Proprietary software|Proprietary]]
|
|
|-
| [https://github.com/juicedata/juicefs JuiceFS]
| Juicedata
| [[Apache License 2.0|Apache License]]
| Cross-platform
| An open-source [[POSIX]]-compliant file system built on top of [[Redis]] and [[object storage]] (e.g. [[Amazon S3]]), designed and optimized for cloud native environment.
|-
| [[LizardFS]]
| Skytechnology
| GNU [[GPL v3]]
| Cross-platform
| An open source, highly available POSIX-compliant file system that supports Windows clients. 
|-
| [[Lustre (file system)|Lustre]]
| Originally developed by [[Cluster File Systems]] and currently supported by OpenSFS
| GNU [[GPL v2]] & [[LGPL]]
| [[Linux]]
| A [[POSIX]]-compliant, high-performance filesystem used on a majority of systems in the [[Top-500]] list of [[High Performance Computing|HPC]] systems. Lustre has [[high availability]] via storage [[failover]].
|-
| [[MapR FS]]
| [[MapR]]
| [[Proprietary software|Proprietary]]
| Linux
| Highly scalable, POSIX compliant, fault tolerant, read/write filesystem with a distributed, fault tolerant metadata service. It provides an HDFS and NFS interface to clients as well as a noSQL table interface and [[Apache Kafka]] compatible messaging system.
|-
| [[MooseFS]]
| [[Core Technology]]
| GNU [[GPL v2]] and [[proprietary software|proprietary]]<ref>{{Cite web | url=https://moosefs.com/license-pro |title = MooseFS}}</ref>
| [[Cross-platform]] ([[Linux]], [[NetBSD]], [[FreeBSD]], [[macOS]], [[OpenSolaris]])
| A fault tolerant, highly available and high performance scale-out network distributed file system. It spreads data over several physical commodity x86 servers, which are visible to the user as one namespace. For standard file operations MooseFS acts like any other Unix-like file systems.
|-
| [[ObjectiveFS]]
| Objective Security Corporation
| [[Proprietary software|Proprietary]]
| [[Linux]], [[macOS]]
| POSIX-compliant shared distributed filesystem. Uses object store as a backend. Runs on AWS S3, GCS and object store devices.
|-
| [[OneFS distributed file system]]
| [[Isilon]]
| [[Proprietary software|Proprietary]]<ref>{{cite web| url = http://doc.isilon.com/onefs/8.1.0/elms_esrs/01-ifs-c-elms-esrs-container-topic.htm |title = OneFS 8.1 eLicensing and remote support changes}}</ref>
| [[FreeBSD]]
| BSD-based OS on dedicated Intel based hardware, serving NFS v3 and SMB/CIFS to [[Microsoft Windows|Windows]], [[macOS]], [[Linux]] and other [[UNIX]] clients under a [[proprietary software]].
|-
| [[OpenIO#Product|OIO-FS]]
| [[OpenIO]]
| [[Proprietary software|Proprietary]]
| [[Linux]]
| OIO-FS provides file-oriented access to [[OpenIO|OpenIO SDS]] [[object storage]] backend. It is based on [[FUSE (filesystem)|FUSE]] technology and presents a [[POSIX]] file system to users. This access can be used locally, or over a network using [[Network File System|NFS]] or [[Server Message Block|SMB]].<ref>{{Cite web|url=https://docs.openio.io/18.10/source/arch-design/fs_overview.html|title=Features of OIO-FS — OpenIO SDS 18.10 Object Storage documentation|website=docs.openio.io|access-date=2018-12-20}}</ref>
|-
| [https://www.panasas.com/panfs-architecture/panfs/ PanFS]
| [[Panasas]]
| [[Proprietary software|Proprietary]]
| [[Linux]], [[macOS]], [[FreeBSD]]
| A [[POSIX]]-compliant, high-performance, [[Parallel File System|parallel filesystem]] used by [[High Performance Computing|HPC]] clusters. It uses [[erasure code|erasure coding]] and snapshots for data protection, is based upon a [[Scale out|scale-out]] [[Object storage|object store]], and is focused on transparent failure recovery and ease of use.
|-
|[https://www.quobyte.com/editions-features/ Quobyte DCFS]
|[https://www.quobyte.com/ Quobyte]
|[[Proprietary software|Proprietary]]
|[[Linux]], [[macOS]], [[FreeBSD]]
|A fault-tolerant, [[Parallel File System|parallel]] [[POSIX]] file system, with block (VMs) and object (S3) interfaces, and advanced enterprise features like [[Multitenancy|multi-tenancy]], strong authentication, encryption. [[Split-brain (computing)|Split-brain]] safe fault-tolerance is achieved through [[Paxos (computer science)|Paxos]]-based [[leader election]] and [[Erasure code|erasure coding]].
|-
| [[RozoFS]]
| Rozo Systems
| GNU [[GPL v2]]
| [[Linux]]
| A [[POSIX]] [[distributed file system|DFS]] focused on [[fault-tolerance]] and high-performance, based on the [[Mojette Transform|Mojette]] [[erasure code]] to reduce significantly the amount of redundancy (compared to plain [[Replication (computing)|replication]]).
|-
| [[Scality]]
| Scality ring
| [[Proprietary software|Proprietary]]
| [[Linux]]
| A POSIX file system{{Citation needed|date=November 2017}} focused on high availability and performance. Also provides S3/REST/NFS interfaces.
|-
| [[Tahoe-LAFS]]
| Tahoe-LAFS Software Foundation
| GNU [[GPL v2]]+ and other<ref>{{cite web|url=https://tahoe-lafs.org/trac/tahoe-lafs/browser/git/docs/about.rst |title=about.rst in trunk/docs – tahoe-lafs |publisher=Tahoe-lafs.org |access-date=2014-02-09}}</ref>
| [[Linux]], [[Microsoft Windows|Windows]], [[macOS]]
| A secure, decentralized, fault-tolerant, [[peer-to-peer]] [[distributed data store]] and [[distributed file system]].
|-
| [[VaultFS]]
| Swiss Vault
| [[Proprietary software|Proprietary]]
| [[Linux]], [[Unix]]
| [[Peer-to-Peer]] dynamically configurable EC (any*Data + any*Parity) bitrot & HW fault-tolerant POSIX/S3 [[distributed file system]] using intermixable CMR & SMR [[shingled magnetic recording]] disks.
|-
| [[XtreemFS]]
| Contrail E.U. project, the German MoSGrid project and the German project "First We Take Berlin"
| [[BSD 3-Clause]]<ref>{{cite web| url = http://www.xtreemfs.org/license.php |title = XtreemFS - License}}</ref>
| [[Linux]], [[Solaris (operating system)|Solaris]], [[macOS]], Windows
| A [[cross-platform]] file system for wide area networks. It replicates the data for fault tolerance and caches metadata and data to improve performance over high-latency links. [[Transport Layer Security|SSL]] and [[X.509]] certificates support makes XtreemFS usable over public networks. It also supports [[striping]] for usage in a [[Cluster (computing)|cluster]].
|}

In development:

* [[zFS (IBM file system project)|zFS]] from [[IBM]] (not to be confused with [[ZFS]] from [[Sun Microsystems]] or the zFS file system provided with IBM's [[z/OS]] operating system) focus on [[cooperative cache]] and [[distributed transactions]] and uses [[object storage device]]s. Under development and not freely available.
* [[HAMMER (file system)|HAMMER]]/ANVIL by [[Matt Dillon (computer scientist)|Matt Dillon]]
* [[PNFS]] (Parallel NFS) – Clients available for [[Linux]] and [[OpenSolaris]] and back-ends from [[NetApp]], [[Panasas]], [[EMC Corporation|EMC]] [[Highroad]] and [[IBM]] [[GPFS]]
* [[CRFS|Coherent Remote File System]] (CRFS) – requires [[Btrfs]]
* [[Elliptics|Parallel Optimized Host Message Exchange Layered File System]] (POHMELFS) and Distributed STorage (DST). POSIX compliant, added to Linux kernel 2.6.30

=== Peer-to-peer file systems ===
Some of these may be called [[cooperative storage cloud]].

* [[IBM Cloud Object Storage]] uses Cauchy [[Reed–Solomon error correction|Reed–Solomon]] [[information dispersal algorithms]] to separate data into unrecognizable slices and distribute them, via secure Internet connections, to multiple storage locations.
* [[Scality]] is a distributed filesystem using the [[Chord (peer-to-peer)|Chord]] peer-to-peer protocol.
* [[IPFS]] InterPlanetary File System is p2p, worldwide distributed content-addressable, file-system.
* [[Vault File System|VaultFS]] – fully peer-to-peer with distributed data & metadata, without separate Master or Failover nodes