From owner-freebsd-current@freebsd.org Mon Oct 3 09:31:05 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 18CD8AC625C for ; Mon, 3 Oct 2016 09:31:05 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 D04A77D8; Mon, 3 Oct 2016 09:31:04 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bqzaK-000Q2u-B3>; Mon, 03 Oct 2016 11:30:56 +0200 Received: from x4e34adaa.dyn.telefonica.de ([78.52.173.170] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bqzaK-003Tg5-0l>; Mon, 03 Oct 2016 11:30:56 +0200 Date: Mon, 3 Oct 2016 11:30:50 +0200 From: "O. Hartmann" To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: ZFS - Abyssal slow on copying Message-ID: <20161003113050.0f1b09bd.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/6xEaX9simWG6gXG.eqLpTJs"; protocol="application/pgp-signature" X-Originating-IP: 78.52.173.170 X-ZEDAT-Hint: A 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: Mon, 03 Oct 2016 09:31:05 -0000 --Sig_/6xEaX9simWG6gXG.eqLpTJs Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 2 Oct 2016 15:30:41 -0400 Allan Jude schrieb: > On 2016-10-02 15:25, O. Hartmann wrote: > >=20 > > 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 (Sa= msung 850 Pro, > > 256GB) which has an UFS filesystem. Aditionally, I have also a backup a= nd a data HDD, > > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both = the sources for > > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residi= ng on the 3 TB > > data drive.=20 > >=20 > > The box itself has 8 GB RAM. When it comes to create the memory disk, w= hich is ~ 1,3 > > GB in size, the NanoBSD script starts creating the memory disk and then= installing > > world into this memory disk. And this part is a kind of abyssal in term= s of the speed. > >=20 > > The drive sounds like hell, the heads are moving rapidly. The copy spee= d is incredibly > > slow compared to another box I usually use in the lab with UFS filesyst= em only > > (different type of HDD). > >=20 > > The whole stuff the nanbsd is installed from and to is on a separate ZF= S partition, > > but in the same pool as everything else. When I first setup the new par= titions, I > > switched on deduplication, but I quickly deactivated it, because it had= a tremendous > > impact on the working speed and memory consumption on that box. But som= ething seems > > not right since then - as I initially described, the copy/initialisation > > speed/bandwith is abyssal. Well, I also fear that I did something wrong= when I firt > > initialised the HDD - there is this 125bytes/4k block discussion and I = do not know > > how to check whether I'm affected to that or not (or even causing the p= roblems) and > > how to check whether DEDUPLICATION is definitely OFF (apart from the us= ual stuff list > > features via "zfs get all"). > >=20 > > As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader= from source to > > memory disk and the HDD makes sounds like hell and close to loosing the= r/w heads. On > > other boxes this task is done in a blink of an eye ... > >=20 > > Thanks for your patience, > >=20 > > Regards, > > oh > > =20 >=20 > Turning deduplication off, only stops new blocks from being > deduplicated. Any data written while deduplication was on, are still > deduplicated. You would need to zfs send | zfs recv, or > backup/destroy/restore to get the data back to normal. >=20 > If the drive is making that much noise, have you considered that the > drive might be failing? >=20 Hello. Might there be any hint I can investigate on that ZFS partition showing me = that the particular partition is still doing deduplication? If I wouldn't know that = I switch dedup on and later off, I would blame the OS instead. So, for further foren= sik analysis in the future, it would be nice to know how to look at it - if it is doable= via simple checking the features of the ZFS partition ... Thanks, oh=20 --Sig_/6xEaX9simWG6gXG.eqLpTJs Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX8iVKAAoJEOgBcD7A/5N8ApEIAIKj12AWXm+qQozZ9UTYi8Nq rgTADh6ICcVV4j2QmUBNv2Ry9oUDc0C0Y7HJ0t6Pr/2oESG7I62SxPbLyiqSl1ax EvB20YGDRMn7owRvk7y++rSmp8WwpKbl4aDGCez6Q6K408XZVJVu2jIiIG2db94l zSok0/ixPE7+u0+I9ilLYGZZrhaHD0B4b99NYVnxaBozfrtlggQ3hkwKVGPE6lor AhBgOMiehhFYPSsLnAkpy4ujcr3F7BMjpKsk7+7IcWm0tx2+ihK1D9u9WNCvePuf 9mQqETYn0b/c9dBZT0r99VMcPJ8q7CoUTVe6v/aAENAr8yAs5VO0ybZt7zP7tFU= =qqiZ -----END PGP SIGNATURE----- --Sig_/6xEaX9simWG6gXG.eqLpTJs--