Date: Wed, 31 Oct 2012 23:30:07 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: John Nielsen <lists@jnielsen.net> Cc: freebsd-fs@freebsd.org Subject: Re: creating a bootable ZFS image Message-ID: <20121031233007.57aea90b@fabiankeil.de> In-Reply-To: <E89CE323-D4AF-4EF7-855E-2F16E51E71F1@jnielsen.net> References: <E89CE323-D4AF-4EF7-855E-2F16E51E71F1@jnielsen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/sAwor/XY6FvDk/uMqtg8U7/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable John Nielsen <lists@jnielsen.net> 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/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121031233007.57aea90b>