From: Vojtech Pavlik <vojtech@suse.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: kmo@daterainc.com, linux-bcache@vger.kernel.org
Subject: Re: Bcache stuck at writeback of a key, consuming 100% CPU, not possible to detach
Date: Mon, 31 Aug 2015 17:54:15 +0200 [thread overview]
Message-ID: <20150831155415.GA7394@suse.com> (raw)
In-Reply-To: <20150831170928.56fa9bbd@harpe.intellique.com>
On Mon, Aug 31, 2015 at 05:09:28PM +0200, Emmanuel Florac wrote:
> Le Mon, 31 Aug 2015 16:49:49 +0200
> Vojtech Pavlik <vojtech@suse.cz> écrivait:
>
> > >
> > > The bcache_writeback stays at 100% _even_ when in writethrough mode,
> > > alas. So this looks normal. However dirty_data definitely should
> > > drop to zero...
> >
> > This most certainly isn't normal. The ftrace shows it's looping in a
> > loop doing nothing useful.
> >
>
> Yep, I've had a quick look at the code, however it's not very
> inspiring. It very much looks like there's a missing test. From your
> trace it looks like it finds a key_bad (?) -- from the struct
> bch_extent_keys_ops in bcache/extents.c -- but there is no code anywhere
> to manage this case apparently.
>
> Ah, and I can't download your complete trace, too : twilight.ucw.cz
> isn't responding. :)
Sadly, the bcache array crashed hard earlier today (with a bug in and the machine
doesn't boot anymore. I'm recovering it now.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2015-08-31 15:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 8:54 Bcache stuck at writeback of a key, consuming 100% CPU, not possible to detach Vojtech Pavlik
2015-08-31 14:39 ` Emmanuel Florac
2015-08-31 14:49 ` Vojtech Pavlik
2015-08-31 15:04 ` Kent Overstreet
2015-08-31 16:45 ` Vojtech Pavlik
2015-08-31 16:53 ` Kent Overstreet
2015-08-31 17:09 ` Vojtech Pavlik
2015-09-01 13:34 ` Vojtech Pavlik
2015-08-31 16:54 ` Vojtech Pavlik
2015-08-31 15:09 ` Emmanuel Florac
2015-08-31 15:54 ` Vojtech Pavlik [this message]
2015-09-05 11:06 ` Jens-U. Mozdzen
2015-09-05 11:29 ` Vojtech Pavlik
2015-09-07 15:13 ` Jens-U. Mozdzen
2015-09-07 15:52 ` Vojtech Pavlik
2015-09-07 16:01 ` Vojtech Pavlik
[not found] ` <B7A73681-AF9A-438C-9323-B2CE3BEFCA98@profihost.ag>
2015-09-07 18:56 ` Vojtech Pavlik
2015-09-08 9:04 ` Jens-U. Mozdzen
2015-09-08 9:10 ` Vojtech Pavlik
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=20150831155415.GA7394@suse.com \
--to=vojtech@suse.com \
--cc=eflorac@intellique.com \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
/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