Amazon Elastic Block Store Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=Internal=
=Internal=


* [[Amazon Elastic Block Storage#Subjects|Amazon Elastic Block Storage]]
* [[Amazon Elastic Block Store#Subjects|Amazon Elastic Block Store]]


=Operations=
=Operations=

Revision as of 00:44, 10 December 2019

Internal

Operations

Making an EBS Volume Available for Use

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html

I need to do that to use the storage and not fill up the root partition.

Code to apply the procedure automatically is available in em.

Attaching an ESB Volume

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-attaching-volume.html

Extending a Volume

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html

Expanding a Linux Partition

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/storage_expand_partition.html

Organizatorium

Even if the dedicated disk has 800GB, the default partitions are undersized. I need to understand this better, but this is what I did:

lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
xvda    202:0    0  800G  0 disk 
├─xvda1 202:1    0    1M  0 part 
├─xvda2 202:2    0    6G  0 part /

There's a lot of space (790+GB) that is not allocated to any partition.

gdisk /dev/xvda

p (print partions)

n (create new partion)

Partition Number: 3

First sector .. etc

Allocate all, then 'w' and then reboot - otherwise /dev/xvda3 won't be visible.