Date: Sun, 19 Sep 2010 18:41:29 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Dan Mack <mack@macktronics.com> Cc: jhell <jhell@DataIX.net>, stable@freebsd.org, Martin Matuska <mm@freebsd.org> Subject: Re: MFC of ZFSv15 Message-ID: <4C964B49.6080102@infracaninophile.co.uk> In-Reply-To: <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com> References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <201009161543.o8GFhJnh029157@lava.sentex.ca> <4C923ECD.8020809@FreeBSD.org> <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigAF501D63D208275920E42A13
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 19/09/2010 17:36:01, Dan Mack wrote:
> But I should be able to boot my ZFSv14 root pool using the ZFSv15
> build of FreeBSD, correct? But the problem scenario would be when
> I've upgraded my root pool to v15 and I attempt to boot it with v14
> boot loader. At least that is what I think ...
Yes. The bootloader is not prescient, so bootloader compiled against
v14 can't cope with a zpool using v15. It's only the on-disk format
that counts in this: zfs software will operate perfectly well with older
on-disk data formats.
> I guess what I'm getting at is ... you should be able to buildworld,
> installkernel, reboot, installworld, reboot without worry. But
> after your run 'zpool upgrade', you will need to re-write the
> bootcode using gpart on each of your root pool ZFS disks.
If you want to be completely paranoid, you could update the bootcode on
your boot drive (or one out of a mirror pair, if that's what you're
using) at the point of running installkernel and way before you run
'zpool upgrade'. In theory, should this go horribly wrong and you end
up with an unbootable system, you can recover by booting the 8.0 install
media into FIXIT mode and reinstalling the bootblocks from there (or
booting from the other disk in your mirror set). Once you've got a
system you know will reboot with the new bootblocks, then go ahead and
with installworld and updating the zpool version.
> Am I understanding this correctly ?
Yep. That's quite right. Running 'zpool upgrade -a' is one of those
operations you can't easily reverse, so designing an upgrade plan where
you can stop and back-out at any point is quite tricky. Fortunately,
the risk of things going wrong at the point of running zpool upgrade is
really very small, so for most purposes, just ploughing ahead and
accepting the really very small risk is going to be acceptable.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enigAF501D63D208275920E42A13
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyWS08ACgkQ8Mjk52CukIxuSACglXbPehlYot8K6XWTNd2NeLM1
sj8Anj5UlHd336UG7h+JW+anCNjUknPV
=HtK/
-----END PGP SIGNATURE-----
--------------enigAF501D63D208275920E42A13--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C964B49.6080102>