Date: Mon, 3 Aug 2020 14:11:06 -0400 From: Karl Denninger <karl@denninger.net> To: freebsd-fs@freebsd.org Subject: Re: zfs scrub enable by default Message-ID: <b5134ae8-1f3f-25b4-b668-235905a9dca8@denninger.net> In-Reply-To: <0BF85C14-5671-4779-928A-34C5FD3B82C1@lysator.liu.se> References: <cca34d1a-1892-41ec-ce45-84865100c6e1@FreeBSD.org> <20200803121444.J57111@mulder.mintsol.com> <0BF85C14-5671-4779-928A-34C5FD3B82C1@lysator.liu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 8/3/2020 14:05, Peter Eriksson wrote: > On our pretty big ZFS fileservers (home directories) we run scrubs manually but every now and then - but I have a script that pauses the scrubs during “prime time” since a full scrub run takes a day or so... > > > Crontab: > > # zpool-scrub-pause > 0 8 * * 1-5 /sbin/zpool-scrub pause all >/var/liu/log/zpool-scrub-pause 2>&1 > # zpool-scrub-resume > 0 21 * * 1-5 /sbin/zpool-scrub resume all >/var/liu/log/zpool-scrub-resume 2>&1 > > > The script can be downloaded from: > > https://www.grebo.net/~peter/zfs/ <https://www.grebo.net/~peter/zfs/>; > > > Perhaps something similar could be used with configurable “prime time hours”)? > > - Peter > > >> On 3 Aug 2020, at 18:35, Walter Cramer <wfc@mintsol.com> wrote: >> >> Assuming a fairly-idle system, or one with a tiny zpool - scrubs from 'periodic daily' can work fine. >> >> In cases where that assumption is false - the resources consumed by an hours-long scrub, slowing down a system which people expect to be "as responsive as it usually it"... >> >> Our defaults should try to minimize the nasty surprises. >> >> -Walter >> >> >> On Mon, 3 Aug 2020, Steve Wills wrote: >> >>> Hi, >>> >>> I wonder why we don't enable zfs periodic scrub by default? >>> >>> https://svnweb.freebsd.org/base/head/usr.sbin/periodic/periodic.conf?view=markup#l162 >>> >>> Anyone happen to know? >>> >>> Thanks, >>> Steve I will pipe up AGAINST making this a default "do on its own" thing. It is trivially automated in the cron, and this allows it to be tailored by the load pattern and expectations of the individual configuration. A documentation entry explaining the value and need to do it on *some* sort of schedule makes sense, but automating it is IMHO just begging for trouble. The "very small" ZFS system (where there's no actual enhancement to redundancy) is one degenerate case where a noted error can only tell you that you need to find the impacted file(s) and restore them from backup, since there is no ability to work around the fault. On the other hand larger systems where the time required to complete a scan impacts "working hours" (whatever that means in the context of the usual load) will be materially impacted by an automated scan in most cases, and thus should be hand-tuned anyway. -- Karl Denninger karl@denninger.net <mailto:karl@denninger.net> /The Market Ticker/ /[S/MIME encrypted email preferred]/ [-- Attachment #2 --] 0 *H 010 `He 0 *H 00 H^Ōc!5 H0 *H 01 0 UUS10U Florida10U Niceville10U Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA0 170817164217Z 270815164217Z0{1 0 UUS10U Florida10U Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0"0 *H 0 h-5B>[;olӴ0~͎O9}9Ye*$ g !ukvʶLzN`jL>MD'7U 45CB+kY`bd~b*c3Ny-78ju]9H euέsӬDؽmgwER?&UURj'}9nWD i`XcbGz \gG=u%\Oi13ߝ4 K44pYQr]Ie/r0+eEޝݖ0C15Mݚ@JSZ(zȏ NTa(25DD5.l<g[[Z arQQ%Buȴ~~`IohRbʳڟu2MS8EdFUClCMaѳ !}ș+2k/bųE,n当ꖛ\(8 WV8 d]b yXw ܊:I39 00 U ]^§Q\ӎ0U #0T039N0b01 0 UUS10U Florida10U Niceville10U Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA @Ui0U 0 0U 0 *H :P U!>vJ n io -#ן]Wyu jǑR̀Q nƇ!G ѦF g\ yLx gw=OPycehf[ }ܷ['4ڝ\[p 6\o.B&JF" ZC{;*o*mcCcLY߾` t*S!(` ]DHP5A~/NPp6=mhk밣'doA$86hm5ӚS@ j ެEgl )0JG`%k35PaC?σ ׳HEt}!P㏏%*BxbQwaKG$6 h¦Mve; [o-Iی& I,Tc ߎ#t wPA@l0P+KXBպT zGv;NcI3&J ĬUPNa?/%W6G۟N000 k#Xd\ =0 *H 0{1 0 UUS10U Florida10U Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0 170817212120Z 220816212120Z0W1 0 UUS10U Florida10U Cuda Systems LLC10U karl@denninger.net0"0 *H 0 T[I-ΆϏ dn;Å@שy.us~_ZG%<MYd\gvfnsa1'6Egyjs"C [{~ _K Pn+<*pv#Q+H/7[-vqDV^U>f%GX)H.|l`M(Cr >е͇6#odc"YljҦln8@5SA0&ۖ"OGj?UDWZ5 dDB 7k-)9Izs-JAv J 6L$Ն1SmY.Lqw*SH;EF'DĦH]MOgQQ|Mٙג2Z9y@ y]}6ٽeY9Y2xˆ$T=e CǺǵbn֛{j |@LLt1[Dk5:$= ` M 00<+00.0,+0 http://ocsp.cudasystems.net:88880 U 0 0 `HB0U 0 U %0++03 `HB &$OpenSSL Generated Client Certificate0 U %՞V =;bzQ0U #0]^§Q\ӎϡ01 0 UUS10U Florida10U Niceville10U Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA H^Ōc!5 H0 U 0karl@denninger.net0 *H ۠A0-j%--$% g2#ޡ1^>{K+uGE v1ş7Af&b&O; .;A5* U)ND2bF|\= ]<sˋL!wrw٧> YMÄ3\mWR hSv!_zvl? 3_ xU%\^#O*Gk̍YI_&Fꊛ@&1n } ͬ:{hTP3B.;bU8:Z=^Gw8 !k-@xE@i,+'Iᐚ:f hztX7/(hY` O.1}a`%RW^akǂpCAufgDix UTЩ/7}%=jnVZvcF<M= 2^GKH5魉 _O4ެByʈySkw=5@h.0z> W1000{1 0 UUS10U Florida10U Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0 `He E0 *H 1 *H 0 *H 1 200803181106Z0O *H 1B@.8gmf/ƥI8g_{Y3>gS)cK}HmXkPԱRd]M0l *H 1_0]0 `He*0 `He0 *H 0*H 0 *H @0+0 *H (0 +7100{1 0 UUS10U Florida10U Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0 *H 10{1 0 UUS10U Florida10U Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0 *H F#Py\?KmalҭiaTD|s|m dvKQKj\!S1zڢŤ; +?1uҬ K_A*vΏį_ kי K0+rPՈ`8a5 0I摫Gɱ KXpBh@DŽ oL*Nu^ްoBvy +SքKo hg m?dX0k$,A|\lybw)rDQ4 m쇊Nj݀%xVMs ]Ub,ⴼ@9n& BbW]_P&qV g;BTjǧ?LLa螟ޝ Q_i_D(-9 _n +RŐ pN}\/7M]Ԁ TU q`~ frÛP pX%uo`XXne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b5134ae8-1f3f-25b4-b668-235905a9dca8>