Date: Tue, 15 Aug 2023 18:04:42 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: current@freebsd.org Subject: Re: ZFS deadlock in 14 Message-ID: <86350kqokl.fsf@ltc.des.no> In-Reply-To: <86a5utrafp.fsf@ltc.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?= =?utf-8?Q?rav=22's?= message of "Mon, 14 Aug 2023 16:00:10 %2B0200") References: <86leeltqcb.fsf@ltc.des.no> <86h6p4s64h.fsf@ltc.des.no> <86a5utrafp.fsf@ltc.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Sm=C3=B8rgrav <des@FreeBSD.org> writes: > I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor > 5ca7f02946 appears to be working. I'm going to try to come up with a > more efficient way to reproduce the deadlock than running poudriere. I wrote a script that creates multiple filesystems, snapshots them, populates them and rolls them back continuously but so far I have not succeeded in triggering the deadlock without poudriere. I guess my script doesn't consume enough vnodes. Also, 9228ac3a69c4 (9 August, last commit before the contrib/googletest breakage) still deadlocks. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86350kqokl.fsf>