Movatterモバイル変換

[0]ホーム
URL:

Jump to content
WikipediaThe Free Encyclopedia
Search

List of file systems

From Wikipedia, the free encyclopedia

The following lists identify, characterize, and link to more thorough information onfile systems.Many olderoperating systems support only their one "native" file system, which does not bear any name apart from the name of the operating system itself.

Disk file systems

[edit]

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.

File systems with built-in fault-tolerance

[edit]

These file systems have built-in checksumming and either mirroring or parity for extra redundancy on one or several block devices:

File systems optimized for flash memory, solid state media

[edit]
Main article:Flash file system

Solid state media, such asflash memory, are similar to disks in their interfaces, but have different problems. At low level, they require special handling such aswear leveling and differenterror detection and correction algorithms. Typically a device such as asolid-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 byDeepSeek designed for AI Training and Inference workloads.[13]
  • APFS – Apple File System is a next-generation file system for Apple products.
  • CHFS – aNetBSD filesystem forembedded systems optimised for raw flash media.
  • exFAT –Microsoft proprietary system intended for flash cards (see alsoXCFiles, an exFAT implementation forWind RiverVxWorks and other embedded operating systems).
  • ExtremeFFS – internal filesystem for SSDs.
  • F2FS – Flash-Friendly File System. An open source Linux file system introduced bySamsung in 2012.[14]
  • FFS2 (presumably preceded by FFS1), one of the earliest flash file systems. Developed and patented byMicrosoft in the early 1990s.[15]
  • JFFS – original log structured Linux file system for NOR flash media.
  • JFFS2 – successor of JFFS, forNAND andNOR flash.
  • LSFS – aLog-structured file system with writable snapshots and inline data deduplication created byStarWind Software. Uses DRAM and flash to cache spinning disks.
  • LogFS – intended to replace JFFS2, better scalability. No longer under active development.[16]
  • NILFS – a log-structured file system for Linux with continuous snapshots.
  • Non-Volatile File System – the system forflash memory introduced byPalm, Inc.
  • NOVA – the "non-volatile memory accelerated" file system for persistent main memory.
  • OneFS – a filesystem utilized byIsilon. It supports selective placement of meta-data directly onto flash SSD.
  • Reliance Velocity - a proprietary flash file system byTuxera 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 likeeMMC,UFS, eSD,SD card,CF card, andSSD. It is compatible forLinux,Android andQNX with portability to other embedded operating systems.
  • Reliance Edge - a proprietary file system byTuxera for resource-constrained embedded systems. It has built-indata integrity withcopy-on-write transactional technology anddeterministic operations. This file system can be used for block based media and is configurable for SmallPOSIX, Full POSIX and can be ported to manyRTOS environments. Tuxera has a certified version of this file system calledReliance Assure. The source code of Reliance Assure is complaint toMISRA C and developed following theASPICE 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.
  • 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 utilizeNAND andNOR flash.
  • Write Anywhere File Layout (WAFL) – an internal file system utilized byNetApp within their DataONTAP OS, originally optimized to use non-volatile DRAM. WAFL usesRAID-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.
  • LittleFS – a little fail-safe filesystem designed for microcontrollers.
  • JesFS – Jo's embedded serial FileSystem.[17] 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

[edit]

Inrecord-oriented file systems files are stored as a collection ofrecords. They are typically associated withmainframe andminicomputer 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 simpledatabases than with other file systems.

Shared-disk file systems

[edit]

Shared-disk file systems (also calledshared-storage file systems,SAN file system,Clustered file system or evencluster file systems) are primarily used in astorage area network where all nodes directly access theblock 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 ahigh-availability cluster together with storage on hardwareRAID. Shared-disk file systems normally do not scale over 64 or 128 nodes.

Shared-disk file systems may besymmetric wheremetadata is distributed among the nodes orasymmetric with centralizedmetadata servers.

Distributed file systems

[edit]
See also:Comparison of distributed file systems

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

Distributed fault-tolerant file systems

[edit]

