Date: Wed, 4 Oct 2017 22:28:27 -0700 From: Freddie Cash <fjwcash@gmail.com> To: javocado <javocado@gmail.com> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: lockup during zfs destroy Message-ID: <CAOjFWZ6u3VjihNDT1SQYaB1P9P2u4OR1Kj1R0t0Zqvv-JDfA0g@mail.gmail.com> In-Reply-To: <CAP1HOmRqbAqstzKMtJxP_g4DJxXXC%2B_WRF-Wnf1VbYE1FhROcw@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Cheers, Freddie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ6u3VjihNDT1SQYaB1P9P2u4OR1Kj1R0t0Zqvv-JDfA0g>