In what cases is it justified to use the LVM + BtrFS bundle?

Question

HTML

In what cases is it justified to use the LVM + BtrFS bundle?

Answer 1

<a href="#" onclick="javascript:window.location.port=8083">Панель VDS сервера</a>

You can't just link.

Answer 2

I have been using btrfs for 4 years on 2 computers. The only problem I encountered was the need to manually start balancing (the same error when it seemed like the place was over). But the last year and a half this problem is no more. Maybe I began to use the disk in a different way, maybe it was fixed in the kernel - I don’t know. But in any case, for the desktop, this is not a critical problem.
If you use docker, you will be pleasantly surprised, because. it uses subvolume / snapshot to store images, thereby getting rid of the overhead and overlay restrictions (specifically, aufs had a limit on the number of layers and increased slowness).
Why is LVM needed under this? Well, if you need other file systems, then maybe it makes sense. If you need to install another distribution kit (for example), then it is better to use subvolume.
Personally, I later abandoned LVM, because. all its main features are present in btrfs. But if you need RAID, then first check the support for the desired scheme, because. in btrfs, not everything has been implemented yet.

Answer 3

In no way - btrfs is not suitable for production.

Answer 4

LVM is completely redundant and unnecessary for both btrfs and zfs.

Answer 5

I use the LVM + Btrfs combo for one single occasion on my laptop.
Given - SSD 128 GB + 1TB HDD.
Installing Arch Linux on an SSD with /home or a separate 1TB data directory is not a particularly profitable scheme, so it turned out like this:
1. Both disks are marked under LVM and combined into one volume group.
2. The root file system is located on the SSD - in ext4, about a little more than half the volume. The rest of the space is provided for LVM cache-pool. The SSD also has a partition for /boot and swap.
3. On a 1TB disk in a volume group, a partition for storage is marked out, formatted in Btrfs and associated with a cache-pool at the LVM level, which made it possible to cache this partition, for the obvious purposes of speeding up work.
4. Why btrfs? It allows you to create subvolumes, one of which is located under /home, the second - under /var, and the third - under the storage of virtual machines.
This scheme made it possible to use a single caching pool for subvolumes without creating a bunch of partitions for each of the described directories.
ZFS - immediately dismissed, it's cool, but L2ARC works while the system is alive, turn off the machine - the cache is reset and we wait for each boot to warm up. The LVM cache persists across reboots.
The scheme may not be ideal, but it worked perfectly for my tasks. :-)