public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Olivier <vincent@up4.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID10 Balancing Request for Comments and Advices
Date: Wed, 17 Jun 2015 09:13:08 -0400	[thread overview]
Message-ID: <80BA2964-3B67-430B-99BE-62A348C5DBED@up4.com> (raw)
In-Reply-To: <CAJCQCtRGxCr4GaVwkA0QpK8dYjhaBS0-rmi=ymPxycQiGUa_fg@mail.gmail.com>


> On Jun 16, 2015, at 8:14 PM, Chris Murphy <lists@colorremedies.com> wrote:
> 
> On Tue, Jun 16, 2015 at 5:58 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> 
>> On a current kernel unlike older ones, btrfs actually automates entirely
>> empty chunk reclaim, so this problem doesn't occur anything close to near
>> as often as it used to.  However, it's still possible to have mostly but
>> not entirely empty chunks that btrfs won't automatically reclaim.  A
>> balance can be used to rewrite and combine these mostly empty chunks,
>> reclaiming the space saved.  This is what Hugo was recommending.
> 
> Yes, as little as a -dusage=5 (data chunks that are 5% or less full)
> can clear the problem and is very fast, seconds. Possibly a bit
> longer, many seconds o single digit minutes is -dusage=15. I haven't
> done a full balance in forever.


Yes, on this 80% full 6x4TB RAID10 -dusage=15 took 2 seconds and relocated "0 out of 3026 chunks”.

Out of curiosity, I had to use -dusage=90 to have it relocate only 1 chunk and it took les than 30 seconds.

So I put a -dusage=25 in the weekly cron just before the scrub.

FYI.

Thanks for your help.

  reply	other threads:[~2015-06-17 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 12:09 RAID10 Balancing Request for Comments and Advices Vincent Olivier
2015-06-16 12:25 ` Hugo Mills
2015-06-16 13:34   ` Vincent Olivier
2015-06-16 23:58     ` Duncan
2015-06-17  0:14       ` Chris Murphy
2015-06-17 13:13         ` Vincent Olivier [this message]
2015-06-17 13:27           ` Hugo Mills
2015-06-17 13:29             ` Vincent Olivier
2015-06-18  4:37             ` Duncan
2015-06-17 13:46       ` Vincent Olivier
2015-06-18  8:00         ` Duncan

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=80BA2964-3B67-430B-99BE-62A348C5DBED@up4.com \
    --to=vincent@up4.com \
    --cc=linux-btrfs@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