From: Nix <nix@esperi.org.uk>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Michael Lyle <mlyle@lyle.org>, 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: Fri, 01 Dec 2017 15:10:32 +0000 [thread overview]
Message-ID: <87a7z21o2f.fsf@esperi.org.uk> (raw)
In-Reply-To: <c2c82969-5fba-cea8-756a-d7489b506e7a@profihost.ag> (Stefan Priebe's message of "Tue, 28 Nov 2017 21:31:26 +0100")
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.)
--
NULL && (void)
next prev parent reply other threads:[~2017-12-01 15:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 11:23 ont out of 6 bcache devices does not register automatically Stefan Priebe - Profihost AG
2017-11-22 12:16 ` Coly Li
2017-11-22 12:26 ` Stefan Priebe - Profihost AG
2017-11-22 12:57 ` Coly Li
2017-11-22 13:14 ` Stefan Priebe - Profihost AG
2017-11-22 13:29 ` Coly Li
2017-11-22 14:16 ` Stefan Priebe - Profihost AG
2017-11-22 15:51 ` Coly Li
2017-11-22 19:07 ` Stefan Priebe - Profihost AG
2017-11-22 17:51 ` Michael Lyle
2017-11-22 19:06 ` Stefan Priebe - Profihost AG
2017-11-22 19:42 ` Stefan Priebe - Profihost AG
2017-11-22 20:22 ` Michael Lyle
2017-11-22 20:36 ` Stefan Priebe - Profihost AG
2017-11-22 20:44 ` Michael Lyle
2017-11-22 20:56 ` Stefan Priebe - Profihost AG
2017-11-22 21:03 ` Michael Lyle
2017-11-22 21:07 ` Stefan Priebe - Profihost AG
2017-11-22 21:10 ` Michael Lyle
2017-11-22 21:13 ` Stefan Priebe - Profihost AG
2017-11-23 7:10 ` Stefan Priebe - Profihost AG
2017-11-28 9:36 ` Stefan Priebe - Profihost AG
[not found] ` <CAJ+L6qc79S1t10WfeycRFLesuqbZNfUXrN7qo6fVuwbHk=n8xw@mail.gmail.com>
2017-11-28 19:32 ` Stefan Priebe - Profihost AG
2017-11-28 19:51 ` Michael Lyle
2017-11-28 19:59 ` Stefan Priebe - Profihost AG
2017-11-28 20:05 ` Michael Lyle
2017-11-28 20:31 ` Stefan Priebe - Profihost AG
2017-12-01 15:10 ` Nix [this message]
2017-12-10 19:34 ` Stefan Priebe - Profihost AG
2017-12-10 19:36 ` Michael Lyle
2017-12-10 19:39 ` Stefan Priebe - Profihost AG
2017-12-12 15:38 ` Nix
2017-11-22 21:10 ` Stefan Priebe - Profihost AG
2017-11-22 21:13 ` Michael Lyle
2017-11-23 11:43 ` Kai Krakow
2017-11-23 12:03 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7z21o2f.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=i@coly.li \
--cc=linux-bcache@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=n.fahldieck@profihost.ag \
--cc=s.priebe@profihost.ag \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox