Date: Wed, 9 Nov 2022 11:51:31 -0800 From: Mark Millard <marklmi@yahoo.com> To: "Patrick M. Hausen" <pmh@hausen.com> Cc: Warner Losh <imp@bsdimp.com>, Alexander Leidinger <Alexander@leidinger.net>, tsoome@freebsd.org, Li-Wen Hsu <lwhsu@freebsd.org>, current@freebsd.org Subject: Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script) Message-ID: <66C46BAC-9411-4655-A3A2-C70756123F81@yahoo.com> In-Reply-To: <460205F9-5D59-4033-813B-C34E01BFD6C4@hausen.com> References: <202211070339.2A73dJlO027991@gitrepo.freebsd.org> <20221107121514.Horde.nulS9Wg1s3yzAsXXkuJRBa9@webmail.leidinger.net> <CANCZdfrdc%2BDbv6sDyDLcWNpXnWScEmpUsGu3q8%2BMbZRjDS8eig@mail.gmail.com> <20221108105053.Horde.eqgFiBJe2ngGAj6BkXcv5-Z@webmail.leidinger.net> <20221109134610.Horde.JB7ibQTWprHbmIUfhg7JY7f@webmail.leidinger.net> <CANCZdfptmipq%2BsS0AQ1%2B7EmLT-7YdKv8s%2BnCV7ON1Qy6-C6N9A@mail.gmail.com> <460205F9-5D59-4033-813B-C34E01BFD6C4@hausen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 9, 2022, at 11:02, Patrick M. Hausen <pmh@hausen.com> wrote:
>=20
>> Am 09.11.2022 um 16:54 schrieb Warner Losh <imp@bsdimp.com>:
>>>> There is a fixed list of features we support in the boot loader:
>>>> [...]=20
>>>> Any feature not on this list will cause the boot loader to =20
>>>> reject the pool.
>=20
> I admit that I do not grasp the full implications of this thread and =
the proposed
> and debated changes. Does that imply that a simple "zpool upgrade" of =
the
> boot/root pool might lead to an unbootable system in the future - even =
if the
> boot loader is upgraded as it should, too?
Not as you word it ("as it should"). But . . .
Using an actual example, if I understand/remember right:
When com.delphix:head_errlog was added to main [so: 14],
it was not added yet to the loader as of that commit.
As I understand some folks did pool upgrades before a
loader update for the issue was commited. These people
had the loader refuse the upgraded pools until the
loader was update was available and they got it installed.
There is likely a timing gottcha in that openzfs updates
probably have to be committed before the loader can be
updated to track. Landing in the middle without noticing
and upgrading both the loader and the pool(s) could lead
to such problems: not yet the right loader version to
upgrade to.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66C46BAC-9411-4655-A3A2-C70756123F81>