文件系统列表

最新推荐文章于 2022-07-12 10:29:42 发布
最新推荐文章于 2022-07-12 10:29:42 发布
阅读量1.8k 收藏 1
点赞数
文章标签： system file linux parallel performance compression

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 filesystem shipped on Amiga in the 1990s (AFS is structure compatible with PFS)
  • AthFS - AtheOS File System, a 64-bit journaled filesystem now used by Syllable. Also called AFS
  • 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 the late 1970s.
  • 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
  • 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
  • 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.
  • 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 and is intended to be used with the soon to be released Windows Server 8 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
  • S51K – AT&T UNIX System V 1KB Filesystem, used by 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.
  • SpadFS - Linux - non-journaling, hashing lookup
  • STL (standard language file system) - a file system developed by IBM.[3]
  • 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.
  • 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
  • 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 NetAppsystems
  • XFS – Used on SGI IRIX and Linux systems
  • ZFS - Sun Microsystems ZFS open source specification ported to IBM zSeries systems.

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

[edit]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. While practically eliminating seek times, they require special handling such as wear leveling and different error detection and correction algorithms.

  • CASL is a filesystem designed by Nimble Storage that uses Solid State Devices to cache traditional hard drives.
  • ETFS - Embedded Transactional File System. Designed primarily for NAND devices by QNX Software Systems.
  • exFAT - Microsoft proprietary system intended for flash cards[5]
  • ExtremeFFS - Internal file system for SSDs.
  • 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.
  • 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.
  • 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 [7]
  • Unison RTOS - Fsys-Nand/Nor small footprint low cost flash file system for embedded systems [8]
  • 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)

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

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

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

[edit]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 (Microsoft) (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 [13] is an open source secure, decentralized, fault-tolerant filesystem utilizing encryption as the basis for a least-authority replicated design.

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

  • 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). 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.

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

In development:

  • PlasmaFS [15] 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.
  • Ceph from University of California, Santa Cruz which utilized entire block devices. Available for Linux under the LGPL. Merged for Linux kernel 2.6.34.
  • 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.
  • Hadoop Distributed File System - free GoogleFS clone produced by Apache. http://hadoop.apache.org/
  • 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 Linuxvia. special technology transfer program provided by ETRI. Windows version is under development.
  • parallax [16]
  • PNFS (Parallel NFS) - Clients available for Linux and OpenSolaris and back-ends from NetApp, Panasas, EMC Highroad and IBM GPFS [17]
  • 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 [4] 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 [5] provides a decentralized, versioning file system stored in content addressable storage, whose data may be hosted across heterogeneous data storage nodes.

[edit]Peer-to-peer file systems

  • CFS is a read-only file system based on the Chord DHT
  • Cleversafe uses Cauchy Reed-Solomon Information Dispersal Algorithms (IDAs) to separate data into unrecognizable slices and distribute them, via secure Internet connections, to multiple storage locations.
  • Infinit is a large-scale peer-to-peer file system developed in C++ which enables users to both reliably and securely store their files in a location-independent and replicated way; and to share files with a controlled set of users, friends etc.
  • Ivy [18] 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.
  • Pastis file system is a French peer-to-peer file system developed in Java
  • ColonyFS emphasises anonymity, security and dependability, is written in Java and C#, and is released under the GPL

[edit]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 was used on UnixWare to store files necessary to 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)
  • 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[19]
  • MVFS – MultiVersion File System, proprietary, used by Rational ClearCase.
  • 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 - (early 1990s)
  • SquashFS (compressed read-only)
  • SysmanFS (based on FUSE, a virtual file system for cluster system management)
  • tmpfs in-memory temporary file system (on Linux platforms).
  • UMSDOS - FAT file system extended to store permissions and metadata, 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 - WanderingHorse.net Embedded Filesystem is an open source C library implementing an embedded/embeddable filesystem.

[edit]Pseudo- and virtual file systems

  • devfs – Virtual file system in Unix-like operating systems for managing devices on-the-fly
  • procfs – Pseudo-file system, used to access kernel information about processes
  • 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.

[edit]Encrypted file systems

