From owner-freebsd-amd64@freebsd.org  Wed Apr 20 14:57:49 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 8300CB15ACB
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 20 Apr 2016 14:57:49 +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 73F881FA6
 for <freebsd-amd64@FreeBSD.org>; Wed, 20 Apr 2016 14:57:49 +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 u3KEvmM7034116
 for <freebsd-amd64@FreeBSD.org>; Wed, 20 Apr 2016 14:57:49 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, 20 Apr 2016 14:57:49 +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 Many People
X-Bugzilla-Who: karl@denninger.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-207464-6-qhb0LziKGw@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, 20 Apr 2016 15:43:26 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.21
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, 20 Apr 2016 14:57:49 -0000

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

karl@denninger.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |karl@denninger.net

--- Comment #7 from karl@denninger.net ---
This looks like the same problem I've seen related to an automated backup f=
or
quite some time; the symptomology, if you catch it before it blows up, is t=
hat
the snapshot you're trying to delete cannot be CD'd into, but it's there.

If you reboot before trying to destroy it the panic does not happen, but if
not, kaboom.

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