From: Matthias Ferdinand <bcache@mfedv.net>
To: Thorsten Knabe <linux@thorsten-knabe.de>
Cc: linux-bcache@vger.kernel.org
Subject: Re: PROBLEM: bcache related kernel BUG() since Linux 5.12
Date: Sun, 16 May 2021 10:42:28 +0200 [thread overview]
Message-ID: <YKDa9IOPsDJ0Wa8i@xoff> (raw)
In-Reply-To: <58f92cd7-38d1-bc16-2b5f-b68b2db2233b@thorsten-knabe.de>
On Sat, May 15, 2021 at 09:06:07PM +0200, Thorsten Knabe wrote:
> Hello.
>
> Starting with Linux 5.12 bcache triggers a BUG() after a few minutes of
> usage.
>
> Linux up to 5.11.x is not affected by this bug.
>
> Environment:
> - Debian 10 AMD 64
> - Kernel 5.12 - 5.12.4
> - Filesystem ext4
> - Backing device: degraded software RAID-6 (MD) with 3 of 4 disks active
> (unsure if the degraded RAID-6 has an effect or not)
> - Cache device: Single SSD
Sorry I can't immediately help with bcache, but for DRBD, there was a
similar problem with DRBD on degraded md-raid fixed just recently:
https://lists.linbit.com/pipermail/drbd-user/2021-May/025904.html
Although they had silent data corruption AFAICT, not a loud BUG(), and
they stated problems started with kernel 4.3.
For DRBD it had to do with split BIOs and readahead, which degraded
md-raid may or may not fail, and missing a fail on parts of a split-up
readahead BIO.
Matthias
next prev parent reply other threads:[~2021-05-16 8:45 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 [this message]
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
[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=YKDa9IOPsDJ0Wa8i@xoff \
--to=bcache@mfedv.net \
--cc=linux-bcache@vger.kernel.org \
--cc=linux@thorsten-knabe.de \
/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