Date: Thu, 15 May 2014 15:10:01 GMT From: "Steven Hartland" <killing@multiplay.co.uk> To: freebsd-fs@FreeBSD.org Subject: Re: kern/189355: zfs panic on 10-stable Message-ID: <201405151510.s4FFA1jd043139@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/189355; it has been noted by GNATS. From: "Steven Hartland" <killing@multiplay.co.uk> To: "Radim Kolar" <hsn@sendmail.cz>, "freebsd-fs@FreeBSD.org" <freebsd-fs@freebsd.org>, <bug-followup@freebsd.org> Cc: Subject: Re: kern/189355: zfs panic on 10-stable Date: Thu, 15 May 2014 16:05:39 +0100 ----- Original Message ----- From: "Radim Kolar" <hsn@sendmail.cz> >> This could be something that has already has a fixed in head but wasn't expected >> to get triggered without TRIM queueing which isn't in 10-stable yet. The fix >> is also likely to change based on feedback from the openzfs guys, hence isn't >> in 10-stable yet. > > only workaround to get 10-STABLE boot without panic is to boot 10.0 and then import/export pool > > > 265046 is already merged in 10-stable. Ah yes I did merge that one just in case. > Now building stable with 265152 and 265321 merged. You shouldn't need 265152 as thats just for queued TRIM's and may just confuse things further. I'm not sure 265321 on its own will make a difference here as thats a fix for stack overflow and as your stack in the trace is only 14 deep shouldn't be your case. Once your done building and if it does still panic can you confirm the code line at the panic location with kgdb as well as the details of the zio being processed under pretty print.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405151510.s4FFA1jd043139>