From: Chris Murphy <lists@colorremedies.com>
To: Christian Rohmann <crohmann@netcologne.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
Date: Mon, 25 Jan 2016 23:14:37 -0700 [thread overview]
Message-ID: <CAJCQCtTA4qUNX1R3Pgxq-17zAPJvwPGfO_Fo-qEy2LsQrpF+fg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQe=X4FPzTBKBpP826nswGQyiY4sNES9GugLju3-9HARA@mail.gmail.com>
1495MiB used raid6 in a VM using 4x qcow2 files on an SSD.
Host is using kernel 4.4.0
Guest is using kernel 4.5.0rc0.git9.1.fc24 (this is a Fedora Rawhide
debug kernel so it'll be a bit slower), btrfs-progs 4.3.1
Not degraded, balance takes 11 seconds, that's ~136MiB/s
iotop isn't consistent, max is ~300MiB/s write.
Reboot with 1 device missing and a new empty qcow2 in its place, mount
degraded and 'btrfs replace' takes 13 seconds according to 'btrfs
replace status'.
I don't know that this is very useful information though.
Christian, what are you getting for 'iotop -d3 -o' or 'iostat -d3'. Is
it consistent or is it fluctuating all over the place? What sort of
eyeball avg/min/max are you getting?
Chris Murphy
next prev parent reply other threads:[~2016-01-26 6:14 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 ` Fwd: " Justin Brown
2016-01-26 5:17 ` Chris Murphy
2016-01-26 6:14 ` Chris Murphy [this message]
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=CAJCQCtTA4qUNX1R3Pgxq-17zAPJvwPGfO_Fo-qEy2LsQrpF+fg@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=crohmann@netcologne.de \
--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.