From owner-freebsd-amd64@freebsd.org  Thu Feb 25 18:45:24 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 AF40CAB445F
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Thu, 25 Feb 2016 18:45:24 +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 9E866121C
 for <freebsd-amd64@FreeBSD.org>; Thu, 25 Feb 2016 18:45:24 +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 u1PIjOZT060827
 for <freebsd-amd64@FreeBSD.org>; Thu, 25 Feb 2016 18:45:24 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: Thu, 25 Feb 2016 18:45:24 +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: 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: bug_severity
Message-ID: <bug-207464-6-0oPNynjJBL@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: Thu, 25 Feb 2016 20:10:08 +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: Thu, 25 Feb 2016 18:45:24 -0000

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

dustinwenz@ebureau.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Only Me             |Affects Many People

--- Comment #2 from dustinwenz@ebureau.com ---
Turns out this is quite easy to reproduce. In the following example, the sy=
stem
is booted from a filesystem called "zroot". Running the following three she=
ll
commands twice in succession consistently causes a panic, even on
10.3-PRERELEASE r295115M:

zfs snapshot zroot@panic
ls -d /.zfs/snapshot/panic
zfs destroy zroot@panic


The "ls -d" operation on the .zfs snapshot is required to cause the panic. =
It
also seems important to do this on a freshly booted system; if many success=
ful
snapshot/destroy operations are done, the machine stops being susceptible to
the panic.

The issue is not particularly timing-sensitive. I can still reproduce even =
when
waiting 5 seconds between operations.

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