Unable to Resize Vm

[natenbaptista]

I have a ubuntu 14 Vm of 32GB that was cloned.
Wanted to increase the cloned VM to 100 GB.
Now as per the documentation Proxmox Resize Disk

After starting the VM I ran the command.

root@atp:~# qm resize 101 virtio0 +68G WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full. Size of logical volume pve/vm-101-disk-0 changed from 32.00 GiB (8192 extents) to 100.00 GiB (25600 extents). Logical volume pve/vm-101-disk-0 successfully resized. WARNING: Sum of all thin volume sizes (832.00 GiB) exceeds the size of thin pool pve/data and the amount of free space in volume group (15.99 GiB). root@atp:~#

Seems the increase was successful as it was detected inside the guest ubuntu VM

atp@atp:~$ dmesg | grep vda [ 0.518286] vda: vda1 vda2 < vda5 > [ 0.861727] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null) [ 4.020425] Adding 4092924k swap on /dev/vda5. Priority:-1 extents:1 across:4092924k FS [ 4.548354] EXT4-fs (vda1): re-mounted. Opts: errors=remount-ro [ 79.714018] vda: detected capacity change from 34359738368 to 107374182400

Issue is that according the to documentation the "fdisk -l /dev/vda | grep ^/dev" should show a mismatch, but it does not!
Althought it does show that /dev/vda is 107.4GB now.

atp@atp:~$ sudo fdisk -l /dev/vda Disk /dev/vda: 107.4 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders, total 209715200 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 identifier: 0x0007e7a5 Device Boot Start End Blocks Id System /dev/vda1 * 2048 58918911 29458432 83 Linux /dev/vda2 58920958 67106815 4092929 5 Extended /dev/vda5 58920960 67106815 4092928 82 Linux swap / Solaris

How do i proceed from this point onward?
Anything that I have missed?

 

[fiona]

Hi,
now you can create a new partition with the newly available space and a filesystem on top of it (that is if you don't want to use it for something other than a filesystem). And after you've done that, create a mount entry in /etc/fstab to mount it automatically at boot.