From owner-freebsd-fs@FreeBSD.ORG Fri Feb 14 18:53:05 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C1F3C6E for ; Fri, 14 Feb 2014 18:53:05 +0000 (UTC) Received: from internet06.ebureau.com (internet06.ebureau.com [65.127.24.25]) by mx1.freebsd.org (Postfix) with ESMTP id 14ADF1A13 for ; Fri, 14 Feb 2014 18:53:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by internet06.ebureau.com (Postfix) with ESMTP id 88578A81900 for ; Fri, 14 Feb 2014 12:52:58 -0600 (CST) X-Virus-Scanned: amavisd-new at ebureau.com Received: from internet06.ebureau.com ([127.0.0.1]) by localhost (internet06.ebureau.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ujf62jCyJ-7f for ; Fri, 14 Feb 2014 12:52:58 -0600 (CST) Received: from nail.office.ebureau.com (nail.office.ebureau.com [10.10.20.23]) by internet06.ebureau.com (Postfix) with ESMTPSA id 44BECA818F5 for ; Fri, 14 Feb 2014 12:52:58 -0600 (CST) From: Joe Moog Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Unable to clear a stuck device Message-Id: <537EE1DF-CDA1-4A08-A963-D312E104725E@ebureau.com> Date: Fri, 14 Feb 2014 12:52:58 -0600 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 18:53:05 -0000 We have a FreeBSD host (FreeBSD 9.1-PRERELEASE #0 r244125) configured = with a few ZFS storage volumes. Recently we attached an external volume = to the host, created a GELI-encrypted ZFS volume, and copied some data = to it. When completed, the device was not disconnected properly. Now, = any ZFS/zpool commands that attempt to touch that missing device are = left hanging in perpetuity on the host because it seems to think it can = still access the volume when in fact it cannot. This is not affecting = any other functions of the host besides a few scripts that are intended = to check the health of the attached volumes. Is there any way to clear the apparent presence of this missing device? = We tried to re-attach the volume and perform the necessary ZFS = export/import, but these commands now hang as well (the -f option has no = effect). No doubt a reboot would take care of it, but there are some = functions running on this host that we do not wish to interrupt, if at = all possible. Can anybody make a recommendation? Thanks Joe