From owner-freebsd-fs@freebsd.org  Wed Apr  6 17:10:11 2016
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 7B5BFB06A0F
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed,  6 Apr 2016 17:10:11 +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 6C3AC1F44
 for <freebsd-fs@FreeBSD.org>; Wed,  6 Apr 2016 17:10:11 +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 u36HAAHg059509
 for <freebsd-fs@FreeBSD.org>; Wed, 6 Apr 2016 17:10:11 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: Wed, 06 Apr 2016 17:10:10 +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: avg@FreeBSD.org
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: 
Message-ID: <bug-207667-3630-v4peXC8WnS@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.21
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: Wed, 06 Apr 2016 17:10:11 -0000

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

--- Comment #9 from Andriy Gapon <avg@FreeBSD.org> ---
(In reply to Michelle Sullivan)

Replying to multiple comments at once.

Yes, taking a picture of a monitor is a fine last measure.  A serial consol=
e,
real or emulated via, e.g., IPMI or AMT, is better, of course.

The panic looks like a result of a well-known (among developers) and very h=
ard
to fix problem with interaction between GEOM and ZVOLs that arises from usi=
ng
ZFS pools on top of ZFS volumes.  I can not offer you any fix although I ha=
ve
got some work-in-progress on this issue.

I can suggest a work-around: create a FreeBSD VM using the volumes comprisi=
ng
the pool as the VM's disks and run the scrub within the VM.

Besides zpool scrub commands like zpool reopen, zpool split, zpool online [=
-e]
can also trigger the same bug for pools on top of ZFS volumes.

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