List Of File Systems

The following lists identify, characterize, and link to more thorough information on computer file systems.

Many older operating 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

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.

  • ADFS - Acorn's Advanced Disc filing system, successor to DFS.
  • AdvFS - Advanced File System, designed by Digital Equipment Corporation for their Digital UNIX (now Tru64 UNIX) operating system.
  • AFS (Not to be confused with Andrew File System, below) - Acer Fast Filesystem, used on SCO OpenServer
  • AFS - Ami File Safe, a commercial file system shipped on Amiga in the 1990s (AFS is structure-compatible with PFS)
  • AosFS - File System used by the Oberon and A2 operating systems.
  • APFS - Apple File System is a next-generation file system for Apple products.
  • AthFS - AtheOS File System, a 64-bit journaled filesystem now used by Syllable. Also called AFS.
  • BFS - the Boot File System used on System V release 4.0 and UnixWare.
  • BFS - the Be File System used on BeOS, occasionally misnamed as BeFS. Open source implementation called OpenBFS is used by the Haiku operating system.
  • Btrfs - is a copy-on-write file system for Linux announced by Oracle in 2007 and published under the GNU General Public License (GPL).
  • CBMFS - The filesystem used on most Commodore 64-compatible floppy drives including the venerable 1541.
  • CFS - The Cluster File System from Veritas, a Symantec company. It is the parallel access version of VxFS.
  • CMDFS - A filesystem extension added to CBMFS by Creative Micro Designs, for use in their 3.5 inch floppy drives, RAM disks, and hard drive controllers.
  • CP/M file system -- Native filesystem used in the CP/M (Control Program for Microcomputers) operating system which was first released in 1974.
  • DDFS - Data Domain File System, the data deduplication file system that ships in the Data Domain Deduplication Storage Systems which are an alternative to tape for storing backups and archives.[1]
  • DTFS - Desktop File System, featuring file compression, used by SCO OpenServer
  • DOS 3.x - Original floppy operating system and file system developed for the Apple II
  • EAFS - Extended Acer Fast Filesystem, used on SCO OpenServer
  • Extent File System (EFS) - an older block filing system under IRIX.
  • ext - Extended file system, designed for Linux systems
  • ext2 - Second extended file system, designed for Linux systems.
  • ext3 - A journaled form of ext2.
  • ext4 - A follow up for ext3 and also a journaled filesystem with support for extents.
  • ext3cow - A versioning file system form of ext3.
  • FAT - File Allocation Table, used on DOS and Microsoft Windows; FAT12, FAT16 and FAT32 for 12-, 16- and 32-bit table depths.
  • FFS (Amiga) - Fast File System, used on Amiga systems. This FS has evolved over time. Now counts FFS1, FFS Intl, FFS DCache, FFS2.
  • FFS - Fast File System, used on* BSD systems
  • 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
  • HFS - Hierarchical File System in z/OS; not to be confused with Apple's HFS. HFS is still supported but IBM's stated direction is zFS.
  • 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+ - 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
  • HPFS - High Performance File System, used on OS/2
  • HTFS - High Throughput Filesystem, used on SCO OpenServer
  • IceFS - 64-bit filesystem for MorphOS
  • ISO 9660 - Used on CD-ROM and DVD-ROM discs (Rock Ridge and Joliet are extensions to this)
  • JFS - IBM Journaling file system, provided in Linux, OS/2, and AIX. Supports extents.
  • JXFS used in AmigaOS 4.1.
  • LisaFS - Filesystem used by Apple Lisa's operating system. Unique in that it allowed two different files with exactly same name ("foo" and "foo").
  • LFS - 4.4BSD implementation of a log-structured 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.[2]
  • 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
  • NetWare File System - The original NetWare 2.x-5.x file system, used optionally by later versions.
  • NSS - Novell Storage Services. This is a new 64-bit journaling file system using a balanced tree algorithm. Used in NetWare versions 5.0-up and recently ported to Linux.
  • OneFS - One File System. This is a fully journaled, distributed file system used by Isilon. OneFS uses FlexProtect and Reed-Solomon encodings to support up to four simultaneous disk failures.
  • OFS - Old File System, on Amiga. Good for floppies, but fairly useless on hard drives.
  • OS-9 file system
  • PFS - and PFS2, PFS3, etc. Technically interesting file system available for the Amiga, performs very well under a lot of circumstances. Very simple and elegant.
  • ProDOS - Operating system and file system successor to DOS 3.x, for use on Apple's computers prior to the Macintosh & Lisa computers, the Apple series, including the IIgs
  • Qnx4fs - File system that is used in QNX version 4 and 6.
  • Qnx6fs - New copy-on-write file system presented in QNX 6.4.0 and used as default since 6.4.1.
  • ReFS (Resilient File System) - New file system by Microsoft that is built on the foundations of NTFS (but cannot boot, has a default cluster size of 64 KB and does not support compression) and is intended to be used with the Windows Server 2012 operating system.
  • ReiserFS - File system that uses journaling
  • Reiser4 - File system that uses journaling, newest version of ReiserFS
  • Reliance - Datalight's transactional file system for high reliability applications
  • Reliance Nitro - Tree-based transactional file system developed for high-performance embedded systems, from Datalight
  • RFS - Native filesystem for RTEMS[3]
  • S51K - AT&T UNIX System V 1KB Filesystem, used by SCO UNIX and SCO OpenServer
  • 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.
  • SFS - Smart File System, journaling file system available for the Amiga platforms.
  • Soup (Apple) - the "file system" for Apple Newton Platform, structured as a shallow database
  • SpadFS - Linux. Non-journaling file system that uses a technique called "crash counting" for consistency,[4] hashing lookup.
  • STL (standard language file system) - a file system developed by IBM.[5]
  • TRFS - Experimental, design only
  • Tux3 - An experimental versioning file system intended as a replacement for ext3
  • UDF - Packet-based file system for WORM/RW media such as CD-RW and DVD, now supports hard drives and flash memory as well.
  • UFS - Unix File System, used on Solaris and older BSD systems
  • UFS2 - Unix File System, used on newer BSD systems
  • VxFS Veritas file system, first commercial journaling file system[]; HP-UX, Solaris, Linux, AIX, UnixWare
  • VLIR (Variable Length Indexed Record) - a filesystem extension added by Berkeley Softworks to CBMFS, allowing full random access read and write operations, for computers running GEOS.
  • WAFL - Write Anywhere File Layout. High performance, log-structured like file system. WAFL uses RAID-DP to protect against multiple disk failures, and NVRAM for transaction log replays. Used on NetApp systems
  • XFS - Used on SGI IRIX and Linux systems
  • zFS - z/OS Distributed File Service zSeries File System; not to be confused with other file systems named zFS or ZFS.
  • ZFS - 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:

