From: "Stephen R. van den Berg" <srb@cuci.nl>
To: linux-bcache@vger.kernel.org
Subject: 3.18.3 + latest bcache-dev
Date: Wed, 21 Jan 2015 02:24:24 +0100 [thread overview]
Message-ID: <20150121012424.GB5533@cuci.nl> (raw)
I have:
16GB RAM
16GB SSD swap
5 x 6TB HDD bcache backing storage
2 x 490GB SSD bcache cache (Crucial M550, 4KB block, 2M bucket size)
writeback and trim enabled on bcache.
I used the latestbcache tools from git.
On the backing storage, I created a BTRFS using nossd and notrim.
Now, whenever I boot, I end up with exactly 4 bcache_writebac
processes pegged at 99 or 100% CPU. This is on an octocore cpu.
top shows it as 50% system time. The four processes are marked as R,
but I cannot trace them.
Even after waiting for several minutes, the cpu load does not come down.
The mounted volume simply seems to work, though.
Any ideas?
--
Stephen.
next reply other threads:[~2015-01-21 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 1:24 Stephen R. van den Berg [this message]
2015-01-21 8:00 ` 3.18.3 + latest bcache-dev Kent Overstreet
2015-01-21 11:04 ` Stephen R. van den Berg
2015-01-21 16:45 ` Stephen R. van den Berg
2015-01-22 12:33 ` patch (Re: 3.18.3 + latest bcache-dev) Stephen R. van den Berg
2015-01-22 12:56 ` Stephen R. van den Berg
2015-01-21 22:47 ` 3.18.3 + latest bcache-dev Slava Pestov
2015-01-21 23:04 ` Stephen R. van den Berg
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=20150121012424.GB5533@cuci.nl \
--to=srb@cuci.nl \
--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