Filesystem in Userspace

Short description: Software interface for Unix-like systems

Filesystem in UserspaceWritten in| C

|

Operating system| Unix, Unix-like
Type| File system driver
License| GPL for Linux kernel part, LGPL for Libfuse, Simplified BSD on FreeBSD, ISC license on OpenBSD; proprietary for macOS
Website| github.com/libfuse/libfuse

Filesystem in Userspace (FUSE) is a software interface for Unix and Unix-like computer operating systems that lets non-privileged users create their own file systems without editing kernel code. This is achieved by running file system code in user space while the FUSE module provides only a bridge to the actual kernel interfaces.

FUSE is available for Linux, FreeBSD, OpenBSD, NetBSD (as puffs), OpenSolaris, Minix 3, macOS,[1] and Windows.[2]

FUSE is free software originally released under the terms of the GNU General Public License and the GNU Lesser General Public License.

## Contents

* 1 History
* 2 Operation and usage
* 3 Applications
* 3.1 On-disk file systems
* 3.2 Layering file systems
* 3.3 Archive and backup file systems
* 3.4 Remote/distributed file system clients
* 3.5 Other
* 4 See also
* 5 References
* 6 External links

## History

The FUSE system was originally part of AVFS (A Virtual Filesystem), a filesystem implementation heavily influenced by the translator concept of the GNU Hurd.[3] It superseded Linux Userland Filesystem, and provided a translational interface using `lufis` in libfuse1.

FUSE was originally released under the terms of the GNU General Public License and the GNU Lesser General Public License, later also reimplemented as part of the FreeBSD base system[4] and released under the terms of Simplified BSD license. An ISC-licensed re-implementation by Sylvestre Gallon was released in March 2013,[5] and incorporated into OpenBSD in June 2013.[6]

FUSE was merged into the mainstream Linux kernel tree in kernel version 2.6.14.[7]

The userspace side of FUSE, the libfuse library, generally followed the pace of Linux kernel development while maintaining "best effort" compatibility with BSD descendants. This is possible because the kernel FUSE reports its own "feature levels", or versions. The exception is the FUSE fork for macOS, OSXFUSE, which has too many differences for sharing a library.[8] A break in libfuse history is libfuse3, which includes some incompatible improvements in the interface and performance, compared to the older libfuse2 now under maintenance mode.[9]

As the kernel-userspace protocol of FUSE is versioned and public, a programmer can choose to use a different piece of code in place of libfuse and still communicate with the kernel's FUSE facilities. On the other hand, libfuse and its many ports provide a portable high-level interface that may be implemented on a system without a "FUSE" facility.

## Operation and usage

A flow-chart diagram showing how FUSE works: Request from userspace to list files (ls -l /tmp/fuse) gets redirected by the Kernel through VFS to FUSE. FUSE then executes the registered handler program (./hello) and passes it the request (ls -l /tmp/fuse). The handler program returns a response back to FUSE which is then redirected to the userspace program that originally made the request.

To implement a new file system, a handler program linked to the supplied `libfuse` library needs to be written. The main purpose of this program is to specify how the file system is to respond to read/write/stat requests. The program is also used to mount the new file system. At the time the file system is mounted, the handler is registered with the kernel. If a user now issues read/write/stat requests for this newly mounted file system, the kernel forwards these IO-requests to the handler and then sends the handler's response back to the user.

Unmounting a FUSE-based file system with the `fusermount` command

FUSE is particularly useful for writing virtual file systems. Unlike traditional file systems that essentially work with data on mass storage, virtual filesystems don't actually store data themselves. They act as a view or translation of an existing file system or storage device.

In principle, any resource available to a FUSE implementation can be exported as a file system.

## Applications

### On-disk file systems

Conventional on-disk file systems can be implemented in user space with FUSE, e.g. for compatibility or licensing reasons.

* Linear Tape File System: Allows files stored on magnetic tape to be accessed in a similar fashion to those on disk or removable flash drives.
* NTFS-3G and Captive NTFS, allowing access to NTFS filesystems.
* retro-fuse: retro-fuse is a user-space filesystem that provides a way to mount filesystems created by ancient Unix systems on modern OSes. The current version of retro-fuse supports mounting filesystems created by Fifth, Sixth and Seventh Edition of Research Unix from BTL, as well as 2.9BSD and 2.11BSD based systems.

### Layering file systems

FUSE filesystems can create a view of an underlying file system, transforming the files in some way.

* EncFS: Encrypted virtual filesystem
* FuseCompress, gzipfs, Fuse-ZIP, CompFUSEd: Compressed virtual filesystems
* Archive filesystems may also perform this task

### Archive and backup file systems

FUSE filesystems can expose the contents of archives or backup sets without having to first extract them.

