Date: Wed, 15 Jan 2025 01:40:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283747] kernel panic after telegraf service restart Message-ID: <bug-283747-227-CrdvS7Idvb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283747-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283747-227@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=3D283747 --- Comment #26 from Gleb Smirnoff <glebius@FreeBSD.org> --- Got another advice from Allan to force sync on a ZFS dataset: # zfs set sync=3Dalways $dataset But this all makes sense after we make sure that the process exits. Cause if it does not, then the ktrace system itself may keep tracing in buffers for some time. Also, I would second on Mark's suggestion to try GENERIC-DEBUG kernel from 14.2-RELEASE, or to compile kernel with 'options INVARIANTS' on the existing installation. Cause we are trying to lock a destroyed mutex it could that with INVARIANTS we will crash earlier, and that earlier crash will give more insight on the problem. --=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-283747-227-CrdvS7Idvb>