Re: ont out of 6 bcache devices does not register automatically

Stefan Priebe - Profihost AG
2017-12-10T19:34:57Z

Am 01.12.2017 um 16:10 schrieb Nix:
> On 28 Nov 2017, Stefan Priebe spake thusly:
>
>> Am 28.11.2017 um 21:05 schrieb Michael Lyle:
> [...]
>>> Even if I maintained bcache-tools, I couldn't really fix this. If there
>>> is a desire to proceed through ambiguity, the ordering that actions are
>>> attempted in-- RAID, filesystems, bcache, DM, etc, becomes important,
>>> and can't be solved in any one package.
>>
>> I dont want to allow to register for ambiguity in general - but in case
>> there is ambiguity with an FS (xfs,btrfs, ...). I can't see a way where
>> this could be a problem. Even considering other block drivers like md or dm.
>
> bcache can be stacked underneath filesystems via loopback mounts. Heck
> you can have a RAID->bcache->LVM->cryptfs->loopback->RAID->bcache stack
> if you like (I've done that, though the loopback layers and below were
> only for testing.)

mhm but that means bcache can't be autoregistered in a solid way. Sad to
here that.

Thanks for your example.

Greets,
Stefan