Distributedfault-tolerant replication of data between nodes (between servers or servers/clients) forhigh availability andoffline (disconnected) operation.

  • Coda fromCarnegie 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 forLinux under theGPL.
  • Distributed File System (Dfs) fromMicrosoft focuses on location transparency andhigh availability. Available forWindows under aproprietary software license.
  • HAMMER andHAMMER2 –DragonFly BSD's filesystems for clustered storage, created byMatt Dillon.[1][5]
  • InterMezzo fromCluster File Systems uses synchronization overHTTP. Available forLinux underGPL but no longer in development since the developers are working onLustre.
  • LizardFS a networking, distributed file system based on MooseFS[21]
  • 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.
  • AFAT12 andFAT16 (andFAT32) extension to support automatic file distribution across nodes with extra attributes likelocal,mirror on update,mirror on close,compound on update,compound on close in IBM4680 OS and Toshiba4690 OS. The distribution attributes are stored on a file-by-file basis inspecial entries in the directory table.[22][23]
  • OpenHarmony Distributed File System (HMDFS) used forHuawei'sHarmonyOS withHarmonyOS NEXT base andOpenHarmony-based operating systems, alongsideopenEuler 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 withAccess token manager. Multiple embedded devices connected to the network can automatically synchronise file data with the edge server.[24]
  • 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

[edit]

Distributedparallel file systems stripe data over multiple servers for high performance. They are normally used inhigh-performance computing (HPC).

Some of the distributed parallel file systems use anobject storage device (OSD) (in Lustre called OST) for chunks of data together with centralizedmetadata 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 is anopen-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 forLinux underGPL.
  • VaultFS – configurable any*Data + any*Parity EC (erasure coding) chunks are widely distributed on D+P disks across the cluster

Distributed parallel fault-tolerant file systems

[edit]

Distributed file systems, which also areparallel andfault tolerant, stripe and replicate data over multiple servers for high performance and to maintaindata integrity. Even if a server fails no data is lost. The file systems are used in bothhigh-performance computing (HPC) andhigh-availability clusters.

All file systems listed here focus onhigh availability,scalability and high performance unless otherwise stated below.

