From owner-freebsd-amd64@freebsd.org  Wed Feb 24 18:41:18 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA0DBAB3616
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 24 Feb 2016 18:41:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 DA5841762
 for <freebsd-amd64@FreeBSD.org>; Wed, 24 Feb 2016 18:41:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1OIfIql015339
 for <freebsd-amd64@FreeBSD.org>; Wed, 24 Feb 2016 18:41:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207464] Panic when destroying ZFS snapshot on boot filesystem
Date: Wed, 24 Feb 2016 18:41:19 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: dustinwenz@ebureau.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207464-6-TkxDDmWXqM@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207464-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207464-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Feb 2016 19:48:34 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 18:41:19 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207464

--- Comment #1 from dustinwenz@ebureau.com ---
This is almost a stock kernel, with vimage enabled and the ARC patch applied
from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187594

I see that the checkin yesterday for vfs_subr.c reverted it to back to a
version from December due to an unexplained ZFS bug. It's possible this is
related, but I've not been able to reproduce it yet on r295115.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=