From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
Date: Fri, 22 Jan 2016 14:51:47 +0000 (UTC) [thread overview]
Message-ID: <pan$3f45c$28137200$2a7440f$6da4e9ad@cox.net> (raw)
In-Reply-To: 56A230C3.3080100@netcologne.de
Christian Rohmann posted on Fri, 22 Jan 2016 14:38:11 +0100 as excerpted:
> I am currently doing a big "btrfs balance" to extend a 8 drive RAID6 to
> 12 drives using
> "btrfs balance start -dstripes 1..11 -mstripes 1..11"
>
> With kernel 4.4 and btrfs progs 4.4 it's running fine for a few days now
> and the new disks are slowing getting more and more extents.
> But somehow the process is VERY slow (3% in 3 days) and there is almost
> no additional disk utilization.
>
> The process doing the balance is doing 100% cpu (one core) so apparently
> the whole thing is very much single threaded and therefore CPU-bound in
> this case.
>
> Is this a known issue or is there anything I can do to speed this up? I
> mean the disks have plenty of iops left to work with and the box has
> many more CPU cores idling away.
[This is only intended to be a stop-gap reply, until someone with more
detailed/direct knowledge/experience on the topic can reply.]
My own use-case is btrfs raid1, but from what I've seen on the list,
raid56 mode maintenance that involves recalculating parity, as converting
from an 8-device stripe to a 12-device stripe will, is indeed /very/ slow.
I didn't know it was single-core limited, however. If it's slow/complex
calculations, AND limited to a single core, plus given the likely size of
a filesystem of 8-12 devices in the day of multi-TB devices... ~1%/day,
100 days to complete... Ouch, that's going to be painful!
The good thing is that it happens online, so you can be using the
filesystem and the other cores while it's happening. Plus, balances are
interruptable. You can reboot or whatever and it should pick up and
continue where it left off.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-01-22 14:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 13:38 btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core? Christian Rohmann
2016-01-22 14:51 ` Duncan [this message]
2016-01-24 2:30 ` Henk Slager
2016-01-25 11:34 ` Christian Rohmann
2016-01-25 22:13 ` Chris Murphy
[not found] ` <CAKZK7uxdX9UBPOKButtPjqBOdVUfHdRTimP+W34fkz1h9P+wHg@mail.gmail.com>
2016-01-26 0:44 ` Fwd: " Justin Brown
2016-01-26 5:17 ` Chris Murphy
2016-01-26 6:14 ` Chris Murphy
2016-01-26 8:54 ` Christian Rohmann
2016-01-26 19:26 ` Chris Murphy
2016-01-26 19:27 ` Chris Murphy
2016-01-26 19:57 ` Austin S. Hemmelgarn
2016-01-26 20:20 ` Chris Murphy
2016-01-27 8:48 ` Christian Rohmann
2016-01-27 16:34 ` Austin S. Hemmelgarn
2016-01-27 20:58 ` bbrendon
2016-01-27 21:53 ` Chris Murphy
2016-01-28 12:27 ` Austin S. Hemmelgarn
2016-02-01 14:10 ` Christian Rohmann
2016-02-01 20:52 ` Chris Murphy
2016-02-09 13:48 ` Christian Rohmann
2016-02-09 16:46 ` Marc MERLIN
2016-02-09 21:46 ` Chris Murphy
2016-02-10 2:23 ` Chris Murphy
2016-02-10 2:36 ` Chris Murphy
2016-02-10 13:19 ` Christian Rohmann
2016-02-10 19:16 ` Chris Murphy
2016-02-10 19:38 ` Chris Murphy
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='pan$3f45c$28137200$2a7440f$6da4e9ad@cox.net' \
--to=1i5t5.duncan@cox.net \
--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.