From owner-freebsd-fs@FreeBSD.ORG  Thu May 15 15:10:02 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9C17D12A
 for <freebsd-fs@smarthost.ysv.freebsd.org>;
 Thu, 15 May 2014 15:10:02 +0000 (UTC)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 89F4121B2
 for <freebsd-fs@smarthost.ysv.freebsd.org>;
 Thu, 15 May 2014 15:10:02 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4FFA2V9043140
 for <freebsd-fs@freefall.freebsd.org>; Thu, 15 May 2014 15:10:02 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4FFA1jd043139;
 Thu, 15 May 2014 15:10:01 GMT (envelope-from gnats)
Date: Thu, 15 May 2014 15:10:01 GMT
Message-Id: <201405151510.s4FFA1jd043139@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
Cc: 
From: "Steven Hartland" <killing@multiplay.co.uk>
Subject: Re: kern/189355: zfs panic on 10-stable
Reply-To: "Steven Hartland" <killing@multiplay.co.uk>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 15:10:02 -0000

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.