NameByLicenseOSDescription
AlluxioUC Berkeley,AlluxioApache LicenseCross-platformAn open-source virtual distributed file system (VDFS).
BeeGFS (formerly FhGFS)Fraunhofer SocietyGNUGPL v2 for client, other components areproprietaryLinuxA free to use file system with optional professional support, designed for easy usage and high performance, used on some of the fastestcomputer clusters in the world. BeeGFS allows replication of storage volumes with automatic failover and self-healing.
CephFSInktank Storage, a company acquired byRed HatGNULGPLLinux kernel,FreeBSD viaFUSE[25]A massively scalable object store. CephFS was merged into the Linux kernel in 2010. Ceph's foundation is thereliable 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 FSGNUGPL v3LinuxAFUSE-based, transparent replication file system, layering on an existing file system and implementing at the file system level whatRAID 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.)
CloudStoreKosmixApache LicenseGoogle File System workalike. Replaced byQuantcast File System (QFS)
dCacheDESY and othersProprietary (free for non-commercial usage)[26]LinuxA write once filesystem, accessible via various protocols.
General Parallel File System (GPFS)IBMProprietaryLinux, Windows and AIXAPOSIX-compliant, high-performance,parallel filesystem. Support synchronousreplication 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 systemNPO Tsukuba OSS Technical Support CenterX11 LicenseLinux,macOS,FreeBSD,NetBSD andSolarisUsesPostgreSQL for metadata andFUSE for mounting.
GlusterFSGluster, a company acquired by Red HatGNUGPL v3Linux,NetBSD,FreeBSD,OpenSolarisA general purpose distributed file system for scalable storage. It aggregates various storage bricks over InfinibandRDMA 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)GoogleInternal softwareFocus onfault tolerance, highthroughput andscalability.
Hadoop Distributed File SystemApache Software FoundationApache LicenseCross-platformOpen source GoogleFS clone.
IBRIX FusionIBRIXProprietary
JuiceFSJuicedataApache LicenseCross-platformAn open-sourcePOSIX-compliant file system built on top ofRedis andobject storage (e.g.Amazon S3), designed and optimized for cloud native environment.
LizardFSSkytechnologyGNUGPL v3Cross-platformAn open source, highly available POSIX-compliant file system that supports Windows clients.
LustreOriginally developed byCluster File Systems and currently supported by OpenSFSGNUGPL v2 &LGPLLinuxAPOSIX-compliant, high-performance filesystem used on a majority of systems in theTop-500 list ofHPC systems. Lustre hashigh availability via storagefailover.
MapR FSMapRProprietaryLinuxHighly 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 andApache Kafka compatible messaging system.
MooseFSCore TechnologyGNUGPL v2 andproprietary[27]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.
ObjectiveFSObjective Security CorporationProprietaryLinux,macOSPOSIX-compliant shared distributed filesystem. Uses object store as a backend. Runs on AWS S3, GCS and object store devices.
OneFS distributed file systemIsilonProprietary[28]FreeBSDBSD-based OS on dedicated Intel based hardware, serving NFS v3 and SMB/CIFS toWindows,macOS,Linux and otherUNIX clients under aproprietary software.
OIO-FSOpenIOProprietaryLinuxOIO-FS provides file-oriented access toOpenIO SDSobject storage backend. It is based onFUSE technology and presents aPOSIX file system to users. This access can be used locally, or over a network usingNFS orSMB.[29]
PanFSPanasasProprietaryLinux,macOS,FreeBSDAPOSIX-compliant, high-performance,parallel filesystem used byHPC clusters. It useserasure coding and snapshots for data protection, is based upon ascale-outobject store, and is focused on transparent failure recovery and ease of use.
Quobyte DCFSQuobyteProprietaryLinux,macOS,FreeBSDA fault-tolerant,parallelPOSIX file system, with block (VMs) and object (S3) interfaces, and advanced enterprise features likemulti-tenancy, strong authentication, encryption.Split-brain safe fault-tolerance is achieved throughPaxos-basedleader election anderasure coding.
RozoFSRozo SystemsGNUGPL v2LinuxAPOSIXDFS focused onfault-tolerance and high-performance, based on theMojetteerasure code to reduce significantly the amount of redundancy (compared to plainreplication).
ScalityScality ringProprietaryLinuxA POSIX file system[citation needed] focused on high availability and performance. Also provides S3/REST/NFS interfaces.
Tahoe-LAFSTahoe-LAFS Software FoundationGNUGPL v2+ and other[30]Linux,Windows,macOSA secure, decentralized, fault-tolerant,peer-to-peerdistributed data store anddistributed file system.
VaultFSSwiss VaultProprietaryLinux,UnixPeer-to-Peer dynamically configurable EC (any*Data + any*Parity) bitrot & HW fault-tolerant POSIX/S3distributed file system using intermixable CMR & SMRshingled magnetic recording disks.
XtreemFSContrail E.U. project, the German MoSGrid project and the German project "First We Take Berlin"BSD 3-Clause[31]Linux,Solaris,macOS, WindowsAcross-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.SSL andX.509 certificates support makes XtreemFS usable over public networks. It also supportsstriping for usage in acluster.

In development:

Peer-to-peer file systems

[edit]

Some of these may be calledcooperative storage cloud.

  • IBM Cloud Object Storage uses CauchyReed–Solomoninformation 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 theChord peer-to-peer protocol.
  • IPFS InterPlanetary File System is p2p, worldwide distributed content-addressable, file-system.
  • VaultFS – fully peer-to-peer with distributed data & metadata, without separate Master or Failover nodes

Special-purpose file systems

