The changes that you have made on the console will reflect only at the block level. You can run the command "lsblk" to see the new size on the instance that you have configured on the console.
lsblk -> This command lists the information about all available or the specified block devices
After you increase the size of an EBS volume, you must use file system–specific commands to extend the file system to the larger size.
The steps to extend your filesystem is well documented on this link below:
 Extending a Linux file system after resizing a volume - Identifying the file system for a volume - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html#identify-linux-file-system
Moving on, there is no difference between sda1 and xvda1, they are exactly same. When you run your EC2 instance on a Xen hypervisor the xvd* are simply the Xen disk storage devices, therefore they appear instead of sda, etc.
Thanks a lot.
I was able to solve the problem, using your advice and the article you mentioned.
- asked 4 months ago
- How can I avoid placing tasks on Amazon ECS container instances with Amazon Linux 1 AMIs that don't have enough disk space?AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- How do I increase the size of my EBS volume if I receive an error that there's no space left on my file system?AWS OFFICIALUpdated 25 days ago
- EXPERTpublished 10 months ago