5 ms·
> The rebuild times in this post seem high to me, though. Two factors. Disks are getting large, and the rebuild time for RAID-Z[1] is dependent on the fragment
by magicalhippo 6y ago
> The rebuild times in this post seem high to me, though.
Two factors. Disks are getting large, and the rebuild time for RAID-Z[1] is dependent on the fragmentation. In combination it means it can take ages.
I just had to replace a failing WD Red 3TB[2] in an old 4xRAID-Z1 pool, and it took 9 hours. That was a single 3TB disk. The disks in my new pool are 14TB and 16TB.
[1]: https://youtu.be/Efl0Kv_hXwY https://youtu.be/Efl0Kv_hXwY
[2]: power-on hours in SMART showed over 7 years
- throw0101a 6y agoOpenZFS 2.0 has sequential rebuilds: > The sequential reconstruction feature adds a more traditional RAID rebuild mechanism to ZFS. Specifically, it allows for mirror vdevs to be rebuilt in LBA order. Depending on the pools average block size, overall fragmentation, and the performance characteristics of the devices (SMR) sequential reconstruction can restore redundancy in less time than a traditional healing resilver. However, it cannot verify block checksums as part of the rebuild. Therefore a scrub is automatically started when the last active sequential resilver completes. * https://github.com/openzfs/zfs/pull/10349 https://github.com/openzfs/zfs/pull/10349
- magicalhippo 6y agoYeah I linked to the OpenZFS Developer Summit video on the feature, but forgot to mention it in my post.