Don't Panic: Linux Storage

Linux storage is the collection of layers that turns a disk, a virtual disk, or a remote logical unit into files at a directory. This sounds like one job because applications only see paths. Linux keeps the useful thing visible at the top and the important thing visible underneath several other things.

Start at a path such as /var/lib. A mount point attaches a file system to that directory, and the file system supplies files, directories, allocation, and metadata. Beneath it might be an LVM logical volume, a block device allocated from a volume group. That group draws extents from physical volumes, which may be partitions or whole devices. The same data can therefore have several names. They are colleagues, not aliases.

The useful mental model is a stack, not a disk. findmnt starts with the path and identifies the mounted file system. lsblk follows the block-device family tree. blkid identifies file systems, while pvs, vgs, and lvs describe the LVM layer. Each command answers a different question. Asking df whether a volume group has free extents is like asking a street map whether the building has spare keys. It has a map. It is not that map.

This distinction matters during change and failure. Extending a logical volume changes a lower boundary but does not necessarily grow its file system. A file system can run out of inodes while data blocks remain. A thin pool can exhaust metadata while its data usage looks tolerable. Mounting over a nonempty directory hides the entries underneath, which is unsettling but not evidence that they vanished into a storage dimension.

The surprise is that the safest action is often to stop and trace. Before partitioning, formatting, resizing, or removing anything, confirm the device size, model, serial, transport, active holders, and mounted descendants. Use durable identifiers for persistent mounts because short discovery-order device names can change. Then verify not only that a command succeeded, but that the application can read and write through the intended mount.

Read the Introduction for the complete layer model and the decisions around partitions, LVM, file systems, and mounts. Use the Cheatsheet when an incident demands a specific diagnostic view. The Reference tab carries the official procedures for LVM, device management, and kernel behavior. The quiz checks whether the boundaries have become less mysterious, which is the closest storage gets to being polite.