[edit]Files 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 – SDK that lets developers create installable virtual file systems for Windows in user mode
hello9050
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
HDFS的优化实现ADFS.zip
07-16
ADFS(Ali Distributed File System)是基于hadoop开源分布式系统HDFS的一种优化 实现，能够将HDFS中单点master namenode节点中的内存数据结构利用高速存储介质同步到磁盘中，同时能够提供很高的吞吐和性能 。这样做能够同时解决namenode内存瓶颈问题，meta信息持久化问题和单点故障问题，以及启动时间过长等困扰用户的地方。 标签：ADFS
linux系统输出文件系统列表,（一） Linux文件系统和目录
weixin_33410880的博客
05-12 448
目标1.识别Linux的重要目录的用途2.使用绝对和相对路径名称指定文件3.显示文件目录列表4.使用命令行实用工具创建、复制、移动和删除文件与目录5.查找文件或目录一、 文件系统层次结构目标：了解基本的文件系统布局、组织、以及重要文件类型的位置/usr #安装的软件、共享的库，包括文件和静态只读程序数据。 /usr/bin #用户命令 /usr/sbin #系统管理命令 /usr/local #本...
Android系统文件目录文件列表
ZEROのSPACE
05-21 865
一、system\bin system\bin是系统的文件目录，里面的文件都是系统的本地程序，从bin文件夹名称可以看出是binary二进制的程序，里面主要是Linux系统自带的组件，现在就主要文件做下简单的分析介绍： \system\bin\akmd \system\bin\am \system\bin\app_process 系统进程 \system\bin\dalvikvm D
文件系统汇总
qq_28399355的博客
11-30 153
list-db:简单的文件系统列表持久性
05-29
"简单的文件系统列表持久性"意味着这个数据库提供了一种方法，能够将这些文件系统列表的数据存储到磁盘上，并在需要时重新加载，确保数据的持久化，即使在系统故障后也能恢复。 在标签中提到了“JavaScript”，这...
Delphi PC端读取设备文件系统列表及设备信息
03-06
本项目聚焦于使用Delphi实现PC端设备文件系统列表的读取以及设备信息的获取，这对于系统监控、数据备份或者设备管理类软件来说是至关重要的功能。 首先，让我们深入了解如何使用Delphi来读取设备文件系统列表。在...
os.rar_模拟文件系统
09-14
在压缩包子文件的文件名称列表中，我们看到`www.pudn.com.txt`可能是一个示例文件，用于演示如何在模拟文件系统中存储和访问文本文件。而“可执行程序”可能是一个用于测试模拟文件系统功能的应用程序，它可以模拟...
vc.rar_获取文件列表
09-22
在Windows操作系统中，可以通过编程接口（API）来遍历文件系统，获取驱动器上的所有文件信息。这个过程通常涉及以下几个关键知识点： 1. **文件系统枚举**：Windows API提供了诸如`FindFirstFile`, `FindNextFile` ...
wjj.rar_获取文件列表
09-19
VB是一种流行的面向对象的编程语言，它提供了丰富的功能来处理文件系统操作。在这个程序中，开发者可能使用了FileSystemObject（FSO）或者Directory类来遍历文件夹，获取每个文件或子文件夹的名称，并将这些信息存储...
Windows几种文件系统的比较
09-17
Windows几种文件系统的比较 Window 3.x和MS-DOS一直使用的是文件分配表（FAT）系统；Window95使用的是扩展FAT文件系统；WindowsNT文件系统则再继续支持16位文件系统的同时，还支持两种32位的文件系统—WindowsNT文件系统(NTFS)和高性能文件系统（HPFS）。这几种文件系统各有优缺点，适合于不同的应用目的。
几种嵌入式文件系统的对比
05-11
对几种文件嵌入式文件系统进行了对比，主要是TFAT,FAT,和reliance。
Linux下的文件系统大全
刘爱贵的专栏
11-15 5986
 Source: http://www.linuxlinks.com/Kernel/File_Systems/ Accessfsa permission filesystem for linuxActive Block I/O Scheduling System The
文件系统有哪些
yjxsdzx的博客
09-09 6009
FAT在Win 9X下，FAT16支持的分区最大为2GB同FAT16相比FAT32最大的优点是可以支持的磁盘大小达到2TB（2047GB），但是不能支持小于512MB的分区。 基于FAT32的Win 2000可以支持分区最大为32GB，而基于 FAT16的Win 2000支持的分区最大为4GBNTFSNTFS文件系统是一个基于安全性的文件系统，是Windows NT所采用的独特的文件系统结构，它是
制作文件系统参考大全
kuangreng的专栏
01-29 795
文件系统类型汇总
u010385646的专栏
03-06 1933
The following lists identify, characterize, and link to more thorough information oncomputer file systems. Many older operating systems support only their one "native" file system, which does not
408操作系统学习笔记——文件管理
JiangNan_1002的博客
07-12 4783
1.文件管理基础 2.目录 3.文件系统
文件系统基础知识
iva_brother的博客
08-31 1765
1、长期信息存储需要哪些要求？ 1>能够存储大量信息； 2>使用信息的进程终止时，信息仍旧存在； 3>必须能使多个进程并发存取相关信息。   2、什么是文件系统？ 文件系统是对常规文件和目录的组织集合。在Linux中，用来创建文件系统的命令是mkfs，而且在Linux及其他类Unix系统中，并不区分文件和目录：目录就是记录了其他文件名的文件。   3、什么是文件？...
mount 命令查看已经挂载的文件系统列表
最新发布
05-19
是的，mount命令可以用于查看当前系统中已经挂载的文件系统列表。它会列出已经挂载的设备、挂载点、文件系统类型等信息。你可以在终端中输入以下命令来查看： ``` mount ``` 执行后，会显示出已经挂载的文件系统...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值