Date: Thu, 11 Oct 2018 19:30:10 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-n2T863cScZ@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=229614 --- Comment #26 from Andreas Sommer <andreas.sommer87@googlemail.com> --- I recommend everyone having the described problem and similar `procstat -kk` stacktrace to patch their kernel manually for now. For our development CI host, I did just that (built and replaced kernel only) and it works stably for some days now *without* the `kern.maxvnodes=HIGHNUMBER` workaround. The same applies to my reproduction setup (see GitHub link, posted above) – previously it took a few seconds to reproduce the issue, and after replacing the kernel, no more problems. However, if you have 24/7 services that need to keep running, probably use the workaround for now and wait for a dot release which will then anyhow require a reboot. 2 months actually sounds long enough to give the safety of many people trying and confirming the change. It will also immediately make it from head to stable/12 according to https://www.freebsd.org/releases/12.0R/schedule.html, so I'm happy. -- 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-n2T863cScZ>