2.2. Storage and Device Management

Storage management is where many Linux administrators make their most consequential mistakes. A wrong fdisk decision can destroy a partition table; a missed --force flag when extending a filesystem can leave data inaccessible. The stakes are high, which is why CompTIA weights this topic heavily within the System Management domain.

The storage stack has a clear hierarchy: physical disks → partitions (or raw disks) → optional LVM layer → filesystems → mount points. Each layer depends on the ones below. Understanding this stack means you can troubleshoot storage problems by isolating which layer is failing.

💡 First Principle: Every storage layer is independent — partitioning does not format, formatting does not mount, and mounting does not persist across reboots unless configured in /etc/fstab. You must configure each layer explicitly.

⚠️ Common Misconception (M2): Candidates sometimes reach for chmod 777 as a quick fix when storage permission problems arise. The correct approach depends on the layer — an ACL problem requires setfacl, an SELinux context problem requires restorecon, and a mount option problem requires updating /etc/fstab. Always diagnose before applying.