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.

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

Main article: Flash file system

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.

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.

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
BeeGFS (formerly FhGFS) Fraunhofer Society GPLv2 / 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 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, Mac OS X, 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 Independent fork of MooseFS 1.6.27
Lustre originally developed by Cluster File Systems and currently supported by Intel (formerly Whamcloud) 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
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[16] Linux/NetBSD/FreeBSD/OS X/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, Mac OS X 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, Mac OS, 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.[17]
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[18] Windows, Linux, OS X 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, Mac OS X, 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:

Peer-to-peer file systems

Some of these may be called cooperative storage cloud.

Special-purpose file systems

Pseudo- and virtual file systems

Encrypted file systems

File system interfaces

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

See also

References

  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 20 April 2013.
  4. ↑ Zack Brown. "Zack's Kernel News" (PDF). Linux Magazine. No. 75/2007.
  5. 1 2 "Help - IBM AIX Compilers". Publib.boulder.ibm.com. Retrieved 2012-06-15.
  6. ↑ Michael Larabel (2011-10-05). "Samsung Introduces New Linux File-System: F2FS". phoronix.com. Retrieved 2012-12-07.
  7. ↑ "United States Patent: 5392427". Patft.uspto.gov. Retrieved 2012-06-15.
  8. ↑ 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.
  9. ↑ IBM. 4690 OS Programming Guide Version 5.2, IBM document SC30-4137-01, 2007-12-06 ().
  10. ↑ 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.
  11. ↑ "Encina". Zois.co.uk. Retrieved 2012-06-15.
  12. ↑ "IBM - TXSeries for Multiplatforms, V7.1 - TXSeries for Multiplatforms - Software". 306.ibm.com. Retrieved 2012-06-15.
  13. ↑ Hewlett-Packard Co. "HP Support document - HP Support Center". H20000.www2.hp.com. Retrieved 2014-02-09.
  14. ↑ IBM (2003). Information about 4690 OS unique file distribution attributes, IBM document R1001487, 2003-07-30. (): "[...] 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."
  15. ↑ IBM. 4690 save and restore file distribution attributes. IBM document R1000622, 2010-08-31 ().
  16. ↑ http://moosefs.com/license.html
  17. ↑ http://www.nextplatform.com/2015/06/22/exabyte-scale-automation-filters-into-new-file-system/
  18. ↑ "about.rst in trunk/docs – tahoe-lafs". Tahoe-lafs.org. Retrieved 2014-02-09.
  19. ↑ "Parallax: Managing Storage for a Million Machines" (PDF). University of Cambridge Computer Laboratory. Retrieved 2 December 2008.
  20. ↑ Frank Dabek (September 5, 2001). "A Cooperative File System" (PDF). MIT. Retrieved May 30, 2013.
  21. ↑ http://pdos.csail.mit.edu/ivy/osdi02.pdf
  22. ↑ "Flash Layout - OpenWrt Wiki". Wiki.openwrt.org. 2011-12-20. Retrieved 2012-06-15.
  23. ↑ Fabio Kon, Arnaldo Mandel (1995). "SODA: A Lease-Based Consistent Distributed File System" (PDF).

External links

This article is issued from Wikipedia - version of the Monday, May 02, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.