> tfw you realize a partition is only a sequence of 16 carefully

>>55878565
MBR is dead. Use GUIDO Partition Table.

>>55878565
>>55878711
LVM masterrace

>>55878841
LVM is for plebs

zfs/btrfs master race

File: whatthefuckdidyoujustsaytomeyoulittlebitch.jpg (111KB, 1500x1500px) Image search: [Google]

111KB, 1500x1500px

>>55878841
>>55878849
I can't tell if you're trying to be funny actually neither of (you) know what you're talking about.

>>55878565
>tfw all data is only a sequence of carefully crafted bits
>tfw some of them are magically illegal because

>>55878918
I was just replying to “LVM masterrace”. LVM seems to be mostly used for:

1. Pooling disks together, which btrfs and zfs do better and more safely (losing one disk in an LVM pool = complete failure) and with more protection against bit flips, corruption etc.

2. Providing snapshotting / CoW functionalities, which btrfs and zfs also do more efficiently and better.

3. Allocating virtual block devices to use as VM drives and whatnot (either thinly provisioned or flat), both of which zfs volumes do better (including e.g. snapshotting, checksumming, CoW). Not sure about btrfs

Either way, LVM has pretty much no more reason for existing if you have the option of using something like zfs, which is simply better in virtually every application. LVM suffers greatly from the distinction between FS and block layer, the removal of which is what make zfs and btrfs so awesome.