Date: Fri, 6 Oct 2017 14:02:03 +1100 From: Richard Perini <rpp@ci.com.au> To: FreeBSD Filesystems <freebsd-fs@freebsd.org> Cc: javocado <javocado@gmail.com> Subject: Re: lockup during zfs destroy Message-ID: <20171006030203.GA30590@jodi.ci.com.au> In-Reply-To: <CAOjFWZ6u3VjihNDT1SQYaB1P9P2u4OR1Kj1R0t0Zqvv-JDfA0g@mail.gmail.com> References: <CAP1HOmQtU14X1EvwYMHQmOru9S4uyXep=n0pU4PL5z-%2BQnX02A@mail.gmail.com> <CAOjFWZ54hB_jRaSQ8NX=s214Km9o%2BN=qvnQehJykZbY_QJGESA@mail.gmail.com> <CAOjFWZ7ohEkTvK-jRUOjFmTaaOOViJUrtQWKR8oJyo-CV=%2Bk6Q@mail.gmail.com> <CAP1HOmRqbAqstzKMtJxP_g4DJxXXC%2B_WRF-Wnf1VbYE1FhROcw@mail.gmail.com> <CAOjFWZ6u3VjihNDT1SQYaB1P9P2u4OR1Kj1R0t0Zqvv-JDfA0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 04, 2017 at 10:28:27PM -0700, Freddie Cash wrote: > On Oct 4, 2017 10:13 PM, "javocado" <javocado@gmail.com> wrote: > > Setting vfs.zfs.free_max_blocks to 20k has not helped unfortunately. > > > No, that won't help with this issue as the destroy operation is already in > progress and part of a transaction group. But it will mitigate or > (hopefully) prevent this issue in the future. A bit of a long shot as there's no mention of the FreeBSD version involoved, but we had somewhat similar symptoms caused by bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222288 Cheers, -- Richard Perini Ramico Australia Pty Ltd Sydney, Australia rpp@ci.com.au +61 2 9552 5500 ----------------------------------------------------------------------------- "The difference between theory and practice is that in theory there is no difference, but in practice there is"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171006030203.GA30590>