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:29:06 -0400 [thread overview]
Message-ID: <48569892-8E0C-4C28-87B1-60CD562AA9EF@up4.com> (raw)
In-Reply-To: <20150617132736.GT9850@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
> On Jun 17, 2015, at 9:27 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
>
> On Wed, Jun 17, 2015 at 09:13:08AM -0400, Vincent Olivier wrote:
>>
>>> 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.
>
> In most cases, all you need to do is clean up one data chunk to
> give the metadata enough space to work in. Instead of manually
> iterating through several values of usage= until you get a useful
> response, you can use limit=<n> to stop after <n> successful block
> group relocations.
Nice! Will do that instead! Thanks.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-06-17 13:29 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
2015-06-17 13:27 ` Hugo Mills
2015-06-17 13:29 ` Vincent Olivier [this message]
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=48569892-8E0C-4C28-87B1-60CD562AA9EF@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 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.