From: Jorge Bastos <jorge.mrbastos@gmail.com>
To: Robert Krig <robert.krig@render-wahnsinn.de>
Cc: Chris Murphy <lists@colorremedies.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How long should a btrfs scrub with RAID5/6 take?
Date: Thu, 9 Jan 2020 08:57:16 +0000 [thread overview]
Message-ID: <CAHzMYBSrZdjwJcMj86u8Dr_imxyiRN5yE=cFgNC9Tofb42umXw@mail.gmail.com> (raw)
In-Reply-To: <0530e18f43a5f31ff8d446be362951f68068b5db.camel@render-wahnsinn.de>
I reported recently to the list there there's a performance problem
with scrubs on raid5/6 pools, initial report and followups here:
https://lore.kernel.org/linux-btrfs/CAHzMYBTXvY1VgcoFDUvc2NFmVKq2HJRHuS0VXzoneUMh79cySA@mail.gmail.com/
Quick recap:
4 disk raid5 (raid1 metadata)
UUID: b75ee8b5-ae1c-4395-aa39-bebf10993057
Scrub started: Wed Nov 27 07:32:46 2019
Status: running
Duration: 7:34:50
Time left: 1:52:37
ETA: Wed Nov 27 17:00:18 2019
Total to scrub: 1.20TiB
Bytes scrubbed: 982.05GiB
Rate: 36.85MiB/s
Error summary: no errors found
11 disk raid5 (raid1 metadata)
UUID: 1236acc8-dbd5-41bd-bf3d-872a8fbbce49
Scrub started: Sun Dec 15 11:23:45 2019
Status: running
Duration: 0:51:34
Time left: 90:06:52
ETA: Thu Dec 19 06:22:13 2019
Total to scrub: 18.10TiB
Bytes scrubbed: 175.12GiB
Rate: 57.96MiB/s
Error summary: no errors found
Same 11 disk pool during a btrfs send to /dev/null confirming it's
capable of much better read speeds:
btrfs send /mnt/disks/Pics/T12_disk1_Pics_2019-12-15-0829/ | pv -bart
> /dev/null
At subvol /mnt/disks/Pics/T12_disk1_Pics_2019-12-15-0829/
447GiB 0:13:19 [ 635MiB/s] [ 573MiB/s]
Current speed 635MiB/s, average speed so far 573MiB/s
next prev parent reply other threads:[~2020-01-09 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 10:13 How long should a btrfs scrub with RAID5/6 take? Robert Krig
2020-01-08 17:07 ` Joshua
2020-01-08 21:49 ` Chris Murphy
2020-01-09 6:38 ` Robert Krig
2020-01-09 8:57 ` Jorge Bastos [this message]
2020-01-09 22:48 ` 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='CAHzMYBSrZdjwJcMj86u8Dr_imxyiRN5yE=cFgNC9Tofb42umXw@mail.gmail.com' \
--to=jorge.mrbastos@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=robert.krig@render-wahnsinn.de \
/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;
as well as URLs for NNTP newsgroup(s).