From owner-freebsd-current@freebsd.org Thu Dec 14 14:53:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05918E8326B for ; Thu, 14 Dec 2017 14:53:11 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C60B6766D; Thu, 14 Dec 2017 14:53:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.48.220.8]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LwaMR-1f65I20H79-018NuT; Thu, 14 Dec 2017 15:53:01 +0100 Date: Thu, 14 Dec 2017 15:52:27 +0100 From: "O. Hartmann" To: Dimitry Andric Cc: "O. Hartmann" , Daniel Nebdal , FreeBSD CURRENT Subject: Re: ZFS RAIDZ1: resilvering at <17.3M/s => abyssal slow ... Message-ID: <20171214155254.4736ebe5@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20171214124900.64211bd9@thor.intern.walstatt.dynvpn.de> <20171214144351.24a81faa@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/hyN6twzUHfYMOSMxkitjlQ_"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:Ab+suqM924IoWVld3mpkOV5wu9tftOmpcO9Gi9+xbMKBXeAUzLb MPKA5EBYNTmM2c2THx1puHWTFsQYJy3ESOdZeOw+QpSKfFI/HGbO6c1IImr7xAaB5CvDx5E 0QknE/P6B9d78FV/J/7TlMMrwk2x1L8/pLpgx5pYJBQMFvEZZPkUva6WMFQUqTyVO9t+1jH KhlaLGktdg3eXEUD/kySg== X-UI-Out-Filterresults: notjunk:1;V01:K0:EmUVKKZv2Js=:5klgAcOt8/fSm5B6wfTmtv KDmHIh8rdf94wJkVdZ2KvPBaJfRDoh5VpM+ivzpSVEGUMYnq2/CkFQJESVTr+FO5hURwIQO1/ yWMH32JsWzRdaTRfwymue0VIvOY1z14EMz32/3y6RwezIs+shPZ5hhp8yNiFW+khc2/Pryu/O G2HmsDUvrVL8K0k2FYvNbL44haPEJ6unOhsiy8OJn8RslqDd68b5GOvzSSmf8rRm105tKJiSY OorTMA0cktY/znyHSV2BbsdP1YroJT11fL1Ytzdmx01Hq7HW60Sm3b+VSRqckSq9YG8ewUsXn 5Q5tDOTop0pI25KZaDXzkDW33C0Ln0DOEaCP9s/Ux9kySbf5WsiAhBsHjHCiy7f2i1VY45QHi Dh2sSXQoYcLM7vUJAV2jp6xmtF7UbmtXcTK6oxt0uZy4wHLq0Q+D4WGyN9H55gYcOXjz52ZRf 1LFh+JoBbzcB+j7a3TyQB0Xg6Yz8dbSrsYIDvkhEfYqfouvz8YpRY+3L64qk6HgD2ga/rVXW2 oL/pMCZGSIQEPBfVZX75qMX8gEJn368nL+fT67RN5DtKPlvSp4xBEbUE+hg/0/gJbiNzhw6pm R/atHFLrKSHurJfS8Ud8JBadMZ+ciXDW2FopQ1WW7dihl3WRtmMzYZ52pfus4svqUkoy/+beu 4c69Azx6/4ttj0AbCLE14Yk4In1r4siCmD8P5EAFUZW8tZgtu//iPifqALTseoki+7hg53qbb 3OZT2Pb6j1fO9mxFZyEGVv51qCM6OgXI/rSLmlgli82k307dZ0Mybv7lriuwQx3vbO/O8eYr1 DUpVG47Z4e0TS1JL22Lfg1JlMGafQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:53:11 -0000 --Sig_/hyN6twzUHfYMOSMxkitjlQ_ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 14 Dec 2017 15:46:17 +0100 Dimitry Andric schrieb: > On 14 Dec 2017, at 14:43, O. Hartmann wrote: > >=20 > > Am Thu, 14 Dec 2017 14:09:39 +0100 > > Daniel Nebdal schrieb: =20 > >> On Thu, Dec 14, 2017 at 12:48 PM, O. Hartmann = wrote: =20 > >>> I just started the rebuild/resilvering process and watch the pool crw= aling at ~ 18 > >>> MB/s. At the moment, there is no load on the array, the host is a Ivy= Bridge XEON > >>> with 4 core/8 threads and 3,4 GHz and 16 GB of RAM. The HDDs are atta= ched to a > >>> on-board SATA II (300 MB/s max) Intel chip - this just for the record. > >>>=20 > >>> Recently, I switch on the "sync" attribute on most of the defined poo= ls's zfs > >>> filesystems > >>> - I also use a SSD for ZIL/L2ARC caching, but it seems to be unused r= ecently in > >>> FreeBSD CURRENT's ZFS - this from a observers perspective only. > >>>=20 > >>> When scrubbing, I see recently also reduced performance on the pool, = so I'm > >>> wondering about the low throughput at the very moment when resilverin= g is in > >>> progress. > >>>=20 > >>> If the "perspective" of "zpool status" is correct, then I have to wai= t after two > >>> hours for another 100 hours - ~ 4 days? Ups ... I think there is some= thing badly > >>> misconfigured or missing. =20 > ... > >> This is kind of to be expected - for whatever reason, resilvers seem > >> to go super slow at first and then speed up significantly. Just don't > >> ask me how long "at first" is - I'd give it several (more) hours. =20 >=20 > Hopefully this will get better in the future, please read: >=20 > http://open-zfs.org/wiki/Scrub/Resilver_Performance >=20 > -Dimitry >=20 It has already been started to become better ;-) After a while now, the throughput is at 128 MBytes/s and the estimated time= decreased to ~ 8 h now - that is much more appreciable than 4 days ;-) Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/hyN6twzUHfYMOSMxkitjlQ_ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWjKQRgAKCRDS528fyFhY lOuBAgCgcbPikxGm+GdgGbMMdcsdrfuJdmrSheWxSPX5GdkinEQcPaaU4RPGMU1i duPVxun6h2CZOiTdfNEvqHYT8G7KAgCqY598Sbqk+5gXsoRVM9whewSbplC9MEF4 O9+2zS9fNUM9Ky8LryHsQKw/LlpJrzXBPhRBc8dRcl63IQDZE32D =XJAm -----END PGP SIGNATURE----- --Sig_/hyN6twzUHfYMOSMxkitjlQ_--