Choose the evidence that separates free space, mount state, repair safety, redundancy, and request latency. A storage command succeeding is not enough to put a writer back in service.
Review these lessons
- Linux disk pressure: explain missing space before deleting application data
- Linux filesystem expansion: follow the block device to the mounted filesystem
- Linux read-only filesystem incidents: preserve evidence before repair
- Linux mount boot contracts: prevent a service from writing into an empty mountpoint
- Linux md RAID recovery: identify the failed member before rebuilding
- Linux I/O latency: distinguish device wait from an application queue
Other checks
Common Mistakes
- Do not diagnose a storage incident from a single utilization figure.
- Do not mistake a mountpoint directory for its expected filesystem.