Date: Fri, 26 Oct 2018 17:38:44 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-E6PUFihzXr@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 #29 from Andreas Sommer <andreas.sommer87@googlemail.com> --- (In reply to Andriy Gapon from comment #28) Saw that and tried `procstat -kk` on other processes, but as found previous= ly, it would render the complete system unusable if executed on certain process= es. Didn't find something obvious within the same process (that does `zil_commit_impl` in one thread). The committing process is Buildbot, and I= saw that it happened during a nightly run of periodic scripts (which go through whole filesystem). Now I have to reboot the instance... That's why a non-destructive debugging method might be more helpful to see what other interlock we have between processes/threads. --=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-E6PUFihzXr>