From: Michael Lyle <mlyle@lyle.org>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Coly Li <i@coly.li>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: ont out of 6 bcache devices does not register automatically
Date: Wed, 22 Nov 2017 09:51:32 -0800 [thread overview]
Message-ID: <f6c02ce5-eeff-955f-53a6-0db07aaecd08@lyle.org> (raw)
In-Reply-To: <6c624629-c528-fd92-420f-ea50c4e6e4c5@profihost.ag>
Hi Coly, Stefan--
On 11/22/2017 05:14 AM, Stefan Priebe - Profihost AG wrote:
>> Hi Stefan,
>>
>> Hmm, I don't have idea here. Anyway, is the cache mode set as writeback?
>> Recently I post a patch to fix a potential deadlock between writeback
>> rate update kworker and register code, I am not sure whether it is
>> relative to your issue, but at least we can have a try. the patch title is:
>> [RFC] bcache: fix a circular dead locking with dc->writeback_lock and
>> bch_register_lock
>>
>> Just for your information.
>
> i can try that one - can you please resend? I can't find that mail and
> don't know how to grab that one our of the web html archives to apply
> correctly.
>
> Stefan
I don't think there's any chance this patch will do anything. If
there's a deadlock, the whole thing will become stuck forever and never
allow registration or progress on the device again-- which doesn't match
the symptoms here.
This probably relates to udev configuration in your environment somehow.
Mike
next prev parent reply other threads:[~2017-11-22 17:51 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 [this message]
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
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=f6c02ce5-eeff-955f-53a6-0db07aaecd08@lyle.org \
--to=mlyle@lyle.org \
--cc=i@coly.li \
--cc=linux-bcache@vger.kernel.org \
--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 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.