June 17, 20197 yr Hi, I just started yesterday to create a pool of 8 x 6 TB data plus 2 x 6 TB parity. The parity building is supposed to take about 6 days. Is there a way to speed this up by increasing I/O priority or so (just like in the good old mdadm days)? Thanks! tower-diagnostics-20190617-1638.zip
June 17, 20197 yr Community Expert No. The parity check always runs flat out according to what your hardware supports. Having said that 6 days sounds too long so not sure what is causing that.
June 17, 20197 yr Community Expert 2-3 hours per TB of parity, so 12-18 hours would be normal. Something abnormal for you. On mobile now so will look at diagnostics later if nobody else does.
June 17, 20197 yr Author 27 minutes ago, johnnie.black said: There is something writing to disk1 I stopped this writing on disk 1 in the meanwhile. But still the creation speed on both parity disks is 30 MB/s. Is this normal? There is plenty of CPU and IO available... Edited June 17, 20197 yr by Raki72
June 17, 20197 yr Author 4 hours ago, johnnie.black said: Post new diags without writes. Here we go. Thanks for your support. Could it be that my system is hitting the maximum bandwidth of USB 3? tower-diagnostics-20190617-1902.zip Edited June 17, 20197 yr by Raki72
June 18, 20197 yr 9 hours ago, Raki72 said: Here we go. Thanks for your support. Could it be that my system is hitting the maximum bandwidth of USB 3? tower-diagnostics-20190617-1902.zip 107.88 kB · 1 download you're using USB? yeah, that will make it slower for alot of reasons and the overhead usb bring along... if you are going to use usb, expect it to be alot slower than if it were sata/sas.
June 18, 20197 yr Community Expert USB is not recommended for array devices, for performance and reliability reasons.
Archived
This topic is now archived and is closed to further replies.