02-10-2020, 12:14 AM
(02-08-2020, 12:15 PM)Jeremiah Cornelius Wrote:(02-08-2020, 10:09 AM)moonwalkers Wrote: To be fair, without LVM you can't do things like shutdown your laptop, replace your HDD/SSD, connect the old one with USB adapter, start your laptop from the old drive over USB, start migration, keep working as usual while migration is going on, then once it is finished just unplug the old drive in the middle of some build job or whatnot and shortly afterwards just suspend your laptop, throw it into backpack and get on your way. Without LVM even if the sequence is much simpler you're kinda stuck with either a lengthy downtime while the old drive is being cloned to a new one or with multiple rounds of rsync runs and shorter but still an extra downtime.I completely endorse and agree. I wish there were high-level workflows canned, to do exactly what you describe!
Well, the reason could be that not all LVM setups are anywhere near the same from semantic viewpoint. I mean, there is a multitude of all kinds of different topologies possible with LVM, and they can range from something rather simple to something like the layered cake of LVM/LUKS/LVM setup that I like to use and beyond. At the same time, for me the migration script involves merely nine commands, out of which first three are for partitioning the new drive, the other three are for dealing with the EFI system partition, and only the remaining three are directly LVM-related (I don't immediately expand the volumes when moving to a bigger SSD, not until I actually need the extra space).