List of file systems

最新推荐文章于 2021-07-08 21:03:47 发布
最新推荐文章于 2021-07-08 21:03:47 发布
阅读量2.3k 收藏
点赞数
分类专栏： filesystem

from : http://en.wikipedia.org/wiki/List_of_file_systems#File_systems_optimized_for_flash_memory.2C_solid_state_media


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[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.

  • 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.
  • 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.
  • 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 Mac OS X. 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 - 64bit 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 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, hashing lookup
  • STL (standard language file system) - a file system developed by IBM.[4]
  • 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[citation needed]; 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[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, 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
  • ExtremeFFS - Internal file system for SSDs.
  • F2FS – Flash-Friendly File System. An open source Linux file system introduced by Samsung in 2012.[5]
  • FFS2 (presumably preceded by FFS1), one of the earliest flash file systems. Developed and patented by Microsoft in the early 1990s.[6]
  • JFFS – Original log structured Linux file system for NOR flash media
  • JFFS2 – Successor of JFFS, for NAND and NOR flash
  • LogFS – Intended to replace JFFS2, better scalability. In early development.
  • Non-Volatile File System—the "non-volatile file system" for flash memory introduced by Palm, Inc..
  • 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.
  • TFAT – A transactional version of the FAT filesystem.
  • TrueFFS - Internal file system for SSDs, implementing error correction, bad block re-mapping and wear levelling.
  • 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
  • XCFiles – an exFAT implementation from Datalight for Wind River VxWorks and other embedded operating systems
  • 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)
  • OTFS - Used in BOS

Record-oriented file systems[edit]

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[edit]

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[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 have access control lists (ACLs), unless otherwise stated below.

Distributed fault-tolerant file systems[edit]

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.
  • Moose File System (MooseFS) from Gemius SA 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 Mac OS X. 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.[13][14]

Distributed parallel file systems[edit]

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 centralizedmetadata servers.

  • Fraunhofer Parallel File System (FhGFS) from the Fraunhofer Society Competence Center for High Performance Computing. Available free of charge for Linux under a proprietary license. (High availability features are on the roadmap.)
  • 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 GPL.
  • Starfish is a POSIX-compatible, N-way redundant file system created by Digital Bazaar Inc. and published under a pseudo open source license. Available for Linux and Mac OS. Windows support is available via Samba.

Distributed parallel fault-tolerant file systems[edit]

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
CephInktank Storage, a company acquired byRed HatLGPLLinux kernelA 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.
CloudStoreKosmixApache License 2.0 Google File System workalike. Replaced by Quantcast File System (QFS)
CosmosMicrosoft internalinternal software Focuses on fault tolerance, high throughput and scalability. Designed forterabyte and petabyte sized data sets and processing with Dryad.
dCacheDESY and others  A write once filesystem, accessible via various protocols
FS-ManagerCDNetworksproprietary softwareLinuxFocused on Content Delivery Network
Gfarm file systemAsia Pacific GridX11 LicenseLinux, Mac OS X,FreeBSD, NetBSDand SolarisUses OpenLDAP or PostgreSQL for metadata and FUSE or LUFS for mounting
General Parallel File System(GPFS)IBMproprietaryAIX, Linux and WindowsSupport replication between attached block storage. Symmetric or asymmetric (configurable)
GlusterFSGluster, a company acquired by Red HatGNU General Public License v3Linux, NetBSD,FreeBSD,OpenSolarisA 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)Googleinternal softwareLinuxFocus on fault tolerance, high throughput and scalability
Hadoop Distributed File SystemApache Software FoundationApache License 2.0Cross-platformOpen source GoogleFS clone
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
MooseFSMooseFSproprietary software[15]Linux/FreeBSD/OS XMooseFS is a fault tolerant, highly availabile 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
LizardFSSkytechnologyGPLcross-platformIndependent fork of MooseFS 1.6.27
IBRIX FusionIBRIXproprietary softwareLinux 
Lustreoriginally developed by Cluster File Systems and currently supported by Intel (formerlyWhamcloud)GPLLinuxA POSIX-compliant, high-performance filesystem. Lustre has high availability via storage failover
MogileFSDanga InteractiveGPLLinux (but may be ported)Is not POSIX compliant, uses a flat namespace, application level, uses MySQL orPostgres for metadata and HTTP for transport.
OneFS distributed file systemIsilon FreeBSDBSD based OS on dedicated Intel based hardware, serving NFS v3 and SMB/CIFS toWindows, Mac OS, Linux and other UNIX clients under a proprietary software
Panasas ActiveScale File System(PanFS)Panasasproprietary softwareLinuxUses object storage devices
PeerFSRadiant Data Corporationproprietary softwareLinuxFocus on high availability and high performance and uses peer-to-peerreplication with multiple sources and targets
Tahoe-LAFSTahoe-LAFS Software FoundationGNU GPL 2+ and other[16]Windows, Linux,OS Xsecure, decentralized, fault-tolerant, peer-to-peer distributed data store anddistributed file system
TerraGrid Cluster File SystemTerrascale Technologies Incproprietary softwareLinuxImplements on demand cache coherency and uses industrial standard iSCSI and a modified version of the XFS file system
XtreemFSContrail E.U. project, the German MoSGrid project and the German project "First We Take Berlin"open-source (BSD)Linux, Solariscross-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.
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)

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 oncooperative 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 [17]
  • 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[edit]

