![]() ![]() ![]() Like I wrote, it's totally doable, but it's insane, so why would Synology do this? Because somebody at Synology liked BTRFS, but then BTRFS stagnated in terms of it's built-in volume management, and flexible storage resizing. partitions or filesystems usually land on Logical volumes, so it's unorthodox to use a logical volume as the backing store of a raid manager. but in general volume management is customarily at the end of the storage, not at the beginning. The reason for this ordering is the potential gains for volume aware filesystems, similar to stratis, zfs, btrfs, etc. But regardless, from a Linux perspective this type of configuration is ill-advised, and normally done the other way around with mdraid aggregate volumes being the input block devices feed to LVM2 volume management. In the Linux storage world, this is totally possible to do because Linux is flexible, and foot-shooting is allowed. Let's break this down, SHR uses standard Linux raid (mdraid) on top of Linux Logical Volume Management (lvm2). The issue is the spaghetti complexity of how SHR is configured, and the inherent risks involved with recovery. ![]() It's not proprietary, but that's not the issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |