Back to all scenarios
Scenario #389
Storage
Kubernetes v1.24, LVM-based CSI
Overprovisioned Thin Volumes Hit Underlying Limit
Thin-provisioned volumes ran out of physical space, affecting all pods.
Find this helpful?
What Happened
Overcommitted volumes filled up the disk pool.
Diagnosis Steps
- 1df on host showed 100% disk.
- 2LVM pool full, volumes became read-only.
Root Cause
No enforcement of provisioning limits.
Fix/Workaround
• Resized physical disk and added monitoring.Lessons Learned
Thin provisioning must be paired with storage usage enforcement.
How to Avoid
- 1Monitor volume pool usage.
- 2Set quotas or alerts for overcommit.