Date: Thu, 14 Dec 2017 15:52:27 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: "O. Hartmann" <ohartmann@walstatt.org>, Daniel Nebdal <dnebdal@gmail.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: ZFS RAIDZ1: resilvering at <17.3M/s => abyssal slow ... Message-ID: <20171214155254.4736ebe5@thor.intern.walstatt.dynvpn.de> In-Reply-To: <B02D080F-96B1-4456-8D19-21F89821E2C0@FreeBSD.org> References: <20171214124900.64211bd9@thor.intern.walstatt.dynvpn.de> <CA%2Bt49PJuznLxGnLERwAhVW2CjETJYWO6rKcWo3qOo5bZLQkqYA@mail.gmail.com> <20171214144351.24a81faa@thor.intern.walstatt.dynvpn.de> <B02D080F-96B1-4456-8D19-21F89821E2C0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Am Thu, 14 Dec 2017 15:46:17 +0100 Dimitry Andric <dim@FreeBSD.org> schrieb: > On 14 Dec 2017, at 14:43, O. Hartmann <ohartmann@walstatt.org> wrote: > > > > Am Thu, 14 Dec 2017 14:09:39 +0100 > > Daniel Nebdal <dnebdal@gmail.com> schrieb: > >> On Thu, Dec 14, 2017 at 12:48 PM, O. Hartmann <ohartmann@walstatt.org> wrote: > >>> I just started the rebuild/resilvering process and watch the pool crwaling at ~ 18 > >>> MB/s. At the moment, there is no load on the array, the host is a IvyBridge XEON > >>> with 4 core/8 threads and 3,4 GHz and 16 GB of RAM. The HDDs are attached to a > >>> on-board SATA II (300 MB/s max) Intel chip - this just for the record. > >>> > >>> Recently, I switch on the "sync" attribute on most of the defined pools's zfs > >>> filesystems > >>> - I also use a SSD for ZIL/L2ARC caching, but it seems to be unused recently in > >>> FreeBSD CURRENT's ZFS - this from a observers perspective only. > >>> > >>> When scrubbing, I see recently also reduced performance on the pool, so I'm > >>> wondering about the low throughput at the very moment when resilvering is in > >>> progress. > >>> > >>> If the "perspective" of "zpool status" is correct, then I have to wait after two > >>> hours for another 100 hours - ~ 4 days? Ups ... I think there is something badly > >>> misconfigured or missing. > ... > >> 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. > > Hopefully this will get better in the future, please read: > > http://open-zfs.org/wiki/Scrub/Resilver_Performance > > -Dimitry > 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 -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWjKQRgAKCRDS528fyFhY lOuBAgCgcbPikxGm+GdgGbMMdcsdrfuJdmrSheWxSPX5GdkinEQcPaaU4RPGMU1i duPVxun6h2CZOiTdfNEvqHYT8G7KAgCqY598Sbqk+5gXsoRVM9whewSbplC9MEF4 O9+2zS9fNUM9Ky8LryHsQKw/LlpJrzXBPhRBc8dRcl63IQDZE32D =XJAm -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171214155254.4736ebe5>