From owner-freebsd-questions@freebsd.org Tue Jan 2 20:34:28 2018 Return-Path: Delivered-To: freebsd-questions@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 468F6EB80C8 for ; Tue, 2 Jan 2018 20:34:28 +0000 (UTC) (envelope-from prvs=15339981c8=vogelke@pobox.com) Received: from WPAFB-MAIL6.AFNOC.Af.MIL (wpafb-mail6.afnoc.af.mil [131.27.1.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "WPAFB-Mail6.afnoc.af.mil", Issuer "DOD ID SW CA-38" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CC58071F8E for ; Tue, 2 Jan 2018 20:34:26 +0000 (UTC) (envelope-from prvs=15339981c8=vogelke@pobox.com) Received: from us.af.mil (unknown [131.9.254.142]) by WPAFB-MAIL6.AFNOC.Af.MIL with smtp (TLS: TLSv1/SSLv3,256bits,DHE-RSA-AES256-SHA) id 0832_0a13_c0d27ea1_2d42_47a1_bac8_f379b623441a; Tue, 02 Jan 2018 20:34:12 +0000 Received: from ([131.9.40.227]) by 52vejx-mr-008.us.af.mil with SMTP id 20Z0FN1.326334541; Tue, 02 Jan 2018 14:34:05 -0600 Received: (qmail 17947 invoked by uid 100); 2 Jan 2018 20:34:05 -0000 From: "Karl Vogel" Date: Tue, 2 Jan 2018 15:34:05 -0500 To: freebsd-questions@freebsd.org Subject: Re: zpool fragmentation Message-ID: <20180102203405.GA17447@bsd118.wpafb.af.mil> Reply-To: vogelke@pobox.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2018 20:34:28 -0000 On Tue, Jan 02, 2018 at 01:52:54PM -0600, Adam Vande More wrote: > On Tue, Jan 2, 2018 at 12:40 PM, pete wright wrote: > >> are there any coping mechanisms people use to reduce fragmentation? > > Keep lots of free space. If you create an unmounted empty filesystem with a reservation to prevent the zpool from filling up, it gives you behavior similar to ufs's reserved blocks. I reserve 5-10% to make sure the system doesn't become completely unusable: root# zfs create -o reservation=50G -o mountpoint=none rpool/reservation -- Karl Vogel I don't speak for the USAF or my company Sheep learn to recognise celebrity faces from different angles --"New Scientist", 8 Nov 2017