From owner-freebsd-fs@FreeBSD.ORG Wed Oct 31 22:42:59 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CBFDC0E for ; Wed, 31 Oct 2012 22:42:59 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.42]) by mx1.freebsd.org (Postfix) with ESMTP id B37A58FC0C for ; Wed, 31 Oct 2012 22:42:58 +0000 (UTC) Received: from [84.44.210.71] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TTgnp-0004r8-Rk; Wed, 31 Oct 2012 23:30:25 +0100 Date: Wed, 31 Oct 2012 23:30:07 +0100 From: Fabian Keil To: John Nielsen Subject: Re: creating a bootable ZFS image Message-ID: <20121031233007.57aea90b@fabiankeil.de> In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/sAwor/XY6FvDk/uMqtg8U7/"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd-fs@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 22:42:59 -0000 --Sig_/sAwor/XY6FvDk/uMqtg8U7/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable John Nielsen wrote: > What I am doing instead is creating the pool with -o failmode=3Dcontinue, > installing, unmounting everything, then forcibly detaching the md > device. This gives me an image I can use, and it boots and runs fine. > Unfortunately, that leaves me with a defunct pool on the build host > until I reboot it. Anything I try to do to the pool (destroy, offline, > export, etc) returns "cannot open 'zfsroot': pool I/O is currently > suspended." (With the default failmode=3Dwait, it's even worse since any > command that tries to touch the pool never returns.) The pool state is > "UNAVAIL" and the device state is "REMOVED". Once the build host is > rebooted the device state changes to UNAVAIL and zpool destroy works as > expected. Did you try "zpool clear [-F] $pool" after reattaching the md? It often works for me in situations where other zpool subcommands just hang like you described above. Fabian --Sig_/sAwor/XY6FvDk/uMqtg8U7/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCRpnIACgkQBYqIVf93VJ0Z8ACeNRrRwKrUV1906XQkstMdBg+K eGAAoISYGfWBqiRiswUrCYqWm0ak7V4b =bBpP -----END PGP SIGNATURE----- --Sig_/sAwor/XY6FvDk/uMqtg8U7/--