First time here? Check out the FAQ!
![]() | 1 | initial version |
NOT the answer but an update:
I read up about virsh blockresize and tried on the VM...
@hypervisor:~$ sudo virsh blockresize bootstrap --path /dev/system/bootstrap --size 20G error: Failed to resize block device '/dev/system/bootstrap' error: Requested operation is not valid: domain is not running
PS: this also has the wrong path for the file... /dev/system/bootstrap
so a) sudo virsh start bootstrap b) find the path using ps -faux | grep bootstrap which will show file=/dev/mapper/system-bootstrap
Then:
@hypervisor:~$ sudo virsh blockresize bootstrap --path /dev/mapper/system-bootstrap --size 20G Block device '/dev/mapper/system-bootstrap' is resized
except it doesn't seem to make any difference:
Using fdisk shows (I think similarly to previously after the first lvextend that there is now 21.5Gb hdd avail..) but the OS just wont resize... at this point I wish there was just a way to boot the VM using "gparted live" and resize...
@bootstrap:~$ sudo fdisk -l
Disk /dev/vda: 21.5 GB, 21474836480 bytes 16 heads, 63 sectors/track, 41610 cylinders, total 41943040 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: 0x00000000
Device Boot Start End Blocks Id System /dev/vda1 * 2048 20971519 10484736 83 Linux
![]() | 2 | No.2 Revision |
NOT the answer but an update:
I read up about virsh blockresize and tried on the VM...VM...
http://serverfault.com/questions/604876/online-resizing-of-kvm-guest-root-filesystem
@hypervisor:~$ sudo virsh blockresize bootstrap --path /dev/system/bootstrap --size 20G error: Failed to resize block device '/dev/system/bootstrap' error: Requested operation is not valid: domain is not running
PS: this also has the wrong path for the file... /dev/system/bootstrap
so a) sudo virsh start bootstrap b) find the path using ps -faux | grep bootstrap which will show file=/dev/mapper/system-bootstrap
Then:
@hypervisor:~$ sudo virsh blockresize bootstrap --path /dev/mapper/system-bootstrap --size 20G Block device '/dev/mapper/system-bootstrap' is resized
except it doesn't seem to make any difference:
Using fdisk shows (I think similarly to previously after the first lvextend that there is now 21.5Gb hdd avail..) but the OS just wont resize... at this point I wish there was just a way to boot the VM using "gparted live" and resize...
@bootstrap:~$ sudo fdisk -l
Disk /dev/vda: 21.5 GB, 21474836480 bytes 16 heads, 63 sectors/track, 41610 cylinders, total 41943040 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: 0x00000000
Device Boot Start End Blocks Id System /dev/vda1 * 2048 20971519 10484736 83 Linux