public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Coly Li <i@coly.li>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
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 21:29:10 +0800	[thread overview]
Message-ID: <11ecba69-d19e-fe34-eef4-ba9f4de28d0e@coly.li> (raw)
In-Reply-To: <6c624629-c528-fd92-420f-ea50c4e6e4c5@profihost.ag>

On 22/11/2017 9:14 PM, Stefan Priebe - Profihost AG wrote:
> Am 22.11.2017 um 13:57 schrieb Coly Li:
>> On 22/11/2017 8:26 PM, Stefan Priebe - Profihost AG wrote:
>>>
>>> Am 22.11.2017 um 13:16 schrieb Coly Li:
>>>> On 22/11/2017 7:23 PM, Stefan Priebe - Profihost AG wrote:
>>>>> Hello,
>>>>>
>>>>> i've 6 bcache blk devices attached to 3 caching ssds (2 each). One fails
>>>>> to register automatically at boot time.
>>>>>
>>>>> After reboot i always need to execute:
>>>>> echo /dev/sdf1 >/sys/fs/bcache/register
>>>>>
>>>>> to bring up the bcache device.
>>>>>
>>>>> Any idea?
>>>>
>>>> Hi Stefan,
>>>>
>>>> Is there any clue from kernel message ?
>>>
>>> Sadly not.
>>>
>>> Working one:
>>> ]# dmesg | grep sdi
>>> [    1.060377] sd 5:0:0:0: [sdi] 1953525168 512-byte logical blocks:
>>> (1.00 TB/932 GiB)
>>> [    1.060393] sd 5:0:0:0: [sdi] Write Protect is off
>>> [    1.060396] sd 5:0:0:0: [sdi] Mode Sense: 00 3a 00 00
>>> [    1.060425] sd 5:0:0:0: [sdi] Write cache: enabled, read cache:
>>> enabled, doesn't support DPO or FUA
>>> [    1.104341]  sdi: sdi1
>>> [    1.104644] sd 5:0:0:0: [sdi] Attached SCSI disk
>>> [    2.005452] bcache: register_bdev() registered backing device sdi1
>>> [    2.045211] bcache: bch_cached_dev_attach() Caching sdi1 as bcache0
>>> on set 76b95bf8-9cc7-407f-9f9e-a42b6d1bcb27
>>>
>>>
>>> not working one:
>>> # dmesg | grep sdf
>>> [    0.946107] sd 0:0:5:0: [sdf] 1953525168 512-byte logical blocks:
>>> (1.00 TB/932 GiB)
>>> [    1.400267] sd 0:0:5:0: [sdf] Write Protect is off
>>> [    1.400267] sd 0:0:5:0: [sdf] Mode Sense: 00 00 00 00
>>> [    1.401347] sd 0:0:5:0: [sdf] Write cache: enabled, read cache:
>>> enabled, supports DPO and FUA
>>> [    1.902910]  sdf: sdf1
>>> [    2.341289] sd 0:0:5:0: [sdf] Attached SCSI disk
>>> [  295.458804] bcache: register_bdev() registered backing device sdf1
>>> [  295.506656] bcache: bch_cached_dev_attach() Caching sdf1 as bcache5
>>> on set 76b95bf8-9cc7-407f-9f9e-a42b6d1bcb27
>>>
>>> At 295s i registeeed it manually.
>>
>> 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.

Hi Stefan,

Can you download the patch from following URL:
https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-patches.git/plain/for-test/0001-bcache-fix-a-circular-dead-locking-with-dc-writeback.patch

Coly Li

  reply	other threads:[~2017-11-22 13:29 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 [this message]
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
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=11ecba69-d19e-fe34-eef4-ba9f4de28d0e@coly.li \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox