From: Matthias Ferdinand <bcache@mfedv.net>
To: 朱菁 <zhujing@ecloudtech.com.cn>
Cc: linux-bcache@vger.kernel.org
Subject: Re: 答复: a strange bcache0 100% busy with no IO rw and no cpu consumption
Date: Sun, 14 May 2017 15:53:49 +0200 [thread overview]
Message-ID: <20170514135349.GA28395@xoff> (raw)
In-Reply-To: <000e01d2cc95$1b81cad0$52856070$@ecloudtech.com.cn>
On Sun, May 14, 2017 at 05:33:12PM +0800, 朱菁 wrote:
> Hi:
> Thx for your reply.
> /dev/sdb on esxi-node equal bcache0 on stor-node.
sorry, it just looked too easy :-)
I have also seen suspiciously high iostat values on bcache devices,
where extreme values of "wkB/s" go together with high "avgrq-sz"
(probably a derived value), but never on two consecutive measurements,
always several days in between. But "%util" always looked ok.
Since iostat is just reading /proc/diskstat, I would rather suspect some
(bcache related) bug there.
Sometimes I also see funny numbers in writeback_rate_debug, e.g.
increasing "dirty" values like this:
2.8M .. 2.9M .. 2.10M .. 3.0M
Matthias
prev parent reply other threads:[~2017-05-14 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 3:20 a strange bcache0 100% busy with no IO rw and no cpu consumption 朱菁
[not found] ` <20170514084515.GA23435@xoff>
[not found] ` <000e01d2cc95$1b81cad0$52856070$@ecloudtech.com.cn>
2017-05-14 13:53 ` Matthias Ferdinand [this message]
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=20170514135349.GA28395@xoff \
--to=bcache@mfedv.net \
--cc=linux-bcache@vger.kernel.org \
--cc=zhujing@ecloudtech.com.cn \
/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