this post was submitted on 21 Jan 2024
22 points (100.0% liked)

linuxmemes

20741 readers
854 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Pantherina@feddit.de 0 points 7 months ago (1 children)

Can you explain LVM in practice to me? I used ext4 and now Fedora Kinoite with BTRFS, the filsystem never makes any problems and some fancy features just work.

[–] mdurell@lemmy.world 0 points 7 months ago (1 children)

In practice, you would split a disk up to keep /home separate from/ and probably other parts of the filesystem too like /var/log.. this has long been an accepted practice to keep a full disk from bringing something production offline completely and/or complicating the recovery process. Now, you could use partitions but once those are set, it's hard to rearrange them without dumping all the data and restoring it under the new tables. LVM stands for Logical Volume Manager and puts an abstraction layer between the filesystems and the partitions (or whole disk if you are into that). This means you can add Disks arbitrarily in the future and add parts of those disks to the filesystems as required. This can really minimize or even eliminate downtime when you have a filesystem getting filled up and there's nothing you can easily remove (like a database).

It's good to know but with the proliferation of cloud and virtual disks it's just easier on those systems to leave off LVM and just keep the filesystems on their own virtual disks and grow the disk as required. It is invaluable when running important production systems on bare metal servers even today.

Hope this helps.

[–] Pantherina@feddit.de 0 points 7 months ago

Thanks! So BTRFS does something similar with volumes, but baked in.