From owner-freebsd-current@freebsd.org Tue Oct 4 10:58:35 2016 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 D814FAF4BD8 for ; Tue, 4 Oct 2016 10:58:35 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F5EFF53 for ; Tue, 4 Oct 2016 10:58:34 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.171.4] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1brNBA-0000v2-VR for freebsd-current@freebsd.org; Tue, 04 Oct 2016 12:42:33 +0200 Date: Tue, 4 Oct 2016 12:42:32 +0200 From: Fabian Keil To: freebsd-current@freebsd.org Subject: Re: ZFS - Abyssal slow on copying Message-ID: <20161004124232.6d655b61@fabiankeil.de> In-Reply-To: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/F8ZBStBvUfFgsuEJviflzLx"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 04 Oct 2016 10:58:35 -0000 --Sig_/F8ZBStBvUfFgsuEJviflzLx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "O. Hartmann" wrote: > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:50= CEST 2016 ), I > have a NanoBSD setup which creates an image for a router device. >=20 > The problem I face is related to ZFS. The system has a system's SSD (Sams= ung 850 Pro, > 256GB) which has an UFS filesystem. Aditionally, I have also a backup and= a data HDD, > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both th= e sources for > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing= on the 3 TB > data drive.=20 >=20 > The box itself has 8 GB RAM. When it comes to create the memory disk, whi= ch is ~ 1,3 GB > in size, the NanoBSD script starts creating the memory disk and then inst= alling world > into this memory disk. And this part is a kind of abyssal in terms of the= speed. Can you reproduce the issue if you replace the memory disk with a zvol or tmpfs? While I agree that depulication could be the cause of the problem, it probably wouldn't hurt to rule out a memory-disk related issue before recreating the pool. Fabian --Sig_/F8ZBStBvUfFgsuEJviflzLx Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlfzh5kACgkQBYqIVf93VJ36UQCeLN8gS1+IYN7XyocdiUCxrOtJ GVQAmweiXND8rPccqdMgZFiEf++Dev1H =lnl0 -----END PGP SIGNATURE----- --Sig_/F8ZBStBvUfFgsuEJviflzLx--