how does lvm allow the root partition to be smaller?
how does lvm allow the root partition to be smaller?
Ai still dont understand that
Aand no diff downloads either, which perhaps for a 2gb compressed iso is not that big of a deal
Slvm isn't a partition in the normal sense, it uses volumes that can be dynamically resized, hence it being able to do some bonkers stuff lol
Awell
Aif i have a bucket
Awith a partition in the middle
Aand the bucket is 2 liters
Aif i fill each partition with 1.5 liters it will overflow
Aso wheres the magic here
Sall that would matter to LVM is the overall size, not where your partition is
MLvm can do thin provisions and over provsioning
Alets logic this out
MIt can blow up on you if you over fill it
Ai have an image that is 20gb and the update is also 20gb
AI need 40gb total, like legacy abroot
Abut with lvm i can use 20gb?
MYou will need 40 GB.
Ayeah so well
MIt's more on a 1 TB drive you can provision 2, 1 TB partitions on it. Each will think it has 1 TB, but it only consumes the current space actually on disk
Ayeah vanillaos folk claim they reduced their root partition size from 40gb to 20gb by using lvm
Aand thats funny math
G@antheas https://github.com/ublue-os/cosmic/blob/3943e8fe9d195cd5496a374a5f89905eeb1856b2/.github/workflows/build.yml does this look good now?
Gnot entirely sure what else needs to be done
Ayou can also try
skip_compression https://github.com/hhd-dev/rechunk/blob/a66777859f9c565984d6172af21ddbbe14612f00/action.yml#L26GitHub
Contribute to hhd-dev/rechunk development by creating an account on GitHub.
Ashould save 2 min
Gis there a lot of space gain from compression?
SThat imo is just a really bad way to explain what you have actually done by using LVM
Aits on by default in ostree-rs-ext
Aand i use it on my action bc i use skopeo to push
Abut for bazzite we did podman so it gets scraped
Ahttps://github.com/hhd-dev/rechunk/blob/master/.github/workflows/online_test_deck.yml and check out this and pick out stuff that you like
GitHub
Contribute to hhd-dev/rechunk development by creating an account on GitHub.
Alike cosmic version
Ai still dont get the math here
Ai aint no genious but google has spent millions of dollars on the AB issue
Goh I think we use the docker push action
Gin the cosmic build.yml
Gnvm it's the redhat version
Gdoes the redhat action use skopeo or podman?
Apodman
Awell you load to podman so gzip gets stripped
Aand then recompressed
Aso you might as well skip
Galr
Aif space allows
FInstead of storing 40GB partition fixed to that amount, that partition can dynamically use the space up to 40GB
Auh so lvm applies to the whole drive or the root partition?
Fbut it is the bad explanation of LVM
Gyeah we got plenty, the cosmic image is pretty small
SThe 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.