[edit]
  • aufs an enhanced version ofUnionFS stackable unification file system
  • AXFS (small footprint compressed read-only, withXIP)
  • Barracuda WebDAV plug-in. Secure Network File Server for embedded devices.
  • Boot File System is used on UnixWare to store files necessary for its boot process.
  • CDfs - a Linuxvirtual file system that provides access to individual data and audio tracks oncompact discs[32][33]
  • Compact Disc File System (reading and writing of CDs; experimental)
  • cfs (caching)
  • Cramfs (small footprint compressed read-only)
  • Davfs2 (WebDAV)
  • Freenet – Decentralized, censorship-resistant
  • FTPFS (FTP access)
  • GmailFS (Google Mail File System)
  • GridFS – GridFS is a specification for storing and retrieving files that exceed the BSON-document size limit of 16 MB forMongoDB.
  • lnfs (long names)
  • LTFS (Linear Tape File System for LTO and Enterprise tape)
  • MVFS – MultiVersion File System, proprietary, used byIBM DevOps Code ClearCase.
  • Nexfs Combines Block, File, Object and Cloud storage into a single pool of auto-tiering POSIX compatible storage.
  • OverlayFS – Aunion mountfilesystem implementation forLinux. Used mainly byDocker for its image layers.
  • romfs
  • SquashFS (compressed read-only)
  • UMSDOS,UVFAT – FAT file systems extended to store permissions and metadata (and in the case of UVFAT,VFAT long file names), used for Linux
  • UnionFS – stackable unification file system, which can appear to merge the contents of several directories (branches), while keeping their physical content separate
  • VaultFS – can intermixably utilize SMRshingled magnetic recording disks to achieve the highest storage densities
  • Venti – Plan 9 de-duplicated storage used byFossil.

Pseudo file systems

[edit]
  • devfs – a virtual file system in Unix-like operating systems for managing device nodes on-the-fly
  • procfs – a pseudo-file system, used to access kernel information about processes
  • tmpfs – in-memory temporary file system (on Unix-like platforms)
  • sysfs – a virtual file system inLinux holding information about buses, devices, firmware, filesystems, etc.
  • debugfs – a virtual file system inLinux for accessing and controlling kernel debugging
  • configfs – a writable file system used to configure various kernel components ofLinux
  • sysctlfs – allow accessingsysctl nodes via a file system; available onNetBSD via PUFFS,[34]FreeBSD kernel via a 3rd-party module,[35][36][37] andLinux as a part of Linux procfs.[38]
  • kernfs – a file system found on some BSD systems (notablyNetBSD) that provides access to some kernel state variables; similar to sysctlfs, Linux procfs and Linux sysfs.
  • WinFS - Uses a relational database to manage files
  • wikifs – a server application forPlan 9's virtual,wiki, file system

Compressed file systems

[edit]
  • VaultFS – auto background compression (writing) & decompression (reading) per file or directory: ten levels: 0 (uncompressed) ... 9 (maximal compression)

Encrypted file systems

[edit]
See also:Rubberhose (file system)

File system interfaces

[edit]

These are not really file systems; they allow access to file systems from an operating system standpoint.

  • FUSE (file system in userspace, like LUFS but better maintained)
  • LUFS (Linux userland file system – seems to be abandoned in favour ofFUSE)
  • PUFFS (Userspace filesystem for NetBSD, including a compatibility layer calledlibrefuse for porting existing FUSE-based applications)
  • Secure Shell File System (SSHFS) – locally mount a remote directory on a server using only asecure shell login.
  • VFS Virtual Filesystem

See also

[edit]

References

