Using Amazon Webservices - Revision history

Kpe: /* Increasing storage on running instance */

2023-02-06T20:34:49Z

Increasing storage on running instance

← Older revision		Revision as of 22:34, 6 February 2023
Line 60:		Line 60:
	</syntaxhighlight>In case you are using an XFS filesystem a result will occur complaing about a bad superblock. Then you need to grow the root partition using:<syntaxhighlight lang="bash">		</syntaxhighlight>In case you are using an XFS filesystem a result will occur complaing about a bad superblock. Then you need to grow the root partition using:<syntaxhighlight lang="bash">
	sudo xfs_growfs -d /		sudo xfs_growfs -d /
	</syntaxhighlight~~>In case you are using the main volume, instead try<syntaxhighlight lang="bash"~~>		</syntaxhighlight>
	~~sudo growpart /dev/xvda 1~~
	~~sudo resize2fs /dev/xvda1~~		Finally check size is incresed with <syntaxhighlight lang="bash">
	~~</syntaxhighlight>~~Finally check size is incresed with <syntaxhighlight lang="bash">
	df -h		df -h
			</syntaxhighlight>

			=== Variant: Main volume ===
			In case you are using the main volume, instead try
			<syntaxhighlight lang="bash">
			sudo growpart /dev/xvda 1
			sudo resize2fs /dev/xvda1
	</syntaxhighlight>		</syntaxhighlight>

	=== Variant: LUKS volume ===		=== Variant: LUKS volume ===
	Find the crypt partition		Find the crypt partition
			<syntaxhighlight lang="bash">
	ls /dev/mapper/		ls /dev/mapper/
			</syntaxhighlight>

	Fill the space (in above we found crypt-sdf)		Fill the space (in above we found crypt-sdf)
			<syntaxhighlight lang="bash">
	sudo cryptsetup resize /dev/mapper/crypt-sdf		sudo cryptsetup resize /dev/mapper/crypt-sdf
	sudo resize2fs /dev/mapper/crypt-sdf		sudo resize2fs /dev/mapper/crypt-sdf
			</syntaxhighlight>

Kpe: /* Increasing storage on running instance LUKS */

2023-02-06T20:33:20Z

Increasing storage on running instance LUKS

← Older revision		Revision as of 22:33, 6 February 2023
Line 67:		Line 67:
	</syntaxhighlight>		</syntaxhighlight>

	== ~~Increasing storage on running instance~~ LUKS ==		=== Variant: LUKS volume ===
	Find the crypt partition		Find the crypt partition

Kpe: /* Increasing storage on running instance LUKS */

2023-02-06T20:31:42Z

Increasing storage on running instance LUKS

← Older revision		Revision as of 22:31, 6 February 2023
Line 75:		Line 75:

	sudo cryptsetup resize /dev/mapper/crypt-sdf		sudo cryptsetup resize /dev/mapper/crypt-sdf
			sudo resize2fs /dev/mapper/crypt-sdf

Kpe: /* Increasing storage on running instance LUKS */

2023-02-06T20:30:14Z

Increasing storage on running instance LUKS

← Older revision		Revision as of 22:30, 6 February 2023
Line 68:		Line 68:

	== Increasing storage on running instance LUKS ==		== Increasing storage on running instance LUKS ==
			Find the crypt partition

			ls /dev/mapper/

			Fill the space (in above we found crypt-sdf)

	sudo cryptsetup resize /dev/mapper/crypt-sdf		sudo cryptsetup resize /dev/mapper/crypt-sdf

Kpe: /* Increasing storage on running instance */

2023-02-06T20:29:09Z

Increasing storage on running instance

← Older revision		Revision as of 22:29, 6 February 2023
Line 47:		Line 47:

	== Increasing storage on running instance ==		== Increasing storage on running instance ==
	Note that the ~~fowllowing~~ operation can be done while the server is running		Note that the following operation can be done while the server is running

	In the AWS console		In the AWS console
Line 66:		Line 66:
	df -h		df -h
	</syntaxhighlight>		</syntaxhighlight>

			== Increasing storage on running instance LUKS ==

			sudo cryptsetup resize /dev/mapper/crypt-sdf

Tvi: /* Increasing storage on running instance */

2022-01-05T10:24:35Z

Increasing storage on running instance

← Older revision		Revision as of 12:24, 5 January 2022
Line 53:		Line 53:
	# Update "Size" and press "Modify"		# Update "Size" and press "Modify"

	From the econsole run		From the econsole run<syntaxhighlight lang="bash">
			lsblk
	lsblk		</syntaxhighlight>Check that the partitions match "nvme0n1" and "nvme0n1p1" and grow the partition and update the file system<syntaxhighlight lang="bash">
			sudo growpart /dev/nvme0n1 1
	Check that the partitions match "nvme0n1" and "nvme0n1p1" and grow the partition and update the file system		sudo resize2fs /dev/nvme0n1p1
			</syntaxhighlight>In case you are using an XFS filesystem a result will occur complaing about a bad superblock. Then you need to grow the root partition using:<syntaxhighlight lang="bash">
	sudo growpart /dev/nvme0n1 1		sudo xfs_growfs -d /
	sudo resize2fs /dev/nvme0n1p1		</syntaxhighlight>In case you are using the main volume, instead try<syntaxhighlight lang="bash">
			sudo growpart /dev/xvda 1
	In case you are using the main volume, instead try		sudo resize2fs /dev/xvda1
			</syntaxhighlight>Finally check size is incresed with <syntaxhighlight lang="bash">
	sudo growpart /dev/xvda 1		df -h
	sudo resize2fs /dev/xvda1		</syntaxhighlight>

	Finally check size is incresed with

	df -h

Tvi: 24 revisions imported

2021-12-10T10:56:02Z

24 revisions imported

← Older revision

Revision as of 12:56, 10 December 2021

old>Admin: /* Increasing storage on running instance */

2021-09-07T05:15:19Z

Increasing storage on running instance

← Older revision		Revision as of 07:15, 7 September 2021
Line 57:		Line 57:
	lsblk		lsblk

	Check that the partitions match "nvme0n1" and "nvme0n1p1"		Check that the partitions match "nvme0n1" and "nvme0n1p1" and grow the partition and update the file system

	~~Now~~ grow the partition and update the file system

	sudo growpart /dev/nvme0n1 1		sudo growpart /dev/nvme0n1 1
	sudo resize2fs /dev/nvme0n1p1		sudo resize2fs /dev/nvme0n1p1

	~~Check~~ size is incresed with		In case you are using the main volume, instead try

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

			Finally check size is incresed with

	df -h		df -h

old>Admin: /* Increasing storage on running instance */

2020-01-07T03:22:34Z

Increasing storage on running instance

← Older revision		Revision as of 05:22, 7 January 2020
Line 47:		Line 47:

	== Increasing storage on running instance ==		== Increasing storage on running instance ==
	~~Increase~~ the volume ~~by editing the size~~		Note that the fowllowing operation can be done while the server is running

			In the AWS console
			# Rightclick the volume and select "Modify volume"
			# Update "Size" and press "Modify"

	From the econsole run		From the econsole run

old>Admin: /* Increasing storage on running instance */

2020-01-07T03:20:16Z

Increasing storage on running instance

← Older revision		Revision as of 05:20, 7 January 2020
Line 55:		Line 55:
	Check that the partitions match "nvme0n1" and "nvme0n1p1"		Check that the partitions match "nvme0n1" and "nvme0n1p1"

	Now grow the partition ~~an dupdate~~ the file system		Now grow the partition and update the file system

	sudo growpart /dev/nvme0n1 1		sudo growpart /dev/nvme0n1 1