NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
BTRFS scrub speed is insanely slow.
So I have a RN104, with about 10TB of disk space. When I set it to do a BTRFS scrub, the speed is horrific. I'm getting something like 30GB/hour of scrub speed. At the present rate, it would take ...
You can check the smart stats by downloading the log zip file. Disk_info.log is a good place to look, as is smart_history.log.
There are other RN104 users who post here. I have an RN102 that I'm not using right now, but that might behave differently than an RN104 running XRAID with mismatched disks.
Thanks, this is helpful to know. The tables look pretty clean to me...
time model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors
------------------- -------------------- -------------------- ------------ ------------ -------------- ---------- ------------ ------------ ----------------- ----------
2015-02-21 19:03:53 WDC WD20EARX-32PASB0 WD-WCAZAF733419 -1 -1 -1 -1 -1 -1 -1 0
2015-02-21 19:03:53 ST3000DM001-1ER166 W500F7RK -1 -1 -1 -1 -1 -1 -1 0
2015-02-21 19:03:53 ST3000DM001-1ER166 W500F8PV -1 -1 -1 -1 -1 -1 -1 0
2015-02-21 19:03:53 ST3000DM001-1ER166 W500F7XV -1 -1 -1 -1 -1 -1 -1 0
2015-02-21 19:05:41 WDC WD20EARX-32PASB0 WD-WCAZAF733419 0 0 0 -1 -1 0 0 0
2015-02-21 19:05:41 ST3000DM001-1ER166 W500F7RK 0 0 0 0 0 0 0 0
2015-02-21 19:05:41 ST3000DM001-1ER166 W500F8PV 0 0 0 0 0 0 0 0
2015-02-21 19:05:41 ST3000DM001-1ER166 W500F7XV 0 0 0 0 0 0 0 0
And disk_info.log doesn't look like it has anything worrying. The first HD (the 2TB one) is a bit older than the others, and it spent a lot of its life in a computer where it spun up and down a lot (It's also a WD green, known for this sort of thing), but it doesn't look like it is reporting any issues. I think the disks are no better or worse off now than they were a year or so ago when I first started having these issues.
Device: sdd
Controller: 0
Channel: 0
Model: WDC WD20EARX-32PASB0
Serial: WD-WCAZAF733419
Firmware: 51.0AB51
Class: SATA
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 2fe4ed8e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 43
Start/Stop Count: 264
Power-On Hours: 31597
Power Cycle Count: 76
Load Cycle Count: 1470451
Device: sdc
Controller: 0
Channel: 1
Model: ST3000DM001-1ER166
Serial: W500F7RK
Firmware: CC25
Class: SATA
RPM: 7200
Sectors: 5860533168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 2fe4ed8e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 49
Start/Stop Count: 44
Power-On Hours: 15656
Power Cycle Count: 43
Load Cycle Count: 85
Device: sdb
Controller: 0
Channel: 2
Model: ST3000DM001-1ER166
Serial: W500F8PV
Firmware: CC25
Class: SATA
RPM: 7200
Sectors: 5860533168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 2fe4ed8e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 50
Start/Stop Count: 42
Power-On Hours: 15657
Power Cycle Count: 42
Load Cycle Count: 82
Device: sda
Controller: 0
Channel: 3
Model: ST3000DM001-1ER166
Serial: W500F7XV
Firmware: CC25
Class: SATA
RPM: 7200
Sectors: 5860533168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 2fe4ed8e
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 46
Start/Stop Count: 42
Power-On Hours: 15657
Power Cycle Count: 42
Load Cycle Count: 82
The disk health looks fine to me too.
FWIW, the 3 TB Seagate DM drives are known to have high failure rates with RAID. But there's no evidence of problems with your particular drives.
When the time comes to replace them (and the WD green), I recommend using NAS-purposed drives - WDC Red or Seagate Ironwolf models. I use Reds myself.
So it's not the disk health, and it's not something loading down the CPU (other than the scrub itself). Have you tried measuring NAS throughput when scrubs aren't running? For instance using NAStester on a PC? http://www.808.dk/?code-csharp-nas-performance
Yes, I have. In particular, to take the network out of the picture, I've tried to just sha1sum the files on the disk. This is a worst case, since the sha1 itself should take quite a lot of CPU. It runs much faster than the scrubs, around 1.5 GB/minute. At that rate, I would go through the full 4TB in about 1.5-2 days, which is just what I see if I run an sha1sum on every file using find. This is what I would expect to see from the scrub, or better. So the NAS has no trouble reading all the data off these disks in some reasonable amount of time.
This is totally a software bug.
a) Same hardware
b) Only the OS version changed
c) Nothing running
d) No hardware problems
e) Hardware has no problem reading and even sha1 hashing the data in a reasonable amount of time
f) defrags and rebalances work in a reasonable amount of time (~1 day)
g) Scrubs are horrifically slow (~20+ days), at least 10x slower than anything else that runs on this thing.
There's really nothing else it could be.
It would have to be a bug/performance bottleneck in BTRFS itself.
BTRFS checksums use CRC32c, and they are block-based not file based (done on 4K blocks). CRC32 should be significantly faster than SHA-1 (perhaps 60% fewer cycles). Since checksum verification is always done, your sha1sum test is actually computing both the BTRFS checksums and the SHA-1 hashes.
FWIW, my last scrub took about 31 hours on my RN526. Disk configuration is 4x6TB RAID-5, with about 8.5 TiB of data (including snapshots). Roughly 75 MB/s.
For 4.2Tb raid 1 it took me around 15hrs!
On my RN316.
aalexandrebeta wrote:
For 4.2Tb raid 1 it took me around 15hrs!
On my RN316.
That sounds about right actually.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