File systems optimized for flash memory, solid state media

Solid state media, like flash memory, are similar to disks in their interfaces, but have different problems. On low level, they require special handling such as wear leveling and different error detection and correction algorithms. Typically a device such as solid-state disk 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 needed.

  • CASL is a filesystem designed by Nimble Storage that uses solid-state devices to cache traditional hard disk drives.
  • ETFS - Embedded Transactional File System. Designed primarily for NAND devices by QNX Software Systems.
  • exFAT - Microsoft proprietary system intended for flash cards (see also XCFiles, an exFAT implementation for Wind River VxWorks and other embedded operating systems)
  • ExtremeFFS - Internal file system for SSDs.
  • F2FS - Flash-Friendly File System. An open source Linux file system introduced by Samsung in 2012.[6]
  • FFS2 (presumably preceded by FFS1), one of the earliest flash file systems. Developed and patented by Microsoft in the early 1990s.[7]
  • JFFS - Original log structured Linux file system for NOR flash media
  • JFFS2 - Successor of JFFS, for NAND and NOR flash
  • LSFS - is 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.[8]
  • Non-Volatile File System--the "non-volatile file system" for flash memory introduced by Palm, Inc.
  • NOVA - The "non-volatile memory accelerated" file system for persistent main memory.
  • OneFS - OneFS is a file system utilized by Isilon. It supports selective placement of meta-data directly onto flash SSD.
  • RFS - Robust File System (developed and used by Samsung)
  • Segger Microcontroller Systems emFile - File system for deeply embedded applications which supports both NAND and NOR flashes. Wear leveling, fast read and write, and very low RAM usage.
  • SafeFLASH - HCC-Embedded - Fail-safe file system that supports NAND and NOR flash types with integrated wear-leveling and bad-block handling.
  • SPIFFS - SPI Flash File System, wear leveling file system 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 utilize non-volatile DRAM
  • UFFS - Ultra low cost flash file system for embedded system
  • Unison RTOS - Fsys-Nand/Nor small footprint low cost flash file system for embedded systems
  • Write Anywhere File Layout - WAFL is an internal file system utilized by NetApp within their DataONTAP OS, originally optimized to use non-volatile DRAM
  • YAFFS - A Log structured file system designed for NAND flash, but also used with NOR flash.
  • ZFS - Allows placing write-ahead log (ZIL) on flash, and using flash as a second-level read cache (L2ARC)

