There's no reason the "disks" you're spanning couldn't already be redundant, although probably safe to assume that isn't the case at home. ⇒ Never really needed it as I have preferred hardware or ZFS. Have logical volumes stretched over several disks. My nas/server also has additional drives that each have luks, and are joined into a btrfs-managed raid1. Btrfs (/, /home), VM Images, and swap on LVM. My laptop, desktop, (home) nas/sever and (work) workstation have pretty similar setups: EFI System, /boot, and LUKS partitions. That's as much an argument against bare partitions as it is LVM.Įvery machine I use has the same setup: boot, EFI, and then XFS on LUKS for the rest of the space. If you lose a disk that isn't redundant, you lose data. That's just how disks work, and isn't LVM-specific. If your physical volumes are not on a RAID-1, RAID-5 or RAID-6 losing one disk can lose one or more logical volumes if you span (or extend) your logical volumes across multiple non-redundant disks.I'm sure there's one person somewhere that is glad this was listed. If dual-booting, note that Windows does not support LVM you will be unable to access any LVM partitions from Windows.Requires (multiple) daemons to constantly run. Additional steps in setting up the system, more complicated.Unless systemd-homed beats LVM to the punch. ⇒ When I finally switch to using a dedicated /home partition, I may end up switching to LVM. for /, /home, /backup, etc.) without the hassle of entering a key multiple times on boot. This allows creating a system with (one or more) physical disks (encrypted with LUKS) and LVM on top to allow for easy resizing and management of separate volumes (e.g. Support for various device-mapper targets, including transparent filesystem encryption and caching of frequently used data.Snapshots allow you to backup a frozen copy of the file system, while keeping service downtime to a minimum.Online/live migration of LV being used by services to different disks without having to restart services.File systems on them still need to be resized, but some (such as ext4) support online resizing. Resize/create/delete logical and physical volumes online.⇒ Never needed it, although I admit this would be nice if you made an oopsie and didn't give your boot or EFI partitions enough space. It does not depend on the position of the LV within VG, there is no need to ensure surrounding available space. Resize logical volumes regardless of their order on disk.⇒ Usually I just grab all available space on a partition rather than growing piecemeal. Create small logical volumes and resize them "dynamically" as they get filled up.Have logical volumes stretched over several disks.⇒ Either I've used hardware JBOD, RAID, or ZFS. Use any number of disks as one big disk.Just for giggles, I'll go through the Arch wiki's advantages list: I don't discount that you've had good cause to use LVM, I'm only talking about myself here. The things that LVM is supposed to make easy, I have never needed. Every machine I use has the same setup: boot, EFI, and then XFS on LUKS for the rest of the space. But it's still pretty irrelevant for me, the only machine I have with more than a single disk is my NAS. Mailing list: Fedora Testers (for Fedora Beta releases)īeyond what's on the Arch wiki, I would add that the benefit of resizing a LV is highly dependent on the FS that you have on top of it.Discord: discord.gg/fedora (Voice & Text chat).Post content regarding Fedora Project or Linux in general.This subreddit is not affiliated with or endorsed by the Fedora Project. A community for users, developers and people interested in the Fedora Project and news and information about it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |