From owner-freebsd-fs@freebsd.org  Tue Mar 14 19:17:16 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 67210D0C15D
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 14 Mar 2017 19:17:16 +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 56741162F
 for <freebsd-fs@FreeBSD.org>; Tue, 14 Mar 2017 19:17:16 +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 v2EJHGnD037887
 for <freebsd-fs@FreeBSD.org>; Tue, 14 Mar 2017 19:17:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol
 pool...
Date: Tue, 14 Mar 2017 19:17:16 +0000
X-Bugzilla-Reason: AssignedTo CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: michelle@sorbs.net
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Unable to Reproduce
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207667-3630-z7XlCJWN1K@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207667-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-207667-3630@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-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2017 19:17:16 -0000

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

--- Comment #13 from Michelle Sullivan <michelle@sorbs.net> ---
It does, not going to bother with this anymore though now.  Got better thin=
gs
to do with my life than chase down bugs a year after notification on an OS =
that
I am migrating away from because of these very 'obsolete version' closure of
bugs.  I will however tell you it's how its setup that causes the issue, do=
n't
remember how I did it because I'm unable to get it setup in the same way ag=
ain.

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