Difference between revisions of "Programming/Linux/Working with AWS instances"

From Thalesians Wiki
(Created page with "=Elastic storage= Once you have changed the size of a volume using AWS's elastic storage, the changes won't be immediately reflected in <pre> df -h </pre> New volumes should be formatted to be accessible. Resized existing volumes should also be modified (resized) from inside the operating systems. A detailed discussion of these aspects can be found in * [|Making an Amazon EBS volume available for use on Linux] * [|Extending a Linux file system after resizing a volume]...")
(No difference)

Revision as of 22:34, 14 December 2023

Elastic storage

Once you have changed the size of a volume using AWS's elastic storage, the changes won't be immediately reflected in

df -h

New volumes should be formatted to be accessible. Resized existing volumes should also be modified (resized) from inside the operating systems. A detailed discussion of these aspects can be found in

  • [|Making an Amazon EBS volume available for use on Linux]
  • [|Extending a Linux file system after resizing a volume]

However, as a quick solution, run the following two commands, in the given order, after resizing a volume:

sudo growpart /dev/xvda 1
sudo resize2fs /dev/xvda1

The volume size changes should then be reflected in

df -h