* archivemount
* Atlas (Rubrik backup software): Immutable, distributed filesystem used by Rubrik Cloud Data Management data protection applications
* Borg (backup software): Deduplicating backup program that allows backup archives to be mounted as FUSE filesystems.
* Restic: Free, fast, efficient and secure backup software uses FUSE to be able to browse all of your backup snapshots as a regular file system
* SPFS A file system for Spectrum Protect, designed to mount the backup server filespace anywhere on your server, and use the features included from the backup server (encryption, de-duplication, compression, filtering etc). This is a WORM file system.

### Remote/distributed file system clients

* CernVM-FS: A distributed read-only software distribution system, implemented as a POSIX filesystem in user space (FUSE) using HTTP transport, to deliver software in a fast and reliable fashion at global scale.
* CloudStore (formerly, Kosmos filesystem): By mounting via FUSE, existing Linux utilities can interact with CloudStore
* ExpanDrive: A commercial filesystem implementing SFTP/FTP/S3/Swift using FUSE
* FTPFS
* GlusterFS: Clustered Distributed Filesystem having ability to scale up to several petabytes.
* goofys: A FUSE filesystem that allows access to Amazon S3/Microsoft Azure storage with an emphasis on performance.
* google-drive-ocamlfuse is a FUSE filesystem for Google Drive, written in OCaml. It lets you mount your Google Drive on Linux.
* IPFS: A peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files.
* JuiceFS: A distributed POSIX file system built on top of Redis and S3.
* KBFS: A distributed filesystem with end-to-end encryption and a global namespace based on Keybase.io service that uses FUSE to create cryptographically secure file mounts.
* Lustre Cluster filesystem will use FUSE to allow it to run in userspace, so that a FreeBSD port is possible.[10] However, the ZFS-Linux port of Lustre will be running ZFS's DMU (Data Management Unit) in userspace.[11]
* MinFS: MinFS is a fuse driver for Amazon S3 compatible object storage server. MinFS[12] lets you mount a remote bucket (from a S3 compatible object store), as if it were a local directory.
* MooseFS: An open source distributed fault-tolerant file system available on every OS with FUSE implementation (Linux, FreeBSD, NetBSD, OpenSolaris, OS X), able to store petabytes of data spread over several servers visible as one resource.
* Nexfs: A commercial Linux file system that combines Block, File, and S3 compatible Cloud & Object storage into a single pool of POSIX compatible storage.
* ObjectiveFS: Distributed filesystem with object store backend (Amazon S3, Google Cloud Storage or S3-compatible object store) using FUSE
* Rclone can mount a variety of remote / cloud storage with FUSE.
* s3fs: Gives the ability to mount an S3 bucket as if it were a local file system.
* Sector File System: Sector is a distributed file system designed for large amount of commodity computers. Sector uses FUSE to provide a mountable local file system interface.
* SSHFS: Provides access to a remote filesystem through SSH.
* Transmit: A commercial FTP client that also adds the ability to mount WebDAV, SFTP, FTP and Amazon S3 servers as disks in Finder, via MacFUSE.
* WebDrive: A commercial filesystem implementing WebDAV, SFTP, FTP, FTPS and Amazon S3
* WikipediaFS: View and edit Wikipedia articles as if they were real files
* Wuala: Was a multi-platform, Java-based fully OS integrated distributed file system. Using FUSE, MacFUSE and CBFS Connect respectively for file system integration, in addition to a Java-based app accessible from any Java-enabled web browser (service discontinued in 2015).
* IndexFS: A remote file aggregating filesystem with transparent CURL access to distributed files.

### Other

* GVfs: The virtual filesystem for the GNOME desktop
* rvault: A secure and authenticated store for secrets and small documents using envelope encryption with one-time password (OTP) authentication. It uses FUSE to expose the vault as a file system.

## See also

* PUFFS, a similar framework with FUSE compatibility
* 9P (protocol)
* Installable File System
* Dokan Library FUSE Windows compatibility
* Windows Projected File System (ProjFS)

## References

