Hello
I am currently testing FreePBX running on an EC2 instance on Amazon AWS.
To migrate onto AWS I first setup FreePBX as a virtual machine on my desktop using VirtualBox and I allocated a relatively small hard drive size. I then exported the VM and uploaded it as an image onto AWS so I could spin up an instance. When I created the AWS instance I gave it a 200GB hard drive. However, the FreePBX server still thinks it has an 8GB hard drive.
Does anyone have any information on how best to expand into the full 200GB.
Below are a few commands that may help profile more information on the setup:
[root@pbx02 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 7.1G 3.9G 3.2G 56% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 8.0K 1.9G 1% /dev/shm
tmpfs 1.9G 153M 1.8G 9% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/xvda1 1.9G 127M 1.7G 7% /boot
tmpfs 379M 0 379M 0% /run/user/0
tmpfs 379M 0 379M 0% /run/user/995
[root@pbx02 ~]#
[root@pbx02 ~]# fdisk -l
Disk /dev/xvda: 214.7 GB, 214748364800 bytes, 419430400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000aa2c4
Device Boot Start End Blocks Id System
/dev/xvda1 * 2048 4098047 2048000 83 Linux
/dev/xvda2 4098048 20971519 8436736 8e Linux LVM
Disk /dev/mapper/SangomaVG-root: 7562 MB, 7562330112 bytes, 14770176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/SangomaVG-swaplv1: 1073 MB, 1073741824 bytes, 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@pbx02 ~]#
[root@pbx02 ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root SangomaVG -wi-ao---- 7.04g
swaplv1 SangomaVG -wi-ao---- 1.00g
[root@pbx02 ~]#
Thanks