3.5. Storage Management
💡 First Principle: Storage management is ongoing, not a one-time setup task. Drives fill, performance degrades, data deduplicates, and quotas enforce policy. The difference between proactive and reactive storage management is the difference between a planned maintenance window and an emergency service outage because a drive is 100% full.
Why this matters in production: Storage failures are almost always predictable. A drive that hits 100% capacity doesn't fail silently — it crashes running services, corrupts open files, and fills application logs with errors. Administrators who monitor capacity trends and I/O latency catch these problems at 75% utilisation, not at 100%. The sections below cover how storage gets allocated (provisioning and partitioning) and how it gets watched (monitoring and optimisation). Together they represent the operational discipline that separates environments that have scheduled storage expansions from environments that have 3 AM emergencies.
⚠️ Exam Trap: The exam distinguishes between storage provisioning (allocating and formatting capacity) and storage management (ongoing monitoring, quota enforcement, deduplication). Questions that describe a disk-full scenario are almost always testing whether you identify the monitoring failure, not just the capacity issue.