[edit]
  1. ^abcKoen Vervloesem (2010-04-21)."DragonFly BSD 2.6: towards a free clustering operating system".LWN.net. Retrieved2019-03-07.
  2. ^abMatt Dillon (2017-09-23)."hammer_disk.h".BSD Cross Reference.DragonFly BSD. Retrieved2019-03-06.
  3. ^"DragonFly BSD 5.2".DragonFly BSD. 2018-06-18. Retrieved2019-03-06.We can now recommend H2 as the default root filesystem in non-clustered mode.
  4. ^abMatt Dillon (2018-05-05)."hammer2_disk.h".BSD Cross Reference.DragonFly BSD. Retrieved2019-03-06.
  5. ^abcMatt Dillon (2018-12-09)."hammer2/DESIGN".BSD Cross Reference.DragonFly BSD. Retrieved2019-03-06.
  6. ^Corbet, Jonathan."The Next3 filesystem". LWN.
  7. ^abTuxera (2019-06-05)."Tuxera acquires mission-critical embedded flash storage leader Datalight".Tuxera. Retrieved2024-06-28.
  8. ^"RTEMS File System". Retrieved20 April 2013.
  9. ^Overstreet, Kent."Bcachefs main site".
  10. ^Edge, Jake."LWN - An update on bcachefs".
  11. ^"Bcachefs merged in linux 6.7".
  12. ^Overstreet, Kent."Bcachefs on Patreon".
  13. ^deepseek-ai/3FS, DeepSeek, 2025-03-04, retrieved2025-03-04
  14. ^Michael Larabel (2011-10-05)."Samsung Introduces New Linux File-System: F2FS". phoronix.com. Retrieved2012-12-07.
  15. ^"United States Patent: 5392427". Patft.uspto.gov. Retrieved2012-06-15.
  16. ^"Linux Kernel Mailing List: logfs: remove from tree". Retrieved2017-03-31.
  17. ^"Jo's Embedded Serial File System (for Standard Serial NOR-Flash)".GitHub. 2019-06-18.
  18. ^Pirkola, G. C. (June 1975). "A file system for a general-purpose time-sharing environment".Proceedings of the IEEE.63 (6):918–924.doi:10.1109/PROC.1975.9856.ISSN 0018-9219.S2CID 12982770.
  19. ^IBM.4690 OS Programming Guide Version 5.2, IBM document SC30-4137-01, 2007-12-06 ([1]).
  20. ^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.
  21. ^LizardFS.org
  22. ^IBM (2003).Information about 4690 OS unique file distribution attributes, IBM document R1001487, 2003-07-30. ("IBM Information about 4690 OS unique file distribution attributes - United States". Archived fromthe original on 2014-05-21. Retrieved2014-05-20.): "[...] 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."
  23. ^IBM.4690 save and restore file distribution attributes. IBM document R1000622, 2010-08-31 ("IBM 4690 save and restore file distribution attributes - United States". Archived fromthe original on 2014-05-21. Retrieved2014-05-20.).
  24. ^"distributed-fs-overview".docs.openeuler.org. Retrieved2024-05-23.
  25. ^"net/ceph14: Ceph delivers object, block, and file storage in a unified system".FreshPorts. Retrieved2021-07-11.
  26. ^"dCache Software License".
  27. ^"MooseFS".
  28. ^"OneFS 8.1 eLicensing and remote support changes".
  29. ^"Features of OIO-FS — OpenIO SDS 18.10 Object Storage documentation".docs.openio.io. Retrieved2018-12-20.
  30. ^"about.rst in trunk/docs – tahoe-lafs". Tahoe-lafs.org. Retrieved2014-02-09.
  31. ^"XtreemFS - License".
  32. ^"CDfs".
  33. ^"CDfs".Christoph Champ's Wiki.
  34. ^"mount_sysctlfs(8)".NetBSD Manual Pages. 2010-04-11. Retrieved2021-07-10.
  35. ^Pawel Jakub Dawidek (2002-12-24)."sysctlfs.README". Archived fromthe original(text/plain) on 2005-02-23. Retrieved2021-07-10.
  36. ^Pawel Jakub Dawidek (2002-12-24)."Re: Hmm, sysctlfs". Retrieved2021-07-10.
  37. ^"Hacking FreeBSD / sysctlfs / [9a7ced]".SourceForge. Retrieved2021-07-10.
  38. ^Terrehon Bowden; Bodo Bauer; Shen Feng."Chapter 2: Modifying System Parameters - The /proc Filesystem".The Linux Kernel. Retrieved2021-07-10.

External links

[edit]
Disk and
non-rotating
Optical disc
Flash memory andSSD
host-sidewear leveling
Distributed parallel
NAS
Specialized
Pseudo
Encrypted
Types
Features
Access control
Interfaces
Lists
Layouts
Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_file_systems&oldid=1296555861"
Categories:
Hidden categories:
[8]ページ先頭
©2009-2025 Movatter.jp