Date: Sat, 19 Nov 2011 21:19:21 +0100 From: Florian Wagner <florian@wagner-flo.net> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org Subject: Re: Extending zfsboot.c to allow selecting filesystem from boot.config Message-ID: <20111119211921.7ffa9953@naclador.mos32.de> In-Reply-To: <4EB98E05.4070900@FreeBSD.org> References: <20111015214347.09f68e4e@naclador.mos32.de> <4E9ACA9F.5090308@FreeBSD.org> <20111019082139.1661868e@auedv3.syscomp.de> <4E9EEF45.9020404@FreeBSD.org> <20111019182130.27446750@naclador.mos32.de> <4EB98E05.4070900@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/WIArBJPXjyaA459VtaNDFsT Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable > on 19/10/2011 19:21 Florian Wagner said the following: > >> [...] > >>=20 > >>> The only thing I was a bit confused by is that on the boot prompt > >>> only the pool and filename to be booted are printed. > >>=20 > >> Do you mean the (gpt)zfsboot prompt? > >=20 > > Yes. For a boot.config with "rpool:root/something:" it prints: > >=20 > > Booting from Hard Disk... /boot.config: rpool FreeBSD/x86 boot > > Default: rpool:/boot/zfsloader boot: <CURSOR> >=20 >=20 > Thank you very much for your testing and reports! > Please see these additional changes: > http://people.freebsd.org/~avg/zfsboot.fixes.diff Thanks for the additional patch. It seems to be exactly what I'm looking for. Sadly your patches (tested with and without the latest one) seem to break booting on RAID-Z2 arrays. The prior test, for which I've reported success were using a VM with only a single disk. Today I tried the patched bootloader on my fileserver with a 6 disk RAID-Z2 array. That didn't go so well: Installing the modified gptzfsboot results in a blinking screen with turquoise-striped ASCII background and assorted characters in the foreground. Installing the modified zfsloader (but unmodified gptzfsboot) makes it unable to find its root dataset: BTX loader 1.00 BTX version is 1.02 [...] BIOS drive C: is disk0 BIOS drive D: is disk1 [...] FreeBSD/x86 ZFS enabled bootstrap loader, Revision 1.0 [...] ZFS: can't find dataset [LONG NUMBER] ZFS: can't map root filesystem to its name can't load 'kernel' Type '?' [...] OK lsdev cd devices: disk devices: disk0: BIOS drive C: disk0p1: FreeBSD boot disk0p2: FreeBSD ZFS disk0p3: FreeBSD ZFS disk1: BIOS drive D: disk1p1: FreeBSD boot disk1p2: FreeBSD ZFS disk1p3: FreeBSD ZFS pxe devices: zfs devices: zfs:root OK The output is from my test VM, where I've reproduced the problem. Setup is: - RAID-Z2 over the four partitions disk{0,1}p{2,3}. - Pool is simply called root. - root has bootfs property set to root/stable-8-r226381. - There is no boot.config on that dataset. A zfsloader built without your patches boots the system. Any more information I can provide? Regards Florian --Sig_/WIArBJPXjyaA459VtaNDFsT Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk7ID0oACgkQLvW/2gp2pPzlywCeM4SnOtb0WczOo2kKQ3Kws4h7 mdoAoJtVBcgw5AE2GYcundP7CmJVvhic =Eguv -----END PGP SIGNATURE----- --Sig_/WIArBJPXjyaA459VtaNDFsT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111119211921.7ffa9953>