The way it's explained is wrong, lvm doesnt have a set partition structure like were used to, what it does is basically take the whole disk and then rather than split it into partitions (with hard limits) it uses a volume that can change dynamically but only shows what's actually in use. So say you have one disk of 40gb but tell lvm to use three volumes it will adjust the volumes based on the usage. That's about the best i can explain it, the problem at the moment is the /boot can't use LVM as grub can't read from there.
as an aside, is using latestlatest for this ok? prev-ref: "${{ env.IMAGE_REGISTRY }}/cosmic-${{ matrix.flavor }}:latest"prev-ref: "${{ env.IMAGE_REGISTRY }}/cosmic-${{ matrix.flavor }}:latest"
so basically you always have a /boot partition and then the rest managed with LVM which is where things like bootc, systemd-boot and OCI come into play as they don't have that limit. It's all rather confusing when you get to the explaining it in text lol
I do wonder at times if I should save some money and get a multidisk server again to try things like this with LVMRaid/Linuxmd and see how long it takes to totally tear itself to bits lol
Don't like dosubot closing issues just because they are not active for some time Most of those automatically closed issues are still related to the project