Date: Fri, 15 Jan 2016 15:20:17 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 205708] Kernel panic possibly happening while adding/removing/listing ZFS snapshot Message-ID: <bug-205708-3630-ddEtbceubI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205708-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-205708-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=3D205708 karl@denninger.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@denninger.net --- Comment #6 from karl@denninger.net --- Are you running the patch from here? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187594 If not are you willing to try the latest version of that patch (from 2015-12-10)? I have had a somewhat-related crash going on for quite a while, and while i= t is difficult to reproduce I've had it happen both with earlier versions of the above patch and on a "clean" system. HOWEVER, the last version has now been running since early December -- with no panics. My blowups were all related to snapshot manipulation during backup operatio= ns, so this may be related. If so then the root is likely the result of a modu= lo extension that returns an unexpected delay product and causes trouble elsew= here in the code. The latest version of that patch prevents the extension from occurring. I can pull out just that couple of lines of code that appear to have been effective in stopping the blowups if you'd like to try something simpler and leave the rest of the ZFS code alone. --=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-205708-3630-ddEtbceubI>