Editing List of file systems (section)

=== {{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