linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Thorsten Knabe <linux@thorsten-knabe.de>,
	Rolf Fokkens <rolf@rolffokkens.nl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: PROBLEM: bcache related kernel BUG() since Linux 5.12
Date: Sat, 5 Jun 2021 23:20:34 +0800	[thread overview]
Message-ID: <1dba3411-5824-d9d6-befd-fda3d7806ded@suse.de> (raw)
In-Reply-To: <c838fdb3-e56b-c0f1-bfeb-0f5ebf4b369d@thorsten-knabe.de>

On 6/4/21 8:06 PM, Thorsten Knabe wrote:
> Hi Coly.
>
> On 6/4/21 12:35 PM, Coly Li wrote:
>> On 6/4/21 5:07 PM, Rolf Fokkens wrote:
>>> Hi Coly, Thorsten,
>>>
>>> I survived 48 hours perfectly:
>>>
>>> bash-5.0$ uptime
>>>  10:45:53 up 2 days, 11:05,  1 user,  load average: 2.82, 3.45, 2.67
>>> bash-5.0$ cat /proc/version
>>> Linux version 5.12.8-200.rf.fc33.x86_64
>>> (mockbuild@tb-sandbox-mjolnir.local.tbai.nl) (gcc (GCC) 10.3.1 20210422
>>> (Red Hat 10.3.1-1), GNU ld version 2.35-18.fc33) #1 SMP Tue Jun 1
>>> 23:10:39 CEST 2021
>>> bash-5.0$
>>>
>>> Furthermore there are no concerning messages in the syslog.
>> Hi Rolf,
>>
>> Thanks for your update. Which kind of applications/workload are running
>> in the past 2 days ?
>>
>> Coly Li
>>
> No problems observed here too. Made a few (intended) reboots, ran a some
> kernel builds and made a full backup during the last two days. Kernel is
> now a stock 5.12.9.
> Just booted the system from an USB stick (kernel here: debian
> 5.10.0-0.bpo.5-amd64) and performed a filesystem (ext4) check, which
> reported no errors.

Hi Thorsten and Rolf,

Thank you all for the testing and detail information.

Now I am installing a dedicate machine to use bcache for my git mirrors,
daily downloading and compiling testing.
Let's me see how it works for such workloads.

Coly Li

  reply	other threads:[~2021-06-05 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 19:06 PROBLEM: bcache related kernel BUG() since Linux 5.12 Thorsten Knabe
2021-05-16  8:42 ` Matthias Ferdinand
2021-05-16 14:43   ` Coly Li
2021-05-31  9:37 ` Rolf Fokkens
2021-06-01 15:34   ` Coly Li
2021-06-01 21:04     ` Rolf Fokkens
2021-06-01 21:46       ` Rolf Fokkens
2021-06-02  8:33     ` Thorsten Knabe
2021-06-02  9:45       ` Rolf Fokkens
2021-06-02 11:08         ` Coly Li
2021-06-04  9:07           ` Rolf Fokkens
2021-06-04 10:35             ` Coly Li
2021-06-04 12:06               ` Thorsten Knabe
2021-06-05 15:20                 ` Coly Li [this message]
     [not found]               ` <ec9f73fa-a16c-b0c1-d1f8-2bf4e585be5f@rolffokkens.nl>
2021-06-07 10:11                 ` Coly Li

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=1dba3411-5824-d9d6-befd-fda3d7806ded@suse.de \
    --to=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux@thorsten-knabe.de \
    --cc=rolf@rolffokkens.nl \
    /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;
as well as URLs for NNTP newsgroup(s).