Record-oriented file systems

In record-oriented file systems files are stored as a collection of records. They are typically associated with 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 databases than with other file systems.

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 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 asymmetric with centralized metadata servers.

Distributed file systems

Distributed file systems 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.

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 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 GPL.
  • Distributed File System (Dfs) from Microsoft focuses on location transparency and high availability. Available for Windows under a proprietary software license.
  • InterMezzo from Cluster File Systems uses synchronization over HTTP. Available for Linux under GPL but no longer in development since the developers are working on Lustre.
  • Lizardfs a networking, distributed file system based on MooseFS
  • 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.
  • 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 special entries in the directory table.[15][16]

Distributed parallel file systems

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

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

Distributed parallel fault-tolerant file systems

Distributed file systems, which also are 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 (HPC) and high-availability clusters.

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

Name By License OS Description
Alluxio (formerly Tachyon) Alluxio Open Foundation Apache License 2.0 Linux and macOS Alluxio, formerly known as Tachyon, is the world's first memory speed virtual distributed storage system. It unifies data access and bridges computation frameworks and underlying storage systems. Applications only need to connect with Alluxio to access data stored in any underlying storage systems. Additionally, Alluxio's memory-centric architecture enables data access orders of magnitude faster than existing solutions.
BeeGFS (formerly FhGFS) Fraunhofer Society Open-source (GPLv2 & BeeGFS EULA) 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 clusters in the world. BeeGFS allows replication of storage volumes with automatic failover and self-healing.
Ceph Inktank Storage, a company acquired by Red Hat LGPL Linux kernel 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 is a 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 Google File System workalike. Replaced by Quantcast File System (QFS)
Cosmos Microsoft internal internal software Focuses on fault tolerance, high throughput and scalability. Designed for terabyte and petabyte sized data sets and processing with Dryad.
dCache DESY and others A write once filesystem, accessible via various protocols
FS-Manager CDNetworks proprietary software Linux Focused on Content Delivery Network
General Parallel File System (GPFS) IBM proprietary AIX, Linux and Windows Support replication between attached block storage. Symmetric or asymmetric (configurable)
Gfarm file system Asia Pacific Grid X11 License Linux, macOS, FreeBSD, NetBSD and Solaris Uses OpenLDAP or PostgreSQL for metadata and FUSE or LUFS for mounting
GlusterFS Gluster, a company acquired by Red Hat GNU General Public License v3 Linux, NetBSD, FreeBSD, OpenSolaris A general purpose distributed file system for scalable storage. It aggregates various storage bricks over Infiniband 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 Cross-platform Open source GoogleFS clone
IBRIX Fusion IBRIX proprietary software
Infinit Infinit International, Inc proprietary cross-platform A POSIX-compliant file system for both local area network and wide area networks. Infinit replicates blocks of data between the various storage resources composing the infrastructure (being local or through cloud API) in order to guarantee data reliability (durability and availability) through Byzantine fault tolerance and data rebalancing (i.e. self healing).
LizardFS Skytechnology GPL cross-platform An open source, highly available POSIX-compliant file system that supports Windows clients.
Lustre originally developed by Cluster File Systems and currently supported by OpenSFS GPL Linux A POSIX-compliant, high-performance filesystem. Lustre has high availability via storage failover
MapR FS MapR 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
MogileFS Danga Interactive GPL Linux (but may be ported) Is not POSIX compliant, uses a flat namespace, application level, uses MySQL or Postgres for metadata and HTTP for transport.
MooseFS Core Technology GPLv2/proprietary[17] Linux/NetBSD/FreeBSD/macOS/OpenSolaris MooseFS is 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 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 FreeBSD BSD based OS on dedicated Intel based hardware, serving NFS v3 and SMB/CIFS to Windows, macOS, Linux and other UNIX clients under a proprietary software
Panasas ActiveScale File System (PanFS) Panasas proprietary software Linux Uses object storage devices
PeerFS Radiant Data Corporation proprietary software Linux Focus on high availability and high performance and uses peer-to-peer replication with multiple sources and targets
Quobyte Quobyte Proprietary software Linux All in one data center file system (file, block and object storage). Commercial successor of XtreemFS, founded by the XtreemFS development team.[18]
RozoFS Rozo Systems GNU GPLv2 Linux A POSIX DFS focused on fault-tolerance and high-performance, based on the Mojette erasure code to reduce significantly the amount of redundancy (compared to plain replication).
Tahoe-LAFS Tahoe-LAFS Software Foundation GNU GPL 2+ and other[19] Windows, Linux, macOS secure, decentralized, fault-tolerant, peer-to-peer distributed data store and distributed file system
TerraGrid Cluster File System Terrascale Technologies Inc proprietary software Linux Implements on demand cache coherency and uses industrial standard iSCSI and a modified version of the XFS file system
XtreemFS Contrail E.U. project, the German MoSGrid project and the German project "First We Take Berlin" open-source (BSD) Linux, Solaris, macOS, Windows 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. SSL and X.509 certificates support makes XtreemFS usable over public networks. It also supports Striping for usage in a cluster.

