From: Tomasz Chmielewski <tch@virtall.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: how long should "btrfs device delete missing ..." take?
Date: Thu, 11 Sep 2014 17:22:15 +0200 [thread overview]
Message-ID: <84a98bc5f667c04ca74ff77b56f537d9@admin.virtall.com> (raw)
After a disk died and was replaced, "btrfs device delete missing" is
taking more than 10 days on an otherwise idle server:
# btrfs fi show /home
Label: none uuid: 84d087aa-3a32-46da-844f-a233237cf04f
Total devices 3 FS bytes used 362.44GiB
devid 2 size 1.71TiB used 365.03GiB path /dev/sdb4
devid 3 size 1.71TiB used 58.00GiB path /dev/sda4
*** Some devices missing
Btrfs v3.16
So far, it has copied 58 GB out of 365 GB - and it took 10 days. At this
speed, the whole operation will take 2-3 months (assuming that the only
healthy disk doesn't die in the meantime).
Is this expected time for btrfs RAID-1?
There are no errors in dmesg/smart, performance of both disks is fine:
# hdparm -t /dev/sda /dev/sdb
/dev/sda:
Timing buffered disk reads: 442 MB in 3.01 seconds = 146.99 MB/sec
/dev/sdb:
Timing buffered disk reads: 402 MB in 3.39 seconds = 118.47 MB/sec
# btrfs fi df /home
Data, RAID1: total=352.00GiB, used=351.02GiB
System, RAID1: total=32.00MiB, used=96.00KiB
Metadata, RAID1: total=13.00GiB, used=11.38GiB
unknown, single: total=512.00MiB, used=67.05MiB
# btrfs sub list /home | wc -l
260
# uptime
17:21:53 up 10 days, 6:01, 2 users, load average: 3.22, 3.53, 3.55
I've tried running this on the latest 3.16.x kernel earlier, but since
the progress was so slow, rebooted after about a week to see if the
latest RC will be any faster.
--
Tomasz Chmielewski
http://www.sslrack.com
next reply other threads:[~2014-09-11 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:22 Tomasz Chmielewski [this message]
2014-09-11 19:31 ` how long should "btrfs device delete missing ..." take? Duncan
2014-09-11 21:25 ` Chris Murphy
2014-09-11 23:51 ` Duncan
2014-09-12 2:10 ` Chris Murphy
2014-09-12 5:19 ` Russell Coker
2014-09-12 5:33 ` Duncan
2014-09-12 6:27 ` Chris Murphy
2014-09-12 5:41 ` Duncan
2014-09-12 5:59 ` Duncan
2014-09-11 23:06 ` Tomasz Chmielewski
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=84a98bc5f667c04ca74ff77b56f537d9@admin.virtall.com \
--to=tch@virtall.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 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).