Ubuntu 18.04 LTS – LVM volume reaches 100 percent causing service failures – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Applications cannot write data, causing transaction failures and unstable service behavior.

Environment & Reproduction

Often seen on rapidly growing logs, databases, or backup directories without quotas.

Root Cause Analysis

Logical volume consumed available extents and filesystem has no free space remaining.

Quick Triage

Identify largest growth paths and free emergency space to restore minimal operations.

Step-by-Step Diagnosis

Check vg/lv usage, filesystem allocation, and top directory consumers by growth rate.

Solution – Primary Fix

Extend logical volume and filesystem safely, then enforce retention or quota controls.

Solution – Alternative Approaches

Migrate high-growth paths to dedicated volume with independent capacity management.

Verification & Acceptance Criteria

Free space returns above operational threshold and write failures cease.

Rollback Plan

If extension fails, revert from snapshot and restore previous mount layout.

Prevention & Hardening

Set predictive capacity alerts and recurring cleanup automation for growth hotspots.

Related Errors & Cross-Refs

Related to journald bloat, runaway temp files, and unbounded backup staging.

Related tutorial: View the step-by-step tutorial for Ubuntu 18.04 LTS.

View all Ubuntu 18.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

LVM administration documentation and Ubuntu disk capacity planning best practices.