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

From: Nix <nix@esperi.org.uk>
To: Michael Lyle <mlyle@lyle.org>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	Coly Li <i@coly.li>,
	"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
	n.fahldieck@profihost.ag
Subject: Re: ont out of 6 bcache devices does not register automatically
Date: Tue, 12 Dec 2017 15:38:57 +0000	[thread overview]
Message-ID: <87tvwwklbi.fsf@esperi.org.uk> (raw)
In-Reply-To: <f4ab9fc2-3842-948c-91a0-bc980d675481@lyle.org> (Michael Lyle's message of "Sun, 10 Dec 2017 11:36:17 -0800")

On 10 Dec 2017, Michael Lyle spake thusly:

> On 12/10/2017 11:34 AM, Stefan Priebe - Profihost AG wrote:
>> 
>> Am 01.12.2017 um 16:10 schrieb Nix:
>>> 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.
>
> These problems aren't anything specific to bcache.

Quite. If you have a crazy stack like that you have to register by hand
at the appropriate time. bcache has uuids, so you should be able to just
try to register everything accessible at each stage, and things will
come together nicely.

-- 
NULL && (void)