Nikolaus Rath posted on Mon, 08 Feb 2016 13:44:17 -0800 as excerpted: > Otherwise I'll give bcache a shot. I've avoided it so far because of the > need to reformat and because of rumours that it doesn't work well with > LVM or BTRFS. But it sounds as if that's not the case..
Bcache used to have problems with btrfs, but as I and others have mentioned, we have people known to be using btrfs with bcache on the list, and it has been working fine for quite some time, now. Bcache vs. LVM, OTOH, I know nothing about. Tho to be fair I guess I'm a bit anti-LVM biased myself, as it seems a bit too much complexity for the offered advantages, and when I tried it some time ago along with mdraid, I decided to keep the mdraid, but kill the lvm as too complex to be confident I could manage it correctly under the pressures of a disaster recovery situation, possibly with limited access to documentation, manpages, other recovery tools, etc. MDRaid, OTOH, was easier to administer, in part because it's possible to assemble mdraid direct from the kernel without userspace (initr* or the like if / is on it), and I successfully managed it thru various issues over some time. Of course these days I use multi-device btrfs directly, no mdraid, and a multi-device btrfs root unfortunately does seem to require an initr*, but its other advantages outweigh the additional complexity of having to use an initr*, so... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
