Date: Wed, 9 Nov 2022 13:51:29 -0700 From: Warner Losh <imp@bsdimp.com> To: "Patrick M. Hausen" <pmh@hausen.com> Cc: Alexander Leidinger <Alexander@leidinger.net>, Mark Millard <marklmi@yahoo.com>, 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: <CANCZdfoeDvxSqqEjpnfK=FCY0K1aYEqTw80SKLAZ-5d2qrW5EA@mail.gmail.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
--000000000000d165cb05ed0fd283 Content-Type: text/plain; charset="UTF-8" On Wed, Nov 9, 2022 at 12:02 PM Patrick M. Hausen <pmh@hausen.com> wrote: > Hi all, > > > 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: > > >> [...] > > >> Any feature not on this list will cause the boot loader to > > >> reject the pool. > > 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? > Yes. For safety, boot loader upgrade is mandatory when you do a zpool upgrade of the root filesystem. It was definitely needed in the OpenZFS jump, and we've had one or two other flag days since. It would be nice if we had a failsafe here, but we don't today. With a failsafe, we could say 'well, go ahead and try, even if it encounters something it doesn't understand... to at least allow the system to boot. Warner --000000000000d165cb05ed0fd283 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 9, 2022 at 12:02 PM Patri= ck M. Hausen <<a href=3D"mailto:pmh@hausen.com">pmh@hausen.com</a>> w= rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p= x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br= > <br> > Am 09.11.2022 um 16:54 schrieb Warner Losh <<a href=3D"mailto:imp@b= sdimp.com" target=3D"_blank">imp@bsdimp.com</a>>:<br> > >>=C2=A0 =C2=A0 There is a fixed list of features we support in = the boot loader:<br> > >>=C2=A0 =C2=A0 [...] <br> > >>=C2=A0 =C2=A0 Any feature not on this list will cause the boot= loader to=C2=A0 <br> > >> reject the pool.<br> <br> I admit that I do not grasp the full implications of this thread and the pr= oposed<br> and debated changes. Does that imply that a simple "zpool upgrade"= ; of the<br> boot/root pool might lead to an unbootable system in the future - even if t= he<br> boot loader is upgraded as it should, too?<br></blockquote><div><br></div><= div>Yes. For safety, boot loader upgrade is mandatory when you do a zpool u= pgrade of the root filesystem. It was definitely needed in the OpenZFS jump= , and we've had one or two other flag days since.</div><div><br></div><= div>It would be nice if we had a failsafe here, but we don't today. Wit= h a failsafe, we could say 'well, go ahead and try, even if it encounte= rs something=C2=A0it doesn't understand... to at least allow the system= to boot.</div><div><br></div><div>Warner</div></div></div> --000000000000d165cb05ed0fd283--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoeDvxSqqEjpnfK=FCY0K1aYEqTw80SKLAZ-5d2qrW5EA>