[zfs] RE: granularity of performance penalty from resilvering

Jason Matthews jason at broken.net
Wed Oct 21 01:29:00 UTC 2015



you could look at these tunables (not the settings themselves)...

these settings actually make resilvers have a higher priority. You 
obviously would want to go the other way.

j.

|* Prioritize resilvering by setting the delay to zero
set zfs:zfs_resilver_delay = 0||

* Prioritize scrubs by setting the delay to zero
set zfs:zfs_scrub_delay = 0

||* resilver for five seconds per TXG
set zfs:zfs_resilver_min_time_ms = 5000

|
|echo zfs_resilver_delay/w0 | mdb -kw
echo zfs_scrub_delay/w0 |mdb -kw
echo zfs_top_maxinflight/w7f |mdb -kw
echo zfs_resilver_min_time_ms/w1388 |mdb -kw


|
On 10/19/2015 11:49 PM, Fred Liu wrote:
>
> Yes, “zpool scrub –s” can stop the resilvering.
>
> *From:*Fred Liu
> *Sent:* 星 期二, 十月20, 2015 12:15
> *To:* 'zfs-discuss at list.zfsonlinux.org'; developer; illumos-zfs; 
> freebsd-fs; zfs-discuss
> *Subject:* granularity of performance penalty from resilvering
>
> Sorry if is a duplicate thread.
>
> The last suffering has been lasted for two weeks for we replaced a 6TB 
> HDD.
>
> There should be some IO throttle measure from ZFS software stack. At 
> least, we can try to stop resilvering like scrubbing
>
> if the realization is quiet complicated.
>
> Besides that, will nice zil/cache be relief?
>
> Thanks.
>
> Fred
>
> *illumos-zfs* | Archives 
> <https://www.listbox.com/member/archive/182191/=now> 
> <https://www.listbox.com/member/archive/rss/182191/22567878-8480fd5f> 
> | Modify 
> <https://www.listbox.com/member/?member_id=22567878&id_secret=22567878-f5b912c9> 
> Your Subscription 	[Powered by Listbox] <http://www.listbox.com>
>



More information about the freebsd-fs mailing list