Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Mar 2019 21:18:57 +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-60Canw6VFF@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 #16 from ncrogers@gmail.com ---
(In reply to Andriy Gapon from comment #15)
Yes, I have added the simpler fix from the private ZoL branch to my custom
kernel and will start deploying that. It applied cleanly to 12.0-RELEASE. I=
 am
torn if it's worthwhile to continue testing with INVARIANTS enabled to see =
if
it still panics, or without and see if it still hangs. I am still not able =
to
replicate either case short of just waiting around for a system to do it - =
no
amount of fs IO or CPU stressing seems to do anything, although I have not
tried dbench like in the ZoL bug report. Fortunately I have access to quite=
 a
few production systems...

I am attaching the patch in case anyone else wants to try it.

I imagine there will need to be a larger effort from someone (mmacy?) to
correctly bring in the fixes to the recent "large_dnode pool feature" from =
ZoL?

--=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-60Canw6VFF>