1. ↑ "Home - FUSE for OS X". https://osxfuse.github.io/.
2. ↑ Zissimopoulos, Bill (2021-02-14), billziss-gh/winfsp, https://github.com/billziss-gh/winfsp, retrieved 2021-02-16
3. ↑ "Some technical advantages of the Hurd". May 15, 2011. http://www.draketo.de/light/english/free-software/some-technical-advantages-of-the-hurd.
4. ↑ "WhatsNew/FreeBSD10 - FreeBSD Wiki". https://wiki.freebsd.org/WhatsNew/FreeBSD10.
5. ↑ "openbsd dev - tech - Fuse (and sshfs) support for OpenBSD". http://openbsd.7691.n7.nabble.com/Fuse-and-sshfs-support-for-OpenBSD-td224422.html.
6. ↑ "'CVS: cvs.openbsd.org: src' - MARC". http://marc.info/?l=openbsd-cvs&m=137027468819965.
7. ↑ "file-systems.fuse.devel - FUSE merged to 2.6.14! - msg#00021 - Recent Discussion OSDir.com". http://osdir.com/ml/file-systems.fuse.devel/2005-09/msg00021.html.
8. ↑ "libfuse/libfuse, the reference implementation of the Linux FUSE (Filesystem in Userspace) interface". libfuse. 9 January 2020. https://github.com/libfuse/libfuse.
9. ↑ "libfuse3 ChangeLog". https://github.com/libfuse/libfuse/blob/master/ChangeLog.rst#libfuse-300-2016-12-08.
10. ↑ "Lustre FreeBSD". http://lustre.sev.net.ua/.
11. ↑ "Architecture ZFS for Lustre". Sun Microsystems. http://arch.lustre.org/index.php?title=Architecture_ZFS_for_Lustre.
12. ↑ "minio/minfs". https://github.com/minio/minfs.

## External links

* Develop your own filesystem with FUSE by Sumit Singh
* List of FUSE filesystems
* Documentation/filesystems/fuse.txt documentation in Linux source tree
* WinFSP, a FUSE-like system for Windows (a FUSE compatibility layer is provided for Cygwin)
* Crossmeta FUSE, Port of FUSE to Windows (commercial software)

* v
* t
* e

File systems

* Comparison of file systems
* distributed
* Unix filesystem

Disk|

* ADFS
* AdvFS
* Amiga FFS
* Amiga OFS
* APFS
* AthFS
* bcachefs
* BFS
* Be File System
* Boot File System
* Btrfs
* CVFS
* CXFS
* DFS
* EFS
* Encrypting File System
* Extent File System
* Episode
* ext
* ext2
* ext3
* ext3cow
* ext4
* FFS/FFS2
* FAT
* exFAT
* Files-11
* Fossil
* HAMMER
* HAMMER2
* HFS
* HFS+
* HPFS
* HTFS
* IBM Spectrum Scale
* JFS
* LFS
* MFS
* Macintosh File System
* TiVo Media File System
* MINIX
* NetWare File System
* Next3
* NILFS
* NILFS2
* NSS
* NTFS
* OneFS
* PFS
* QFS
* QNX4FS
* ReFS
* ReiserFS
* Reiser4
* Reliance
* Reliance Nitro
* RFS
* SFS
* SNFS
* Soup (Apple)
* Tux3
* UBIFS
* UFS
* soft updates
* WAPBL
* VxFS
* WAFL
* Xiafs
* XFS
* Xsan
* zFS
* ZFS

Optical disc|

* HSF
* ISO 9660
* ISO 13490
* UDF

Flash memory and SSD|

* APFS
* FAT
* exFAT
* CHFS
* TFAT
* EROFS
* FFS2
* F2FS
* HPFS
* JFFS
* JFFS2
* JFS
* LogFS
* NILFS
* NILFS2
* NVFS
* YAFFS
* UBIFS

Distributed|

* CXFS
* GFS2
* Google File System
* OCFS2
* OrangeFS
* PVFS
* QFS
* Xsan
* more...

NAS|

* AFS (OpenAFS)
* AFP
* Coda
* DFS
* Google File System
* IBM Spectrum Scale
* Lustre
* NCP
* NFS
* POHMELFS
* Hadoop
* SMB (CIFS)
* SSHFS
* more...

Specialized|

* Aufs
* AXFS
* Boot File System
* CDfs
* Compact Disc File System
* cramfs
* Davfs2
* EROFS
* FTPFS
* FUSE
* Lnfs
* LTFS
* NOVA
* MVFS
* SquashFS
* UMSDOS
* OverlayFS
* UnionFS
* WBFS

Pseudo and virtual|

* configfs
* devfs
* debugfs
* kernfs
* procfs
* specfs
* sysfs
* tmpfs
* WinFS

Encrypted|

* eCryptfs
* EncFS
* EFS
* Rubberhose
* SSHFS
* ZFS

Types|

* Clustered
* Global
* Grid
* Self-certifying
* Flash
* Journaling
* Log-structured
* Object
* Record-oriented
* Semantic
* Steganographic
* Synthetic
* Versioning

Features|

* Case preservation
* Copy-on-write
* Data deduplication
* Data scrubbing
* Execute in place
* Extent
* File attribute
* Extended file attributes
* File change log
* Fork
* Links
* Hard
* Symbolic

Access control|

* Access control list
* Filesystem-level encryption
* Permissions
* Modes
* Sticky bit

Interfaces|

* File manager
* File system API
* Installable File System
* Virtual file system

Lists|

* Cryptographic
* Default
* Log-structured

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Filesystem in Userspace. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Filesystem_in_Userspace&oldid=3050777"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template