Some of these may be called cooperative storage cloud.

  • Cooperative File System is a read-only file system based on the Chord DHT.[18]
  • 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, coded in C++.
  • 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.[19]
  • 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.

Special-purpose file systems[edit]

  • *FS a/k/a Starfish - a virtual system for collaboration and digital preservation; currently under development
  • 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)
  • 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[20]
  • 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[21] - (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.
  • wikifs (Plan 9) (wiki wiki)
  • 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[edit]

  • 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.
  • WinFS – Windows Future Storage, was planned as the successor to NTFS for Windows Vista.

Encrypted file systems[edit]

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

See also[edit]



Fybon
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Oracle Solaris 11.2 Managing ZFS File Systems in Oracle Solaris
06-20
- **健康检查**：使用`zpool status`和`zfs list`等命令检查ZFS池和文件系统的健康状况。 - **错误修复**：当检测到错误时，ZFS有自我修复机制，也可以手动使用`zpool scrub`命令进行深度扫描和修复。 - **监控与...
Efficient Metadata Management in Large Distributed File Systems
01-15
Metadata management in large distributed systems is a ...provides direct permission calculation to the target file, avoiding the overhead of traversing the pathname for permission check.
VXWORKS文件系统
u011996698的博客
07-08 3502
1　文件系统 1.1　loopFs文件系统 循环文件系统(LoopFs)是一种工具，它将映像文件挂载为虚拟块设备。 使用LoopFs，文件的内容被视为虚拟块设备的扇区数据。数据是一对一映射的。如果映像文件包含文件系统格式(如DOSFS、HRFS或CDROMFS (ISO映像))的有效布局，则新的虚拟块设备将由适当的文件系统驱动程序挂载。tcplay工具创建加密容器。 LoopFs文件系统可以配置为支持挂载已被tcplay的VxWorks版本加密的镜像文件，该版本与tcplay的FreeBSD版本部分
云服务器Linux 磁盘分区、格式化、目录挂载
AbsenceOfTrace的博客
05-09 492
链接地址
List of file signatures
qq_40432713的博客
05-09 306
文件系统介绍
sourthstar的专栏
01-29 1976
refer:  http://en.wikipedia.org/wiki/List_of_flash_file_systems#File_systems_optimized_for_flash_memory.2C_solid_state_media Disk file systems Disk file systems are usually block-oriented. Files i
-Organize-pdf-documents-in-the-File-SystemS
03-21
`List<T>`集合的`Sort()`方法配合自定义比较器可以实现排序，而全文搜索可能需要建立倒排索引。 5. **自动化脚本**：编写C#脚本，定期自动整理PDF文档。例如，可以设定一个定时任务，每天将新添加的PDF按特定规则...
Serv-U File Server Platinum 12.1.0.8
10-12
- Side-by-side views of the remote and local file systems. - Multiple different file system views, (e.g., list, icons, details, thumbnails). - Maintain original file dates and times after file ...
List of Filesystems
winndows的专栏
06-03 367
List of FilesystemsRedHat GFS - http://www.redhat.com/gfs/ Oracle OCFS2 - http://oss.oracle.com/projects/ocfs2/ IBM GPFS - http://www-03.ibm.com/systems/clusters/software/gpfs/index.html Sun
JavaScript 音乐播放器及其源代码.zip
07-22
项目：带有源代码的 JavaScript 音乐播放器 JavaScript 音乐播放器是一个使用 JavaScript、CSS 和 HTML 开发的简单项目。这个项目很有趣。在这里，用户可以通过单击不同颜色的图块来播放不同类型的曲调，并欣赏音乐的声音。此外，用户可以像钢琴一样使用它们来生成不同的曲调。   项目制作 音乐播放器项目仅包含 HTML、CSS 和 JavaScript。谈到该系统的功能，用户可以播放不同类型的音乐。您只需单击不同颜色的图块即可收听音乐。该项目包含大量 JavaScript，用于使项目正常运行。 如何运行该项目？ 要运行此项目，您不需要任何类型的本地服务器，但需要浏览器。我们建议您使用现代浏览器，如 Google Chrome 和 Mozilla Firefox。要运行此系统，首先，通过单击 index.html 文件在浏览器中打开项目。 演示： 该项目为国外大神项目，可以作为毕业设计的项目，也可以作为大作业项目，不用担心代码重复，设计重复等，如果需要对项目进行修改，需要具备一定基础知识。 注意：如果装有360等杀毒软件，可能会出现误报的情况，源码本身并无病毒，使用源码时可以关闭360，或者添加信任。
鸿蒙开发健康app案例
07-22
该项目是记录用户日常饮食情况，以及针对不同食物摄入营养不同会有对应的营养摄入情况和日常运动消耗情况，用户可以自己添加食品以及对应的热量。 主要有登陆界面，饮食统计页面，食物列表页 登陆界面首先是进入欢迎界面，然后加载首选项，用户同意授权进入首页，否则弹出用户协议，同意保存首选项，否则就跳出app 饮食统计界面，进入首页之后，用户可以选择日期和获取当前日期来加载饮食记录，饮食记录会展示热量统计，营养统计和分组展示饮食记录 食物列表页展示食物列表以及可以填写食物数量和跳转到食物详情页
1_2_1_pointcloud_based_occupancy_gride_map.launch.py
07-22
1_2_1_pointcloud_based_occupancy_gride_map.launch.py
USB教程与源码.rar
07-22
USB教程与源码.rar
巴比达内网穿透技术-内网穿透
07-22
巴比达内网穿透技术-内网穿透
基于python的网页自动化工具 既能控制浏览器，也能收发数据包
07-22
基于python的网页自动化工具。既能控制浏览器，也能收发数据包。可兼顾浏览器自动化的便利性和requests的高效率。功能强大，内置无数人性化设计和便捷功能。语法简洁而优雅，代码量少。
ppp协议实验路由器中的一种实验
最新发布
07-22
ppp协议实验路由器中的一种实验
Matplotlib styles for scientific plotting
07-22
Matplotlib styles for scientific plotting
ERROR: error loading sources list:
04-05
This file contains a list of software repositories for package managers to use to install and update software. To fix this error, you can try the following steps: 1. Check if the sources list file...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值