archive mirror
 help / color / mirror / Atom feed
From: "Sidney San Martín" <>
Subject: Can't mount filesystem after clean shutdown with discard enabled
Date: Thu, 4 Mar 2021 14:25:23 -0500	[thread overview]
Message-ID: <> (raw)

I enabled discard on the bcache backing a large filesystem with writeback caching a few weeks ago. Yesterday I restarted the system cleanly and it failed to come back. I see the following in the log:

  Mar 04 19:04:18 archiso kernel: bcache: prio_read() bad csum reading priorities
  Mar 04 19:04:18 archiso kernel: bcache: bch_cache_set_error() error on 6432e656-f28e-49f8-943d-6307d42d37e9: IO error reading priorities, disabling caching

The backing devices are all marked dirty when I check with bcache-super-show. I see threads going back years mentioning this problem:

There is also a bug report:

The cache device backs a large BTRFS volume made up of many spinning disks and, while I have a backup, it’s offsite and will take a huge amount of time to restore. Since I’m running BTRFS with some redundancy, I would love to do whatever I can to get things back to as good a state as possible and try a scrub.

I tried building bcache myself and skipping loading priorities, since comments suggest they’re nonessential, and the next thing I hit is:

  Mar 04 15:32:56 archiso kernel: bcache: bch_cache_set_error() error on 6432e656-f28e-49f8-943d-6307d42d37e9: unsupported bset version at bucket 108857, block 0, 79054670 keys, disabling caching

Note that I’m not familiar with bcache internals and this is actually my first time building a kernel module to debug something.

What can I do here? And should discard even be available as an option if it fails this badly?

                 reply	other threads:[~2021-03-04 19:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).