> From: Richard Elling [mailto:richard.ell...@gmail.com] > > > In one of my systems, I have 1TB mirrors, 70% full, which can be > > sequentially completely read/written in 2 hrs. But the resilver took 12 > > hours of idle time. Supposing you had a 70% full pool of raidz3, 2TB disks, > > using 10 disks + 3 parity, and a usage pattern similar to mine, your > > resilver time would have been minimum 10 days, > > bollix > > Resilver time is not a significant problem with ZFS. Resilver time is a much > bigger problem with traditional RAID systems. In any case, it is bad systems > engineering to optimize a system for best resilver time.
Because RE seems to be emotionally involved with ZFS resilver times, I don't believe it's going to be productive for me to try addressing his off-hand comments. Instead, I'm only going to say this much: In my system mentioned above, a complete disk can be copied to another complete disk, sequentially, in 131 minutes. But during idle time it took 12 hours because ZFS resilver only does the used parts of disk, in essentially random order. So ZFS resilver often takes many times longer than a complete hardware-based complete disk resilver. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
