Ubuntu 16.04 LTS LVM Root Volume Reaches 100 Percent

📖 ~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

Critical processes fail to write logs or data, leading to cascading service outages.

Environment & Reproduction

Common on long-lived Ubuntu 16.04 VMs with growing logs, caches, and package artifacts.

Root Cause Analysis

Unchecked growth in root filesystem consumption exhausts allocated logical volume capacity.

Quick Triage

Measure disk usage by path and identify largest consumers before emergency cleanup.

Step-by-Step Diagnosis

Inspect VG free extents, map LV allocations, and confirm filesystem type before resizing operations.

Solution – Primary Fix

Expand underlying disk if needed, extend LVM logical volume, then grow filesystem online or offline.

Solution – Alternative Approaches

Purge obsolete artifacts and move large data paths to separate dedicated volumes.

Verification & Acceptance Criteria

Sustained free-space headroom remains above policy minimum and services operate normally.

Rollback Plan

Revert recent data moves and recover from backups if resizing workflow fails.

Prevention & Hardening

Add capacity alerts and periodic growth forecasting for root volume utilization trends.

Related Errors & Cross-Refs

Often tied to journal growth, container image sprawl, and backup file accumulation.

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

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See LVM administration guides and Linux filesystem resize documentation.