Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script)
- Reply: Alexander Leidinger : "Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script)"
- In reply to: Alexander Leidinger : "Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 09 Nov 2022 21:11:29 UTC
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? Kind regards, Patrick