In development:

  • PlasmaFS is a free and open-source (GPL) userspace filesystem focusing on data safety and security. PlasmaFS provides a transactional API which is accessible over a SunRPC-based protocol. PlasmaFS can also be mounted as NFS volume, and is POSIX-compliant. Both data and metadata are replicated.
  • WebDFS An Open Source scalable, decentralized file store similar to MogileFS in function and purpose. Uses HTTP as the transport. Data is automatically and optimally re-arranged to accommodate the addition of new resources. The lack of central meta data management greatly simplifies deployment and use.
  • 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 devices. Under development and not freely available.
  • HAMMER/ANVIL by Matt Dillon
  • OASIS from ETRI. Very similar to the Lustre or Panasas. Available for Linux via. special technology transfer program provided by ETRI.
  • GLORY-FS also from ETRI. Very similar to the Google File System or Hadoop, but it is fully POSIX compliant. It is specially optimized for large-scale web 2.0 content services. Version 2.5 is available for Linux via. special technology transfer program provided by ETRI. Windows version is under development.
  • parallax [20]
  • PNFS (Parallel NFS) - Clients available for Linux and OpenSolaris and back-ends from NetApp, Panasas, EMC Highroad and IBM GPFS
  • Coherent Remote File System (CRFS) - requires Btrfs
  • Parallel Optimized Host Message Exchange Layered File System (POHMELFS) and Distributed STorage (DST). POSIX compliant, added to Linux kernel 2.6.30
  • Sector from National Center for Data Mining. Sector is a high performance, scalable, and secure distributed file system. Available under Apache License 2.0
  • StarFS from CDNetworks. The StarFS is a global storage platform which supports virtualization of distributed file system and event-driven file synchronization with remote StarFS clusters.
  • Unilium provides a decentralized, versioning file system stored in content addressable storage, whose data may be hosted across heterogeneous data storage nodes.

