From: Kent Overstreet <kent.overstreet@gmail.com>
To: Nikhil Kshirsagar <nkshirsagar@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: bcache-register hang after reboot
Date: Wed, 10 Nov 2021 15:13:09 -0500 [thread overview]
Message-ID: <YYwn1eT86dvSRfeA@moria.home.lan> (raw)
In-Reply-To: <CAC6jXv0mw4eOzFSzzm0acBJFM5whhC=hTFG6_8H__rfA6zq5Cg@mail.gmail.com>
On Wed, Nov 10, 2021 at 11:14:41AM +0530, Nikhil Kshirsagar wrote:
> Hello,
>
> After a reboot of an Ubuntu server running 4.15.0-143-generic kernel,
> the storage devices using bcache do not come back up and the following
> stack traces are seen in kern.log. Please could someone help me
> understand if this is due to a full bcache journal? Is there any
> workaround, or fix?
Your journal is completely full, so persisting the new btree root while doing
journal replay is hanging.
There isn't a _good_ solution for this journal deadlock in bcache (it's fixed in
bcachefs), but there is a hack:
edit drivers/md/bcache/btree.c line 2493
delete the call to bch_journal_meta(), and build a new kernel. Once you've
gotten it to register, do a clean shutdown and then go back to a stock kernel.
Running the kernel with that call deleted won't be safe if you crash, but it'll
get you going again.
next prev parent reply other threads:[~2021-11-10 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 5:44 bcache-register hang after reboot Nikhil Kshirsagar
2021-11-10 20:13 ` Kent Overstreet [this message]
2021-11-11 20:54 ` Mauricio Oliveira
2021-11-13 18:05 ` Kent Overstreet
2021-12-13 22:04 ` Mauricio Faria de Oliveira
2021-12-13 22:22 ` Mauricio Faria de Oliveira
2021-12-14 16:06 ` Coly Li
2021-12-14 16:43 ` Mauricio Faria de Oliveira
2021-11-12 5:45 ` Coly Li
2021-11-13 18:12 ` Kent Overstreet
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=YYwn1eT86dvSRfeA@moria.home.lan \
--to=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=nkshirsagar@gmail.com \
/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