Date: Wed, 9 Nov 2022 21:40:39 +0100 From: "Patrick M. Hausen" <pmh@hausen.com> To: Alexander Leidinger <Alexander@leidinger.net> 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: <D6D6F7BC-3D12-4A4F-8D0B-90CA4E7CF746@hausen.com> In-Reply-To: <20221109213149.Horde.hR9YpUCQ4NbOZcsX1JxqBgu@webmail.leidinger.net> 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> <20221109204509.Horde.lh5parVrWDSJ7kQCFa64hqe@webmail.leidinger.net> <5AFBB434-BB3B-4B5A-AB32-11DAFD03A2AD@hausen.com> <20221109205846.Horde.Rm5dcHB7p4mSbfFmxReYEDW@webmail.leidinger.net> <6C570897-1C17-43EF-A19C-0F50DA2669B0@hausen.com> <20221109211523.Horde.3dLzlxI4V6n_crjLsz_d08E@webmail.leidinger.net> <63316DBD-FFB7-44BA-ADD3-CACBE715518D@hausen.com> <20221109213149.Horde.hR9YpUCQ4NbOZcsX1JxqBgu@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D6D6F7BC-3D12-4A4F-8D0B-90CA4E7CF746>