Recovery and Expansion of a 100% Full LVM Disk

LVM and filesystem resize commands require a small amount of free space to write metadata. If the disk is truly at 100%, these commands may fail.

Action	Command
Clear Package Cache	`yum clean all`
Truncate Logs	`find /var/log -type f -name "*.log" -exec truncate -s 0 {} +`
Clear Temp Files	`rm -rf /tmp/*`

Note: Truncating logs is safer than deleting them, as it preserves file descriptors and avoids "file in use" issues.

Phase 2: Physical Volume (PV) Expansion

Before the Operating System can see the extra space, you must update the LVM Physical Volume layer.

If you increased the size of an existing disk (e.g., /dev/xvda):

If you attached a second disk (e.g., /dev/xvdb):

Now that the Volume Group has free space, you must tell the Logical Volume (the "container") to expand.

The final step is to grow the actual filesystem so the OS recognizes the new capacity. Identify your filesystem type first using df -T.

XFS must be grown using the mount point.

Ext4 must be grown using the device path.

Level	Command	What to check
Physical	`lsblk`	Ensure the parent disk reflects the total hardware size.
LVM	`lvs`	Ensure `centos-root` size matches your target.
Filesystem	`df -h /`	Ensure "Avail" is positive and "Use%" is below 100%.