{
  "slug": "filesystem",
  "term": "Filesystem",
  "aliases": [
    "file system"
  ],
  "definition": "A filesystem organizes files and their metadata and implements operations for naming, accessing and managing them.",
  "note": "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. [snia-filesystem] [linux-vfs-612]\n\nLinux 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. [linux-vfs-612]\n\nLocal 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. [rhel-filesystems]\n\nTmpfs 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. [linux-tmpfs-612]\n\nFor 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. [linux-fsync]\n\nPersistence 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. [pillai-osdi2014]",
  "provenance": [
    "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"
  ],
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Access to the same block volume from several hosts does not provide coordinated shared writes; a shared-disk filesystem needs suitable cluster coordination.",
      "citationIds": [
        "rhel-filesystems"
      ]
    }
  ],
  "related": [
    "file-storage",
    "filesystem-block",
    "inode",
    "dentry"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "citations": [
    {
      "id": "snia-filesystem",
      "title": "SNIA Dictionary: file system",
      "url": "https://www.snia.org/education/online-dictionary/term/file-system",
      "accessed": "2026-11-15"
    },
    {
      "id": "linux-vfs-612",
      "title": "Linux 6.12: Overview of the Linux Virtual File System",
      "url": "https://docs.kernel.org/6.12/filesystems/vfs.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "linux-tmpfs-612",
      "title": "Linux 6.12: Tmpfs, virtual-memory storage, swap and unmount behavior",
      "url": "https://docs.kernel.org/6.12/filesystems/tmpfs.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "rhel-filesystems",
      "title": "Red Hat Enterprise Linux 8: local, network and shared-storage filesystems",
      "url": "https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_file_systems/overview-of-available-file-systems_managing-file-systems",
      "accessed": "2026-11-15"
    },
    {
      "id": "linux-fsync",
      "title": "Linux man-pages: fsync(2), file and directory synchronization",
      "url": "https://man7.org/linux/man-pages/man2/fsync.2.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "pillai-osdi2014",
      "title": "Pillai et al. (OSDI 2014): All File Systems Are Not Created Equal, section 2.2, testing method and limits",
      "url": "https://research.cs.wisc.edu/wind/Publications/alice-osdi14.pdf",
      "accessed": "2026-11-15"
    }
  ]
}