Peer-to-peer file systems

Some of these may be called cooperative storage cloud.

  • Cooperative File System is a read-only file system based on the Chord DHT.[21]
  • Cleversafe uses Cauchy Reed-Solomon information dispersal algorithms to separate data into unrecognizable slices and distribute them, via secure Internet connections, to multiple storage locations.
  • Infinit is a peer-to-peer file system that can be deployed on-premise or over a set of storage resources of different nature: local disk, NAS and even cloud-based resources.
  • Ivy is a multi-user read/write peer-to-peer file system. Ivy has no centralized or dedicated components, and it provides useful integrity properties without requiring users to fully trust either the underlying peer-to-peer storage system or the other users of the file system.[22]
  • Pastis file system is a French peer-to-peer file system developed in Java
  • NimbusFS is a DHT-based cloud filesystem, with built-in replication and x509 certificates authentication, released under CC-BY-NC license.
  • IPFS InterPlanetary File System is p2p, worldwide distributed content-addressable, file-system.

Special-purpose file systems

  • archfs (archive)
  • aufs an enhanced version of UnionFS stackable unification file system
  • AXFS (small footprint compressed read-only, with XIP)
  • 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.
  • Cascade File System - provides file system access to Subversion and Perforce repositories and caches their contents locally
  • cdfs (reading and writing of CDs)
  • clicfs - transparent fuse based LZMA compression read-only layer for other filesystems, including writable ones. Some writing facility is available. Specially designed for linux live distributions.
  • Compact Disc File System (reading and writing of CDs; experimental)
  • cfs (caching)
  • cvsfs (presents the CVS contents as mountable file system).
  • Dokan LGPL FUSE for Windows analog
  • compFUSEd (overlay transparent read-write compression, FUSE based)
  • FuseCompress (overlay transparent read-write compression, FUSE based)
  • Cramfs (small footprint compressed read-only)
  • Cromfs is a user-space (FUSE based) read-only filesystem using an efficient LZMA compression algorithm.
  • Davfs2 (WebDAV)
  • Freenet - Decentralized, censorship-resistant
  • FTPFS/CurlFtpFS (ftp access)
  • GmailFS (Google Mail File System)
  • lnfs (long names)
  • LTFS (Linear Tape File System for LTO and Enterprise tape)
  • mhddfs - Join several filesystems together to form a single larger one
  • mini fo (The mini fanout overlay file system) - Redirects modifying operations to a writeable location called "storage directory", and leaving the original data in the "base directory" untouched. When reading, the file system merges the modified and original data so that only the newest versions will appear. Most prominently used in OpenWrt.[23]
  • MVFS - MultiVersion File System, proprietary, used by Rational ClearCase.
  • MTFS - stackable file system, reliability improvement mechanism for Lustre and other file systems based on replication.
  • nntpfs (netnews)
  • ParFiSys (Experimental parallel file system for massively parallel processing)
  • pramfs - Protected and Persistent RAM Filesystem
  • RAIF Redundant Array of Independent Filesystems - stackable RAID-like file system
  • romfs
  • SODA: a Lease-based Consistent Distributed File System[24] - (early 1990s)
  • SquashFS (compressed read-only)
  • SysmanFS (based on FUSE, a virtual file system for cluster system management)
  • 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
  • Venti - Plan 9 de-duplicated storage used by Fossil.
  • WDK.VFS - SiteAdmin CMS Virtual File System introduced by Evgenios Skitsanos
  • Datalight Reliance - transactional file system for 32-bit embedded systems from Datalight, Inc.
  • ERTFS ProPlus64 - it comes with integrated Failsafe operation, it contains a default journaling mode.
  • WBFS - Wii Backup FileSystem
  • whefs - Embedded Filesystem is an open source C library implementing an embedded/embeddable filesystem.

