In this lesson, you will learn how Btrfs treats physical storage as a flexible, unified pool where subvolumes act as independent, manageable file systems.
The Btrfs Philosophy
Unlike traditional systems where you must pre-allocate fixed partitions, Btrfs manages storage as a single "pool." Think of a Btrfs volume as a massive storage container that doesn't care about partition boundaries. Once you format a device (or multiple devices) as Btrfs, the entire pool is available to every file and folder inside.
Organizing with Subvolumes
Within this pool, you use subvolumes. A subvolume is a POSIX-compliant file tree that acts like a separate partition, but without the rigid size limits. You can create as many subvolumes as you need, and they will all share the total free space of the underlying pool.
For example, you might organize your system like this:
# Create subvolumes for different data categories
sudo btrfs subvolume create /mnt/data/home
sudo btrfs subvolume create /mnt/data/backups
sudo btrfs subvolume create /mnt/data/logs
The Power of Snapshots
Because Btrfs handles storage logically, it can create snapshots. A snapshot is simply a subvolume that shares the same data blocks as the original. When you create a snapshot, it is instantaneous because Btrfs doesn't copy the actual files; it just creates a new reference point. If you modify a file in your home directory, the snapshot remains unchanged because Btrfs uses a "Copy-on-Write" mechanism to preserve the original data blocks.
This architecture allows you to roll back your entire system or specific data folders in seconds. You are essentially organizing your storage into "layers" that can be duplicated or reverted without ever having to worry about resizing a partition or running out of space on one specific disk while others sit empty.
Key Takeaway: Btrfs replaces rigid partition management with a flexible pool-based architecture, allowing you to create limitless subvolumes and instantaneous snapshots that all share the same storage resources.