Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script)

Hi,

> Am 09.11.2022 um 21:31 schrieb Alexander Leidinger <Alexander@leidinger.net>:
> Some features are used directly when enabled. Some features go back to the enabled state when some conditions are met. Some features are not reversible without re-creating the pool (e.g. device_removal). The zzpool-features man-page gives explanations which features belong into which category.

I already knew most of this, too - but thanks for bringing it to my attention again.

If I have to check each individual feature with respect to its "bootability" in the future that
is really bad news given that I have about a hundred servers to manage.

So let me shortly describe our use case.

I run servers hosting jails. I upgrade them e.g. like this:

13.1
13.2
13.3
14.1
...

The "habit" that I cited is to upgrade the zpools to match the release. We use
freebsd-update and in the rare cases where we don't we track releng/x.y.

We do not run main/head in production.

Can I be confident about upgrading my pools or not? Modulo bugs, but we have
test systems, of course.

Kind regards,
Patrick