Pseudo- and virtual file systems

  • devfs - Virtual file system in Unix-like operating systems for managing devices on-the-fly
  • debugfs -Virtual file system in Linux for accessing and controlling kernel debugging.
  • procfs - Pseudo-file system, used to access kernel information about processes
  • tmpfs - in-memory temporary file system (on Linux platforms).
  • specfs - Special File System for device files
  • sysfs - Virtual file system in Unix-like operating systems holding information about buses, devices, firmware, filesystems, etc.
  • wikifs - a server application for Plan 9's virtual, wiki, file system
  • WinFS - Windows Future Storage, was planned as the successor to NTFS for Windows Vista.

Encrypted file systems

File system interfaces

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 of FUSE)
  • VFS Virtual Filesystem
  • Callback File System - the SDK to build custom filesystems and plug them to Windows OS.

See also


  1. ^ Zhu, Ben; Li, Kai; Patterson, Hugo (2008). "Avoiding the Disk Bottleneck in the Data Domain Deduplication File System". Proceedings of the 6th USENIX Conference on File and Storage Technologies (FAST '08). San Jose, CA. pp. 269-282. 
  2. ^ Corbet, Jonathan. "The Next3 filesystem". LWN. 
  3. ^ "RTEMS File System". Retrieved 2013. 
  4. ^ Zack Brown. "Zack's Kernel News" (PDF). Linux Magazine. No. 75/2007. 
  5. ^ a b "Help - IBM AIX Compilers". Retrieved . 
  6. ^ Michael Larabel (2011-10-05). "Samsung Introduces New Linux File-System: F2FS". Retrieved . 
  7. ^ "United States Patent: 5392427". Retrieved . 
  8. ^ "Linux Kernel Mailing List: logfs: remove from tree". Retrieved . 
  9. ^ Pirkola, G. C. (June 1975). "A file system for a general-purpose time-sharing environment". Proceedings of the IEEE. 63 (6): 918-924. ISSN 0018-9219. doi:10.1109/PROC.1975.9856. 
  10. ^ IBM. 4690 OS Programming Guide Version 5.2, IBM document SC30-4137-01, 2007-12-06 ([1]).
  11. ^ 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.
  12. ^ "Encina". IBM. Archived from the original on 2012-02-09. Retrieved . 
  13. ^ "TXSeries for Multiplatforms". Retrieved . 
  14. ^ Hewlett-Packard Co. "HP Support document - HP Support Center". Retrieved . [dead link]
  15. ^ IBM (2003). Information about 4690 OS unique file distribution attributes, IBM document R1001487, 2003-07-30. ("Archived copy". Archived from the original on 2014-05-21. Retrieved . ): "[...] 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."
  16. ^ IBM. 4690 save and restore file distribution attributes. IBM document R1000622, 2010-08-31 ("Archived copy". Archived from the original on 2014-05-21. Retrieved . ).
  17. ^
  18. ^
  19. ^ "about.rst in trunk/docs - tahoe-lafs". Retrieved . 
  20. ^ "Parallax: Managing Storage for a Million Machines" (PDF). University of Cambridge Computer Laboratory. Retrieved 2008. 
  21. ^ Frank Dabek (September 5, 2001). "A Cooperative File System" (PDF). MIT. Archived from the original (PDF) on October 4, 2013. Retrieved 2013. 
  22. ^
  23. ^ "The OpenWrt Flash Layout". 2011-12-20. Retrieved . 
  24. ^ Fabio Kon, Arnaldo Mandel (1995). "SODA: A Lease-Based Consistent Distributed File System" (PDF). 

External links

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.



Top US Cities