CentOS Stream 10 – Common Problem 032 – Diagnosis and Fix

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

After cloud disk resize, lvextend reports insufficient free extents.

Environment & Reproduction

Hosts where PV was not resized after underlying block device grew.

cat /etc/os-release
uname -r
rpm -qa | grep 

Root Cause Analysis

pvresize was skipped, leaving the PV size stale.

Quick Triage

Confirm package, network, SELinux and firewall state.

lsblk
vgs
pvs
lvs

Step-by-Step Diagnosis

Drill into storage/lvm-extend state and recent journal entries to isolate the failure.

pvdisplay /dev/sda2
vgdisplay vg0

Solution – Primary Fix

Apply the standard remediation for storage/lvm-extend on CentOS Stream 10.

sudo pvresize /dev/sda2
sudo lvextend -r -L +10G /dev/vg0/root

Solution – Alternative Approaches

Use growpart then pvresize in cloud-init for automatic growth.

Verification & Acceptance Criteria

Validate the fix with positive functional checks before closing.

df -h
lvs --units g

Rollback Plan

Revert to the previous known-good configuration if the fix regresses.

sudo lvreduce -r -L -10G /dev/vg0/root  # only with backup

Prevention & Hardening

Codify the fix in configuration management and add monitoring.

cloud-init growpart and resize_rootfs modules.

Related Errors & Cross-Refs

XFS shrink limitations and PV metadata corruption.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

LVM administrator guide.