If we have a baremetal machine with a “partition” on traditional “disk”, then extending the filesystem means updating the “last sector” data of the partition, and requires that LBAs “after” the partition are not allocated.
For a VM the situation looks quite the same, but the “disk” can be many things. It could be a file on the host system. It could be one of the partitions on the host system, or LVM volume. The latter sounds fun if you have LVM within “partition” of VM, while entire “disk” of VM is just one LVM volume on the host, gobbled up who knows how.
But, the “disk” for VM does not have to be on the host at all; it can be on external storage system (and most likely is). The SAN products tend to have physical and logical layers, just like we have with LVM – and way more than “single disk”.
May I check if this is fixed or if there are any official workarounds from Rocky? (removing the other 2 partitions)
As of checking, loading up new VMs on Azure marketplace with Rocky Linux 9 images still does not put the root folder at the end for extending partition.
Hey - I am trying to find some time to look into our Azure images for the upcoming 8.10 and 9.4 releases (in May).
The images that we are publishing from our “new” publisher account (Microsoft Azure Marketplace) are constructed using a kickstart which ensures that the root partition should be the last one on the disk–allowing for the user to extend it either with a larger disk (and expanding the partition) or by doing the same, but with LVM (though LVM of course gives a bit more flexibility).
Can you confirm which images you are deploying from?
Community gallery name:
rocky-dc1c6aa6-905b-4d9c-9577-63ccc28c482a
I am looking to put the shared image gallery information on our website as part of the redesign. From your perspective, what information would be important to display, similar to what we display for AWS images?
