upgrade
upgrade

🖲️Operating Systems

File System Types

Study smarter with Fiveable

Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.

Get Started

Why This Matters

File systems are the invisible architecture that determines how your operating system stores, retrieves, and protects data. When you're tested on this material, you're not just being asked to name file systems—you're being asked to understand why different systems exist and what trade-offs they make. The concepts at play include journaling for crash recovery, metadata management, storage efficiency, and platform-specific optimization.

Think of file systems as the organizational strategy for your hard drive. Some prioritize compatibility across devices, others prioritize data integrity through journaling, and newer systems optimize for flash storage characteristics. Don't just memorize which OS uses which file system—know what problem each one solves and why an administrator might choose one over another.


Legacy and Compatibility-Focused Systems

These file systems prioritize broad compatibility over advanced features. They're the "universal translators" of storage—readable by almost anything, but with significant limitations.

The trade-off: maximum portability comes at the cost of modern features like journaling, large file support, and security.

FAT (File Allocation Table)

  • Universally compatible—readable by virtually every operating system, making it the default choice for USB drives and memory cards
  • File Allocation Table structure tracks file locations in a simple table, but this design causes fragmentation as files are created and deleted
  • Size limitations cap files at 4GB and volumes at 2TB (FAT32), making it unsuitable for modern large-file workflows

ReiserFS

  • Small file optimization—designed specifically for efficient handling of large numbers of small files through tail packing
  • Dynamic inode allocation creates inodes on demand rather than pre-allocating, improving space efficiency
  • Legacy status—while historically significant for Linux, it's rarely deployed in new systems today

Compare: FAT vs. ReiserFS—both are largely legacy systems, but for opposite reasons. FAT survives due to universal compatibility despite poor performance; ReiserFS offered excellent small-file performance but lost relevance as other systems caught up. If an FRQ asks about cross-platform storage, FAT is your answer.


Journaling File Systems for Data Integrity

Journaling file systems maintain a log (journal) of changes before committing them to disk. If the system crashes mid-write, the journal enables recovery without full disk scans.

The mechanism: write intentions to the journal first, then execute. On crash recovery, replay or discard incomplete transactions.

NTFS (New Technology File System)

  • Windows standard since Windows NT, supporting volumes up to 16 exabytes and files up to 16TB in practice
  • Journaling and security features include file-level permissions (ACLs), encryption (EFS), and transaction logging for crash recovery
  • Advanced capabilities like disk quotas, sparse files, and hard links make it suitable for enterprise Windows environments

ext4 (Fourth Extended File System)

  • Linux default for most distributions, supporting files up to 16TB and volumes up to 1 exabyte
  • Extents-based allocation replaces the block mapping of ext3, reducing fragmentation and improving large-file performance
  • Backward compatible with ext3 and ext2, allowing administrators to upgrade file systems without reformatting

XFS

  • High-performance parallel I/O—designed by SGI for media and enterprise workloads requiring massive throughput
  • Scalability focus supports file systems up to 8 exabytes with efficient handling of large files and concurrent access
  • Dynamic inode allocation and delayed allocation optimize space usage and write performance

JFS (Journaled File System)

  • Low CPU overhead—IBM designed JFS for efficiency, making it suitable for systems with limited processing power
  • Extent-based allocation groups contiguous blocks for better sequential read/write performance
  • Enterprise heritage from IBM's AIX means robust large-volume support, though it's less common in modern Linux deployments

Compare: ext4 vs. XFS—both are journaling file systems for Linux, but ext4 prioritizes general-purpose reliability while XFS optimizes for parallel I/O and large files. For an exam question about a video editing workstation on Linux, XFS is the better answer.


Platform-Specific Optimized Systems

These file systems are tightly integrated with their parent operating systems, trading cross-platform compatibility for deep OS integration and optimized performance.

The principle: when you control both the OS and the file system, you can optimize for specific hardware and use cases.

HFS+ (Hierarchical File System Plus)

  • macOS legacy standard—supported large files and journaling before APFS replaced it
  • Case handling flexibility allows both case-sensitive and case-insensitive configurations depending on installation choices
  • Metadata-rich design stores extensive file attributes for Spotlight search and Finder integration

APFS (Apple File System)

  • Flash/SSD optimized—Apple designed APFS specifically for solid-state storage characteristics like wear leveling
  • Space sharing allows multiple volumes to share a single pool of storage, dynamically allocating space as needed
  • Native encryption and snapshots provide security and Time Machine backup support at the file system level

Compare: HFS+ vs. APFS—both are Apple-exclusive, but APFS represents a ground-up redesign for flash storage rather than spinning disks. Key exam distinction: APFS supports cloning (instant file copies that share storage until modified) and snapshots natively.


Advanced Copy-on-Write Systems

Copy-on-write (COW) file systems never overwrite data in place. Instead, they write new data to a different location and update pointers. This enables powerful features like snapshots and self-healing.

The mechanism: modifications create new blocks rather than overwriting existing ones, preserving previous states automatically.

ZFS (Zettabyte File System)

  • Combined volume manager and file system—ZFS handles both storage pooling and file organization in one integrated system
  • Data integrity verification uses checksums on all data and metadata, automatically detecting and repairing corruption (self-healing)
  • Enterprise-grade features include snapshots, clones, compression, deduplication, and native RAID (RAID-Z) without hardware controllers

Btrfs (B-tree File System)

  • Linux-native COW system—designed as a modern alternative to ext4 with ZFS-like features under the GPL license
  • Subvolumes and snapshots allow flexible partitioning and instant backups without traditional volume management
  • Built-in RAID and checksumming provide data protection, though RAID 5/6 implementations remain experimental

Compare: ZFS vs. Btrfs—both are copy-on-write systems with snapshots and checksumming, but ZFS is more mature and feature-complete while Btrfs is GPL-licensed and Linux-native. For exam questions about data integrity and self-healing storage, ZFS is the canonical example.


Quick Reference Table

ConceptBest Examples
Universal compatibilityFAT
Windows standard with securityNTFS
Linux general-purposeext4
High-performance parallel I/OXFS
Flash/SSD optimizationAPFS
Copy-on-write with self-healingZFS, Btrfs
Integrated volume managementZFS
Apple ecosystemHFS+, APFS
Low CPU overheadJFS
Small file optimization (legacy)ReiserFS

Self-Check Questions

  1. Which two file systems use copy-on-write architecture and support automatic data integrity verification through checksumming?

  2. A system administrator needs to format a USB drive that will be used across Windows, macOS, and Linux machines. Which file system should they choose, and what limitation will they face?

  3. Compare ext4 and XFS: both are Linux journaling file systems, but when would you specifically recommend XFS over ext4?

  4. What distinguishes APFS from its predecessor HFS+, and why did Apple make this change?

  5. FRQ-style prompt: Explain how journaling improves crash recovery compared to non-journaling file systems. Identify two file systems that implement journaling and describe one additional feature each provides beyond basic journaling.