From: Tim Small <tim@buttersideup.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [PATCH] bcache: Fix writeback_thread never writing back incomplete stripes.
Date: Thu, 01 Oct 2015 10:01:42 +0100 [thread overview]
Message-ID: <560CF676.6020102@buttersideup.com> (raw)
In-Reply-To: <20150917183154.GB28032@kmo-pixel>
On 17/09/15 19:31, Kent Overstreet wrote:
> Here's an updated patch that has a fix for _that_ theory, and also a new
> BUG_ON(). Any chance you could test it?
I've applied your patch (to the Ubuntu 4.2.1 tree - since I need some of
their non-mainline apparmour changes on this box) , and it's stopped the
excessive CPU usage by the bcache_writebac thread.
I'd first experienced this CPU spinning when I tried to disable cache
usage (I'd had some lockups on the machine and I was trying to get to
debug, so I tried switching bcache cache_mode to none whilst I debugged
as part of my process of elimination). I assume the bug was hit whilst
trying to flush the dirty cache data.
I now have:
root@magic:~# cat /sys/block/bcache0/bcache/state
clean
root@magic:~# cat /sys/block/bcache0/bcache/dirty_data
1.5M
root@magic:~# cat /sys/block/bcache0/bcache/cache_mode
writethrough writeback writearound [none]
root@magic:~# uname -a
Linux magic 4.2.1 #2 SMP Sat Sep 26 10:00:40 UTC 2015 x86_64 x86_64
x86_64 GNU/Linux
i.e. state and cache_mode are inconsistent with dirty_data. Is this of
any concern and/or likely to cause problems if I re-enable the cache?
Cheers,
Tim.
next prev parent reply other threads:[~2015-10-01 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 11:10 [PATCH] bcache: Fix writeback_thread never writing back incomplete stripes Vojtech Pavlik
2015-09-16 11:32 ` Kent Overstreet
2015-09-16 21:08 ` Denis Bychkov
2015-09-17 15:30 ` Denis Bychkov
2015-09-17 16:40 ` Kent Overstreet
2015-09-17 18:31 ` Kent Overstreet
2015-09-17 20:54 ` Denis Bychkov
2015-09-19 4:47 ` Denis Bychkov
2015-10-01 9:01 ` Tim Small [this message]
2015-09-29 23:00 ` Peter Kieser
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=560CF676.6020102@buttersideup.com \
--to=tim@buttersideup.com \
--cc=kent.overstreet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.