ch11 · operator · 110-150 min
storage, LVM, and production packet
Read block devices, mounts, filesystems, LVM layers, snapshots, and evidence packets for risky work.
You can plan storage work with proof points before any destructive command.
shows: How a mount point sits on a filesystem, on an LV stacked through VG and PV onto a block device, plus where growth and snapshots act.
does not prove: It is a schematic of the relationships, not evidence of your host's actual layout — only lsblk, findmnt, blkid, and lvs output prove that.
Lessons in this chapter
-
ch11/l01
Devices, filesystems, and mounts
lsblk -fSeparate block devices from filesystems and mount points. -
ch11/l02
LVM layers and growth plan
lvs -aUnderstand PV -> VG -> LV before extending storage. -
ch11/l03
Snapshots, rollback, and final evidence
lvs -a -o +devicesPlan snapshot work around capacity risk and restore path.
production troubleshooting packet
Assemble a final packet for a simulated Linux incident: prompt state, path evidence, file/log evidence, service state, network ladder, resource readout, and storage risk note.
DeliverableA single incident packet with commands, observations, conclusions, and next least-invasive action.
Success criteria
- Every conclusion cites command evidence.
- Risky commands are plans, not casual execution.
- Recall targets are ready for Terminal Drill review.
Storage & LVM
After you can draw device -> filesystem -> mount -> LVM relationships from evidence.