Vasyl Korytov
Vasyl Korytov
okay, submitted a patch in my branch: #4 those docs seem to be broken since existing of the program, if I read the commit history correctly, btw
there is rootfs there indeed: ``` rootfs / rootfs rw 0 0 ... /dev/sda1 / xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0 ```
I think, I can send a PR in several days. thanks.
I made a hack to ignore rootfs and tested it. next I get: `error: unsupported partition table type "" on /dev/sda` ```sh # sfdisk -d /dev/sda # partition table of...
I have `sfdisk from util-linux 2.23.2` I'll check in a while, thanks
error message now changed: `error: unknown MBR partition type "" for /dev/sda4`
(and that's strange as `/` is actually `sda1`)
you should be able to reproduce this on Azure like this: 1. create a server from "CentOS-based 7.5" image from Rogue Wave 2. any size would fit. basic a1 is...
does not. to resize an Azure disk, you must have the VM powered off and deallocated. then you power it on, resize your sda and run growfs.
it may however support live-resizing of non-system disks, frankly, don't know it. IIRC, AWS also did not allow to resize the system disk without powering it off.