Date: Tue, 4 Mar 2014 14:44:57 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Peter Grehan <grehan@freebsd.org> Cc: "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, Xin Li <delphij@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Problem with ZFS userboot changes r262331 and VM with mixed partitions Message-ID: <CAG=rPVdK2f6XfLwX7SXqNpKhj3ZRW67T1900fXy5jZyB43H6LQ@mail.gmail.com> In-Reply-To: <531652AE.9070506@freebsd.org> References: <CAG=rPVd5OQ1Gw6q-e94Ffnk_zPxkFvjaR5bpOOjMg7j-9AvSdw@mail.gmail.com> <531652AE.9070506@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 4, 2014 at 2:24 PM, Peter Grehan <grehan@freebsd.org> wrote: > Hi Craig, > > >> ZFS: i/o error - all block copies unavailable >> >> I don't fully understand all this logic. Is there a bug that can be fixed >> here? > > > Yes - a flag needs to be passed to userboot to tell it to ignore ZFS > filesystems. This is analogous to the decision to use boot2 (implicit UFS) > vs zfsboot (explicit ZFS) as the 2nd-stage loader on a real disk. > > It didn't look possible to do this without changing the userboot ABI, but, > it's probably time to bump that. Thanks for the explanation. Can this flag be passed via bhyveload, and if so, how? Right now the workaround was to recompile userboot with: cd /usr/src/sys/boot/userboot make clean make WITHOUT_ZFS=yes make WITHOUT_ZFS=yes install -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVdK2f6XfLwX7SXqNpKhj3ZRW67T1900fXy5jZyB43H6LQ>