Programming/Linux/Working with AWS instances - Revision history

Admin at 22:36, 14 December 2023

2023-12-14T22:36:16Z

← Older revision		Revision as of 22:36, 14 December 2023
Line 21:		Line 21:
	</pre>		</pre>

	This information comes from [https://stackoverflow.com/questions/62146336/new-volume-in-ec2-instance-not-reflecting \| this Stack Overflow post].		This information comes from [https://stackoverflow.com/questions/62146336/new-volume-in-ec2-instance-not-reflecting\|this Stack Overflow post].

Admin at 22:35, 14 December 2023

2023-12-14T22:35:58Z

← Older revision		Revision as of 22:35, 14 December 2023
Line 21:		Line 21:
	</pre>		</pre>

	This information comes from [https://stackoverflow.com/questions/62146336/new-volume-in-ec2-instance-not-reflecting\|this Stack Overflow post].		This information comes from [https://stackoverflow.com/questions/62146336/new-volume-in-ec2-instance-not-reflecting \| this Stack Overflow post].

Admin at 22:35, 14 December 2023

2023-12-14T22:35:17Z

← Older revision		Revision as of 22:35, 14 December 2023
Line 20:		Line 20:
	df -h		df -h
	</pre>		</pre>

			This information comes from [https://stackoverflow.com/questions/62146336/new-volume-in-ec2-instance-not-reflecting\|this Stack Overflow post].

Admin at 22:34, 14 December 2023

2023-12-14T22:34:31Z

← Older revision		Revision as of 22:34, 14 December 2023
Line 7:		Line 7:

	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		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]		* [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html\|Making an Amazon EBS volume available for use on Linux]
	* [\|Extending a Linux file system after resizing a volume]		* [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html\|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:		However, as a quick solution, run the following two commands, in the given order, after resizing a volume:

Admin: 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

 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]..."

2023-12-14T22:34:05Z

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]..."

New page

=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]

However, as a quick solution, run the following two commands, in the given order, after resizing a volume:
<pre>
sudo growpart /dev/xvda 1
sudo resize2fs /dev/xvda1
</pre>

The volume size changes should then be reflected in
<pre>
df -h
</pre>