Date: Wed, 19 Sep 2018 22:36:41 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-sqiDg2RZEK@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 #15 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Mike from comment #14) As long as you're not memory constrained raising kern.maxvnodes shouldn't c= ause any issues. If anything, it could even increase disk i/o performance (we up= ped small vms that would by default have 200k to 1000000 kern.maxvnodes without= any issues). It would be interesting if you could share if the adjustments improved your situation as well as the kind of workloads that cause interlocks in your se= tup right now to help create a test case that reproduces the problem reliably. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229614-3630-sqiDg2RZEK>