Date: Tue, 8 Aug 2023 10:16:47 -0700 From: Alan Somers <asomers@freebsd.org> To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@freebsd.org> Cc: current@freebsd.org Subject: Re: ZFS deadlock in 14 Message-ID: <CAOtMX2jx7HXSKnXuKCTaXceeA0vPaoCFi%2B7%2BM2_DrdhjFj%2BXpg@mail.gmail.com> In-Reply-To: <86leeltqcb.fsf@ltc.des.no> References: <86leeltqcb.fsf@ltc.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 8, 2023 at 10:08=E2=80=AFAM Dag-Erling Sm=C3=B8rgrav <des@freeb= sd.org> wrote: > > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4 > August) and is 100% reproducable just by starting poudriere bulk in a > 16-core VM and waiting a few hours until deadlkres kicks in. In the > latest instance, deadlkres complained about a bash process: Do you have ZFS block cloning enabled on your pool? There were a lot of bugs associated with that feature. I think that was merged on 3-April. > zpool get feature@block_cloning zroot NAME PROPERTY VALUE SOURCE zroot feature@block_cloning disabled local
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jx7HXSKnXuKCTaXceeA0vPaoCFi%2B7%2BM2_DrdhjFj%2BXpg>