Date: Fri, 6 Jan 2017 09:03:37 -0800 From: Freddie Cash <fjwcash@gmail.com> To: Xin LI <delphij@gmail.com> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: Check status of background destroy Message-ID: <CAOjFWZ7ii9Pes2x8yKytdgnde1dNv5OQ6EM2rWATYL1KwC=Ujg@mail.gmail.com> In-Reply-To: <CAGMYy3uU6bUfjufXFQXbNT2krnRnOj-YC2069ep_2tNjDJuw4A@mail.gmail.com> References: <CAOjFWZ4S42mebL15iT8=TLcfvabBWeUdLDzi_d3WfhKTpuGdOw@mail.gmail.com> <CAGMYy3uU6bUfjufXFQXbNT2krnRnOj-YC2069ep_2tNjDJuw4A@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
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. > This is looking promising. Booting off an 11.0-based mfsBSD didn't work (locked up after "Trying to mount root from /dev/md0"). Booting off a 10.3-based mfsBSD worked. Set that sysctl, then imported the pool without issues. The box has now been running for just over 24 hours. ARC is sitting at 93 GB, with Wired at 116 GB. Previously, the ARC would only be around 10 GB with Wired over 120 GB. "zpool iostat" shows lots of reads and writes happening to the pool. And the Avail space is slowly ticking upwards. Now just need to wait and see how long it takes to free up all 40 TB of referenced space. :) Thanks for the info! -- Freddie Cash fjwcash@gmail.comhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ7ii9Pes2x8yKytdgnde1dNv5OQ6EM2rWATYL1KwC=Ujg>