Ubuntu 18.04 LTS LVM volume extension not reflected in filesystem

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

Disk alerts persist despite completed logical volume extension.

Environment & Reproduction

Ext4 or XFS filesystem on LVM after online capacity increase.

Root Cause Analysis

Filesystem growth step omitted after block device expansion.

Quick Triage

Compare lvdisplay and df outputs to confirm mismatch.

Step-by-Step Diagnosis

Identify filesystem type and validate resize command prerequisites.

Solution – Primary Fix

Run correct grow command and verify mount-level capacity update.

Solution – Alternative Approaches

Perform offline resize from maintenance window for high-risk systems.

Verification & Acceptance Criteria

df reflects new size and write tests succeed.

Rollback Plan

Restore from snapshot if unexpected filesystem corruption appears.

Prevention & Hardening

Automate LV extension workflows to include filesystem growth step.

Related Errors & Cross-Refs

Differentiate partition table changes from LVM-managed volumes.

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 and filesystem resize documentation for Ubuntu 18.04.