Date: Thu, 14 Mar 2019 20:26:21 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 236480] [zfs] [panic] solaris assert: dn->dn_type != DMU_OT_NONE Message-ID: <bug-236480-3630-GSCYZkkaft@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236480-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-236480-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=3D236480 --- Comment #5 from ncrogers@gmail.com --- (In reply to Julien Cigar from comment #4) Glad to hear I'm not the only one... I think this bug is a duplicate of #23= 6220 but I was asked to create a separate issue because of the kernel panic. I t= hink you are suffering from the "deadlock" / hang issue that I am experiencing. = The reason, I believe, that I get an actual panic is because I am trying a cust= om kernel with INVARIANTS enabled. If you don't have INVARIANTS it eventually = the filesystem deadlock. FWIW I am not using nullfs, but I AM using postgresql 11.1. It might be useful if you could report a `procstat -kka` output when this happens. --=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-236480-3630-GSCYZkkaft>