linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Larkin Lowrey <llowrey@nuclearwinter.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Slow writing of dirty data (bcache)
Date: Mon, 10 Mar 2014 20:56:20 +0000	[thread overview]
Message-ID: <20140310205612.GA19912@sucs.org> (raw)
In-Reply-To: <531DE9A5.90801@nuclearwinter.com>

On Mon, Mar 10, 2014 at 11:34:45AM -0500, Larkin Lowrey wrote:
> 
> 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.
> 
> This never happened when running 3.12.7. Is there anything I can do
> about this?

I believe this is intended behaviour - as the cache approaches the
writeback_percent level of fullness the rate of writeback will increase.
It is possible to override the writeback_rate by echoing a new value
into it but it will also change itself so you may find the rate falls
again...  Perhaps that can be avoided by echoing 0 into
writeback_percent too (see
http://evilpiepirate.org/git/linux-bcache.git/tree/Documentation/bcache.txt?h=bcache-dev#n265)...

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2014-03-10 20:56 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 [this message]
     [not found] ` <CALJ65zm4O8KeA1vjhupAFoqh+07qH5OaLMCbm-fShkZk6nf9MA@mail.gmail.com>
2014-03-10 21:14   ` Larkin Lowrey

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=20140310205612.GA19912@sucs.org \
    --to=sitsofe@yahoo.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=llowrey@nuclearwinter.com \
    /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;
as well as URLs for NNTP newsgroup(s).