Amazon Elastic Block Store Operations: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page Amazon Elastic Block Storage Operations to Amazon Elastic Block Store Operations without leaving a redirect) |
|||
(One intermediate revision by the same user not shown) | |||
Line 4: | Line 4: | ||
=Operations= | =Operations= | ||
==Create an ESB Volume== | |||
aws ec2 create-volume --availability-zone=eu-west-1a --size=10 --volume-type=gp2 | |||
==Making an EBS Volume Available for Use== | ==Making an EBS Volume Available for Use== |
Latest revision as of 22:46, 11 December 2019
Internal
Operations
Create an ESB Volume
aws ec2 create-volume --availability-zone=eu-west-1a --size=10 --volume-type=gp2
Making an EBS Volume Available for Use
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
Extending a Volume
Expanding a Linux Partition
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.