EBS Volume Resize Not Reflecting in EC2? Here's Your Fix
AWS | Jun 23, 2026 | 12 views
We've all been there. You make the decision to upgrade your EBS volume through the AWS Console, eagerly wait for the "volume modification" to complete, and then SSH into your instance... only to run df -h and see the same old storage size staring back at you.
Don't panic. Your data isn't lost, and AWS isn't broken.
Here's the truth that trips up even seasoned engineers: AWS only expands the raw, physical disk. Your operating system has no idea this happened. You need to manually tell it to claim the new space.
Follow this checklist for a seamless expansion.
The Step-by-Step Playbook
1. Verify the Drive Size
First, let's see what your Linux instance actually sees. Run:
lsblk
What to look for:
- The main disk (usually
nvme0n1for Nitro instances orxvdafor older Xen) will show the new size - The partition (e.g.,
nvme0n1p1) will still show the old size
If this is the case, you're ready for step 2.
2. Resize the Partition
This step tells the partition table to use the newly available space.
For Nitro instances (NVMe):
sudo growpart /dev/nvme0n1 1
Pro tip: The 1 represents partition number 1. Always verify with lsblk first.
For older Xen instances (XVD):
sudo growpart /dev/xvda 1
3. Resize the File System
Now the partition knows it's bigger—we need to tell the file system to expand into it.
If you're using ext4 (most common):
sudo resize2fs /dev/nvme0n1p1
(Note: adjust the device path to match your partition)
If you're using xfs:
sudo xfs_growfs -d /
(The -d flag works because / is usually the root mount point)
4. Verify Your Success
Finally, confirm the operating system has claimed the new space:
df -h
You should now see the expanded size reflected.
Quick "I Just Want to Get This Done" Command Summary
If your disk is an NVMe root volume and you've just expanded it:
sudo growpart /dev/nvme0n1 1
sudo resize2fs /dev/nvme0n1p1
df -h
One More Pro Tip
Always remember the difference between:
lsblk— shows the raw block device sizedf -h— shows the filesystem usable size
If lsblk shows the new size but df -h doesn't, you haven't completed steps 2 and 3. If lsblk still shows the old size, you may need to double-check your EBS modification in the AWS Console or wait a few extra minutes for the change to fully propagate.
Final Thoughts
This is one of those "once you know, you know" solutions. Yes, it's an extra step. Yes, it's manual. But understanding it means you'll never be caught off guard again.
For production workloads, always ensure you have a solid backup or snapshot before performing these operations. Resizing is generally safe, but it never hurts to be cautious.
No comments yet.