From owner-freebsd-fs@freebsd.org  Wed Jan  4 18:51:45 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 67416C9E837
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed,  4 Jan 2017 18:51:45 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (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 337601282
 for <freebsd-fs@freebsd.org>; Wed,  4 Jan 2017 18:51:45 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.88 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1cOqf0-0006VD-JQ; Wed, 04 Jan 2017 18:51:42 +0000
Date: Wed, 4 Jan 2017 18:51:42 +0000
From: Gary Palmer <gpalmer@freebsd.org>
To: Freddie Cash <fjwcash@gmail.com>
Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>
Subject: Re: Check status of background destroy
Message-ID: <20170104185142.GB95857@in-addr.com>
References: <CAOjFWZ4S42mebL15iT8=TLcfvabBWeUdLDzi_d3WfhKTpuGdOw@mail.gmail.com>
 <CAGMYy3uU6bUfjufXFQXbNT2krnRnOj-YC2069ep_2tNjDJuw4A@mail.gmail.com>
 <CAOjFWZ55AOeURtzeOZX_oR+J=exm-9pUnHi9+SFcVVNkxm2n3A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOjFWZ55AOeURtzeOZX_oR+J=exm-9pUnHi9+SFcVVNkxm2n3A@mail.gmail.com>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2017 18:51:45 -0000

On Wed, Jan 04, 2017 at 10:48:28AM -0800, Freddie Cash wrote:
> On Wed, Jan 4, 2017 at 10:43 AM, Xin LI <delphij@gmail.com> wrote:
> 
> > Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary
> > number, can be larger, limits maximum blocks being freed per txg; see
> > https://svnweb.freebsd.org/base?view=revision&revision=271532 for
> > details).
> >
> > You can inspect the progress with DTrace by looking at zfs-dbgmsg.
> >
> 
> ???Forgot to mention, this server is running 64-bit FreeBSD 9.3-p5.???  That
> sysctl OID doesn't exist.
> 
> ???From the sounds of the comments on that revision, this would probable be a
> useful feature to have.
> 
> I'll have to see about upgrading this system (there's a separate pool for
> the OS), I guess.
> 
> Which FreeBSD version(s) include that feature?  Would 10.3 be okay, or
> would I have to go all the way to 11.0?

The sysctl is in 10.3

$ uname -r
10.3-RELEASE-p15
$ sysctl -d vfs.zfs.free_max_blocks
vfs.zfs.free_max_blocks: Maximum number of blocks to free in one TXG
$ sysctl vfs.zfs.free_max_blocks
vfs.zfs.free_max_blocks: 18446744073709551615
$ 

Regards,

Gary