I opted to use a two disk mirror, and offline the slow disk. Hourly cronjob to online the slow disk, wait, and then offline it again.
Gives me the benefit of automatic fixes in the event of bit rot in any blocks more then an hour old too.
I opted to use a two disk mirror, and offline the slow disk. Hourly cronjob to online the slow disk, wait, and then offline it again.
Gives me the benefit of automatic fixes in the event of bit rot in any blocks more then an hour old too.
That sounds cool; is it possible to just query the ZFS system to know when it has finished synchronizing the slow disk, before bringing it offline again? Do you think that stopping and spinning the disk again, 24 times a day, is not going to cause much wear to the motors?
That is another way, though annoying if you've set up automatic error reporting.