From: Justin Brown <justin.brown@fandingo.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Fwd: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
Date: Mon, 25 Jan 2016 18:44:37 -0600 [thread overview]
Message-ID: <CAKZK7uxOihVUSo9+LPfUxG7WawggkXSoaTbMVa3a4pkSEuxJdQ@mail.gmail.com> (raw)
In-Reply-To: <CAKZK7uxdX9UBPOKButtPjqBOdVUfHdRTimP+W34fkz1h9P+wHg@mail.gmail.com>
> Does anyone suspect a kernel regression here? I wonder if its worth it
> to suggest testing the current version of all fairly recent kernels:
> 4.5.rc1, 4.4, 4.3.4, 4.2.8, 4.1.16?
I don't have any useful information about parity RAID modes or large
arrays, so this might be totally useless. Nonetheless, just last week
I added a 2TB drive to an existing Btrfs raid10 array (5x 2TB before
addition) and did a balance afterwards. I don't take any numbers, but
I was frequently looking at htop and iotop. I thought the numbers were
extremely good: 100-120MB/s sustained for each drive with the "total"
reported by iotop exceeding 600MB/s. That's with integrated sata
controller on an Intel Z97 mini-ITX motherboard (cpu i4770).
Significantly faster than anticipated. I started it one evening, and
it was finished when I awoke the next morning.
That was on 4.2.8-300.fc23.x86_64 with btrfs-progs 4.3.1.
next prev parent reply other threads:[~2016-01-26 0:44 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
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 ` Justin Brown [this message]
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=CAKZK7uxOihVUSo9+LPfUxG7WawggkXSoaTbMVa3a4pkSEuxJdQ@mail.gmail.com \
--to=justin.brown@fandingo.org \
--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.