The current instructions are:
Having only played with VMWare images over a decade ago, I'm actually surprised increasing disk space is such an involved process! It also seems like the perfect candidate for something that a helper-daemon (such as qemu) should handle.
If I actually ever manage to get this vanilla Debian server disk increased I'll report back how it was done in the hope it helps someone else out.
Many thanks.
- Incongrent with the default disk settings of Proxmox (VirtIO SCSI is the disk default in proxmox but instructions show vda/VirtIO)
- Don't acknowledge that the web UI can be used
- Show command syntax that doesn't actually work on recent linux distributions ("resizepart 3 100%" is not valid and results in "invalid token")
- Often don't actually work on recent linux distrubutions (tried in debian, ubuntu, apline - fdisk quite often doesn't report any increase, and neither does parted once installed)
- Contain confusing instructions like in step 3 "If you did not resize the filesystem in step 2"...
- Don't contain any troubleshooting advice if fdisk or parted DON'T report any size increase
Having only played with VMWare images over a decade ago, I'm actually surprised increasing disk space is such an involved process! It also seems like the perfect candidate for something that a helper-daemon (such as qemu) should handle.
If I actually ever manage to get this vanilla Debian server disk increased I'll report back how it was done in the hope it helps someone else out.
Many thanks.