Affected versions: 20.04 LTS

📖 ~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 was expanded at hypervisor level but filesystem capacity remains unchanged, risking application outages from low space.

Environment & Reproduction

Typical in virtualized Ubuntu hosts where partition, PV, LV, and filesystem extension steps were only partially completed.

Root Cause Analysis

Storage stack layers are independent; increasing block device size alone does not automatically propagate to LVM and filesystem layers.

Quick Triage

Confirm device growth, partition map, and free extents before issuing resize commands to avoid incorrect target selection.

Step-by-Step Diagnosis

Compare lsblk, pvs, vgs, and lvs output to pinpoint where capacity propagation stopped in the stack.

Illustrative mockup for ubuntu-20-04-lts — lvm_extend_problem
PV size not recognized after virtual disk growth — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Resize partition if needed, run pvresize, extend logical volume, then grow filesystem with tool matching ext4 or xfs.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

Illustrative mockup for ubuntu-20-04-lts — lvm_pvresize_fix
Extended logical volume and filesystem — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Add a new PV and extend VG, rebalance data paths, or migrate to larger volumes using snapshot-assisted workflows.

Verification & Acceptance Criteria

Filesystem reports expected new capacity and application writes proceed normally without space-related errors.

Rollback Plan

If extension fails mid-process, restore from snapshot and reattempt with verified device map and maintenance downtime.

Prevention & Hardening

Automate expansion runbooks, validate storage topology pre-change, and monitor capacity trendlines before emergency thresholds.

Related storage issues include inode exhaustion, thin pool overcommit, and mount failures after volume manipulation.

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

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Use LVM man pages, Ubuntu storage administration guidance, and virtualization platform docs for safe disk expansion.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.