3 ms·
What I was questioning was that it shouldn't be taking weeks because the write speed of a single disk is enough to fill it in a day or two with sequential IO. I
by the8472 6y ago
What I was questioning was that it shouldn't be taking weeks because the write speed of a single disk is enough to fill it in a day or two with sequential IO. I.e. the sequential resilver alone should be enough to fix the "can take weeks" problem.
Additional speed on top of that is nice of course, if you're using such wide pools.
- magicalhippo 6y agoWith DRAID you'd cut down the time to an hour or so though. Not sure how much that matters in practice, I've just got a home NAS with 6 disks to play with.
- e12e 6y agoI get that using hot virtual spares is much better, I also wonder at a week to write 12tb. 12tb at 200 mb/s is roughly 20 hours. Is it the fact that you get 12tb of essentially non sequencial io mixed with random reads during the rebuild? Still 20 mb/s seems 1990s slow writing tio a mechanical HD? Ed: ok, ok, from tfa: > For 14 wide RAID-Z2 vdevs using 12TB spindles, rebuilds can take weeks. Resilver I/O activity is deprioritized when the system has not been idle for a minimum period. Full zpools get fragmented and require additional I/O’s to recalculate data during reslivering. Obviously writing 12 tb at 0 mb/s will take time..