[OpenIndiana-discuss] how to stop a zfs resilver

Udo Grabowski (IMK) udo.grabowski at kit.edu
Thu Jun 5 11:39:36 UTC 2014


On 05/06/2014 13:22, John McEntee wrote:
>> This is what we use in /etc/system :
>>
>> set zfs:zfs_resilver_delay = 0
>> set zfs:zfs_scrub_delay = 0
>> set zfs:zfs_top_maxinflight = 128
>> set zfs:zfs_resilver_min_time_ms = 5000
>>
>> Resilver went down from 14 days for a 2 TB disk to 7 hours.
>
>
> Currently the backups overnight have a higher load that during the day.
>
> I  would prefer a resilver taking 14 days and the system being usable  (3 way mirror) than several hours and not being usable. Although a Saturday morning may be a good time to set things off. It takes a couple of hours to the resilver time scale to sort itself out, but it had 12 hours left this morning after running for 16 hours using default values, on 3TB disk with the pool 75% used.
 > What percentage of data used on the pool did you have for your 2TB
 > resilver to take 7 hours? As the amount of data has a linear effect on the 
time taken.

We are usually at 70-80 %. The default resilver tactics (oi_151a7)
is now to have very low priority, but that sucks, and with 40 disks
in a raid_z1 pool one is threatened with a possible second fault in
the same vdisk group. So we changed that to have the fastest
possible resilver and let it run overnight when people don't
feel the performance penalty because they sleep....

-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026



More information about the openindiana-discuss mailing list