All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Michael Lyle <mlyle@lyle.org>
Cc: 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, 28 Nov 2017 20:59:56 +0100	[thread overview]
Message-ID: <1855331d-a606-58fd-2649-67203ddee8b5@profihost.ag> (raw)
In-Reply-To: <CAJ+L6qcJ+heW+B2tyimxmJwjW6jQ0tsAz+bYx_3uYSc0YR53nA@mail.gmail.com>

)

Am 28.11.2017 um 20:51 schrieb Michael Lyle:
> On Tue, Nov 28, 2017 at 11:32 AM, Stefan Priebe - Profihost AG
> <s.priebe@profihost.ag> wrote:
>> nobody asked for this - but bcache provides bcache-tools and upstream
>> udev rules and those don't work in this case. To i consider this an
>> upstream bug. Not a bug in my envorinment or in my distribution.
> 
> I do not maintain bcache-tools.  It looks like g2p wrote a set of
> rules in 2014 that Debian uses.  Gentoo uses a different set of rules.
> Arch uses a slightly different set of rules.
> 
> Nor is what you're trying to do completely safe, because depending on
> rule ordering it can mean if you stack md & bcache, for instance, very
> bad things could happen with your change.

Thanks - that helped. - didn't know that the original bcache-tools which
came from kent were handed over to somebody else / or that each
distribution uses it's own.

> This is an issue for your distribution maintainer.
> 
>>
>> I can fix this myself - i just had the hope to get it fixed upstream so
>> others don't fall into the same issue.
>>
>> Greets,
>> Stefan
> 
> Mike
> 

  reply	other threads:[~2017-11-28 19:59 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 [this message]
2017-11-28 20:05                                           ` Michael Lyle
2017-11-28 20:31                                             ` Stefan Priebe - Profihost AG
2017-12-01 15:10                                               ` Nix
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=1855331d-a606-58fd-2649-67203ddee8b5@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=i@coly.li \
    --cc=linux-bcache@vger.kernel.org \
    --cc=mlyle@lyle.org \
    --cc=n.fahldieck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.