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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
