Date: Sun, 11 Nov 2018 15:20:33 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-jiTdCiMq0t@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229614-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-229614-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #40 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Allan Jude from comment #38) Andreas managed to reproduce the issue with the patch (like predicted by avg and you), but it took days of hammering the system heavily. @Allan/avg: Do you have an overview of all the possible code paths in which this interlock can happen? I didn't look closely at the code myself yet. If it's just about reclaiming a vnode, we could just allow that to fail and either retry the operation or allow exceeding kern.maxvnodes temporarily (l= ike in a kind of soft-fail scenario). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229614-3630-jiTdCiMq0t>