![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/80c24909-8a49-4cb6-9bdd-4b8621b8cf1d.jpeg)
1·
23 days agodeleted by creator
deleted by creator
LVM is actually super common. Most Linux distros default to LVM unless you do custom partitioning. It’s not just about the max number of partitions supported by the table. LVM provides a TON more flexibility and ease of management of partitions.
Definitely second this. If you’re using LVM, it uses the physical UUID for the pv. You have to update that on the new drive so it knows where the vg and lvs are being mounted to.
That’s fair, I should have clarified that on most Enterprise Linux distros LVM is definitely the norm. I know Fedora switched to btrfs a few releases back and you may be right about Suse Tumbleweed but pretty sure Suse Leap uses LVM. CentOS, RHEL, Alma, etc. all still default to LVM, as the idea of keeping everything on a single partition is a bad idea and managing multiple partitions is significantly easier with LVM. More than likely that’ll change when btrfs has a little more mileage on it and is trusted as “enterprise ready” but for now LVM is the way they go. MBR vs GPT and EFI vs non-EFI don’t have a lot to do with it though, it’s more about the ease of managing multiple partitions (or subvolumes if you’re used to btrfs), as having a single partition for root, var, and home is bad idea jeans.