Date: Wed, 09 Nov 2022 22:26:00 +0100 From: Alexander Leidinger <Alexander@leidinger.net> To: "Patrick M. Hausen" <pmh@hausen.com> Cc: Warner Losh <imp@bsdimp.com>, 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: <20221109222600.Horde.yo1Ry8tPu9udiPqUgtdDHNG@webmail.leidinger.net> In-Reply-To: <65689194-1F56-4429-9A52-794A8354D995@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> <CANCZdfoeDvxSqqEjpnfK=FCY0K1aYEqTw80SKLAZ-5d2qrW5EA@mail.gmail.com> <AFF06A1C-A58F-40E7-9A21-A585F95E447D@hausen.com> <CANCZdfq0Q67tqE-6%2BSjbdJVH_p0oMh5Xz_bW=SWWM%2BhWnDLZYw@mail.gmail.com> <20221109220540.Horde.6GRfN8bbUC4AsLcvjhWbUgm@webmail.leidinger.net> <65689194-1F56-4429-9A52-794A8354D995@hausen.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Quoting "Patrick M. Hausen" <pmh@hausen.com> (from Wed, 9 Nov 2022 22:11:29 +0100): > Hi, > >> Am 09.11.2022 um 22:05 schrieb Alexander Leidinger >> <Alexander@leidinger.net>: >> Attention, "upgrade" is overloaded here. "OS upgrade" will not >> render the pool unbootable (modulo bugs), but "zpool upgrade rpool" >> will (except we have provisions that zpool upgrade doesn't enable >> all features in case the bootfs property is set). > > And we are back at the start. The "problem" is that I really like > consistency. > So when "zpool status" throws that ominous message at me - any you have > to admit that it is phrased like a warning - I want simply to get > rid of that. > After a reasonable after-update grace period. > > But during our discussion I have come to wonder: > > - I upgrade from 13.0 to 13.1, I do a "zpool upgrade" afterwards, I > also upgrade the boot loader > > - I install 13.1 with ZFS > > What is the difference? Shouldn't these two imaginary systems be > absolutely the same in terms > of ZFS features, boot loader, and all that? On quick look I haven't found a place where a compatibility setting is used for the rpool during the creation, so I can't point out what the exact difference is. Given that empty_bpobj is not in the list of the boot code, it can't be the same, some limit of enabled features has to be in place during initial install, and your example has to be different. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmNsGucACgkQEg2wmwP4 2IZ0bQ/+LwtM+ImQ66cuthOD1BO2oCnaIhl2LvtxxIl7HXW3VdHECEiYHI+bpWap /1B94/ShoOgCDhpD12jmIIOCMYi38Q8ILKmzQWeBKFp7KxjYEQOUXQKNH3dYN0SE zXZHCZarVeKkpzWzlwAWVIMjGBH9GrB7QgOFJ/CmRralun+U/8zEIMwTZ1Po8c/8 MCfTjnL4BACWr3K0aU18oRiPWNLO/cSJ7t1I5mZ0Kve9UUeseaL5mGbtYRGCqxZS frCn7s10iywy+3ifZKmuHtqKUo9dJ5aI5e/u1pdzEeOiMPx+5vQ8wjkDkpEjnC+W S/JetO4VGOmDEbyubzIQs6nCuP7rL+N11VHQet3QAZuFNdv2dwV+tl/35l9p1vdQ sAMh6ZS8EZZHYCLAXU9n1D8wrE49kGYZx/XRzyBHtQVT8tt1LsIE8dPlccLBXK6t u+fKZIXIQBgFhReAHA2hYEIsw09L4lsLuU4m/7FBq48uscZ/r501Tz4bfb8dzCUW yfYzpi/HP1UwTAVrdMFWlDwIXFUfAhVsqV8azOc9vhRRXgqjq1hGKl1jiVhpLdqQ eW8u0m9xosBgbNMmjj+elB7UzOt2MeMWJBk2JibSiIs9J0Dz2dK2Win7ozMWT0Bf glfni7ILmyCMbGAkfxCAI2B1OJHwio2QPBgVTGO6L4+iPe9Ov+c= =BZvq -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221109222600.Horde.yo1Ry8tPu9udiPqUgtdDHNG>