Date: Fri, 15 Mar 2019 06:53:39 +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-Ajr9rm2HIy@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=236480 --- Comment #15 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to ncrogers from comment #14) So far I cannot establish a firm link between those two problems. On the other hand, instantiating a vnode/znode pair for a deleted file can lead to all kinds of unintended consequences down the road. Could you please try to apply a patch based on the first ZoL link? And then keep testing to see if both problems go away or if the first problem comes back? (Or some other less fortunate outcome.) -- 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-Ajr9rm2HIy>