From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Slow writing of dirty data (bcache)
Date: Mon, 10 Mar 2014 16:14:41 -0500 [thread overview]
Message-ID: <531E2B41.5030605@nuclearwinter.com> (raw)
In-Reply-To: <CALJ65zm4O8KeA1vjhupAFoqh+07qH5OaLMCbm-fShkZk6nf9MA@mail.gmail.com>
This solved my immediate problem. Thank you very much.
Should I keep this array at 0 from now on if I want it to spin down when
idle?
--Larkin
On 3/10/2014 12:12 PM, Kent Overstreet wrote:
>
> echo 0 > writeback_percent...
>
> On Mar 10, 2014 6:07 PM, "Larkin Lowrey" <llowrey@nuclearwinter.com
> <mailto:llowrey@nuclearwinter.com>> wrote:
>
> I'm seeing an odd behavior after updating to kernel
> 3.13.5-202.fc20.x86_64 from 3.12.7-300.fc20.x86_64.
>
> I have a bcache device (bcache2) which backs a raid5 array (md2) that
> has 160+MB of dirty data. The dirty data is being written at a
> rate of 1
> page per second (8 sectors). At this rate it'll take 11 hrs to
> finish. I
> like to keep this array spun down when inactive but the drives can't
> spin down since they're being written to once a second.
>
> # cat /sys/block/bcache2/bcache/writeback_rate
> 512
>
> # cat /sys/block/bcache2/bcache/writeback_rate_debug
> rate: 512/sec
> dirty: 161M
> target: 40.8G
> proportional: -35.2M
> derivative: 0
> change: -35.2M/sec
> next io: 624ms
>
> This never happened when running 3.12.7. Is there anything I can do
> about this?
>
> --Larkin
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-03-10 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 16:34 Slow writing of dirty data (bcache) Larkin Lowrey
2014-03-10 20:56 ` Sitsofe Wheeler
[not found] ` <CALJ65zm4O8KeA1vjhupAFoqh+07qH5OaLMCbm-fShkZk6nf9MA@mail.gmail.com>
2014-03-10 21:14 ` Larkin Lowrey [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=531E2B41.5030605@nuclearwinter.com \
--to=llowrey@nuclearwinter.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 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.