filesystem · shipping · also file system

Filesystem

A filesystem organizes files and their metadata and implements operations for naming, accessing and managing them.

Related Observatory article: Read on hesela.com

A filesystem is an implementation, while file storage describes an access model. A disk-backed filesystem also has a stored representation; these are related meanings, not a requirement that every filesystem use a disk format. [1] [2]

Linux VFS provides a common interface across implementations. Its in-memory dentries can associate pathname components with inode objects; the filesystem supplies operations behind that interface. A shared API does not make those implementations identical. [2]

Local filesystems can use directly attached or SAN-provided block storage. Network filesystems instead let clients access files through a server protocol; the client need not see the server's underlying block layout. [4]

Tmpfs stores files in virtual memory and may use swap when enabled. Unmounting its instance loses its contents. Unlike a regular filesystem placed on a RAM block device, tmpfs does not depend on such a block layer. Swap use does not preserve the files after unmounting. [3]

For persistent storage, file contents and the directory entry naming the file have separate synchronization requirements. Linux fsync() on a file does not necessarily persist its containing directory entry; that requires a directory sync as well. [5]

Persistence testing is asymmetric evidence. In Pillai et al.'s OSDI 2014 study, BOB replayed selected block-write orderings while respecting barriers. A recovered counterexample could refute a persistence property, but successful tested states could not prove it for all executions. The reported filesystem/configuration observations are historical, not guarantees for current kernels. [6]

Relations

related
File storage, Filesystem block, Inode, Dentry

Limitations

  • Access to the same block volume from several hosts does not provide coordinated shared writes; a shared-disk filesystem needs suitable cluster coordination. [4]

Citations

  1. SNIA Dictionary: file system (accessed 2026-11-15)
  2. Linux 6.12: Overview of the Linux Virtual File System (accessed 2026-11-15)
  3. Linux 6.12: Tmpfs, virtual-memory storage, swap and unmount behavior (accessed 2026-11-15)
  4. Red Hat Enterprise Linux 8: local, network and shared-storage filesystems (accessed 2026-11-15)
  5. Linux man-pages: fsync(2), file and directory synchronization (accessed 2026-11-15)
  6. Pillai et al. (OSDI 2014): All File Systems Are Not Created Equal, section 2.2, testing method and limits (accessed 2026-11-15)
Sources & caveats
  • Terminology and documentation synthesis; Linux implementation examples are scoped to kernel documentation version 6.12, not a universal filesystem architecture.
  • No native filesystem or crash-recovery experiment was performed for this definition.
  • Persistence context: https://hesela.com/analyses/atomic-rename-directory-durability/#filesystem-foundation

JSON: /data/terms/filesystem.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Filesystem. Hesela. 2026-11-15. https://hesela.dev/terms/filesystem/