From nobody Wed Nov 9 20:15:23 2022 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N6x6Y1VqWz4XH7W for ; Wed, 9 Nov 2022 20:15:33 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-256)) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N6x6X253Gz3y5x; Wed, 9 Nov 2022 20:15:32 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b="SIAi/IwC"; spf=pass (mx1.freebsd.org: domain of Alexander@leidinger.net designates 2a00:1828:2000:313::1:5 as permitted sender) smtp.mailfrom=Alexander@leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net Received: from outgoing.leidinger.net (p508d4280.dip0.t-ipconnect.de [80.141.66.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) client-signature ECDSA (P-256)) (Client CN "outgoing.leidinger.net", Issuer "R3" (verified OK)) by mailgate.Leidinger.net (Postfix) with ESMTPSA id CF15D22828; Wed, 9 Nov 2022 21:15:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1668024926; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fk4otahl7LWahxty9enI/mEV0tWAK63fzTvECCtNU1o=; b=SIAi/IwCHBDlqk+8+WoQxc/uUIRJ9qftcnaE9AE/M/pbMq3XrH84Wc/+CCRu4cZ03JznuA W27L3nYjgcj205QuzrObtzNCIgTE9/e1jB9XmdPhsCjEYkIqQkMt+0lZS/RC2zLgiOR3uZ /cU92fvBNgbT36RREkfNOqRcJbO8FpuzlOISgQGzKzzsM0ojk1M4DxwXMYYdJWmCvQD461 fNDzLeTCRVPNWocIoijxyRDc07ZnFF4NyHZ78IRuO0f6o8KlMlZ8sguz9e8LwucXNHiwu6 VYLBnXA4yIiz1LJU5yJdXdv3rUl4Hr/1MRrCsOnHmrNL/t9l8zDWw9Sb0ER81w== Received: from webmail.leidinger.net (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (Client did not present a certificate) by outgoing.leidinger.net (Postfix) with ESMTPS id 24F6234A3; Wed, 9 Nov 2022 21:15:24 +0100 (CET) Date: Wed, 09 Nov 2022 21:15:23 +0100 Message-ID: <20221109211523.Horde.3dLzlxI4V6n_crjLsz_d08E@webmail.leidinger.net> From: Alexander Leidinger To: "Patrick M. Hausen" Cc: imp@bsdimp.com, marklmi@yahoo.com, tsoome@freebsd.org, 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) References: <202211070339.2A73dJlO027991@gitrepo.freebsd.org> <20221107121514.Horde.nulS9Wg1s3yzAsXXkuJRBa9@webmail.leidinger.net> <20221108105053.Horde.eqgFiBJe2ngGAj6BkXcv5-Z@webmail.leidinger.net> <20221109134610.Horde.JB7ibQTWprHbmIUfhg7JY7f@webmail.leidinger.net> <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> In-Reply-To: <6C570897-1C17-43EF-A19C-0F50DA2669B0@hausen.com> Accept-Language: de,en Content-Type: multipart/signed; boundary="=_p3gxBz2LtTE2NeI3kjiPm6c"; protocol="application/pgp-signature"; micalg=pgp-sha256 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.10 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx:c]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; MLMMJ_DEST(0.00)[current@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE]; DKIM_TRACE(0.00)[leidinger.net:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_CC(0.00)[bsdimp.com,yahoo.com,freebsd.org]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_FIVE(0.00)[6]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4N6x6X253Gz3y5x X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_p3gxBz2LtTE2NeI3kjiPm6c Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting "Patrick M. Hausen" (from Wed, 9 Nov 2022=20=20 21:02:52=20+0100): > Hi, > >> Am 09.11.2022 um 20:58 schrieb Alexander Leidinger=20=20 >>=20: >> >> Quoting "Patrick M. Hausen" (from Wed, 9 Nov 2022=20=20 >>=2020:49:37 +0100): >> >>> Hi, >>> >>>> Am 09.11.2022 um 20:45 schrieb Alexander Leidinger=20=20 >>>>=20: >>>> But "zpool set feature@edonr=3Denabled rpool" (or any other feature=20= =20 >>>>=20not in the list we talk about) would render it unbootable. >>> >>> Sorry, just to be sure. So an active change of e.g. checksum or=20=20 >>>=20compression algorithm >>> might render the system unbootable but a zpool upgrade never will?=20= =20 >>>=20At least not intentionally? ;-) >> >> If you mean "zpool upgrade", then no (modulo bugs). OpenZFS uses=20=20 >>=20the feature flags instead of zpool upgrade. > > I know about feature flags and all my pools are recent enough to have the= m. > > Yet, I made it a habit to whenever I see this message: > > ----------- > status: Some supported features are not enabled on the pool. The pool can > still be used, but some features are unavailable. > action: Enable all features using 'zpool upgrade'. Once this is done, > the pool may no longer be accessible by software that does not support > the features. See zpool-features(7) for details. > ----------- > > to do a "zpool upgrade" after some time of burn in followed by an=20=20 >=20update of the > boot loader. > > I desire to know if that is in fact dangerous. Ugh. This changed. It is indeed dangerous now. I just tested it with a=20= =20 non-root=20pool which didn't had all flags enabled. "zpool upgrade=20=20 "=20will now enable all features. I remember that it wasn't in the past and I had to enable the feature=20=20 flags=20by hand. I don't know if a pool with bootfs set is behaving=20=20 differently,=20but I consider testing this with a real rpool to be=20=20 dangerous. Bye, Alexander. --=20 http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_p3gxBz2LtTE2NeI3kjiPm6c Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmNsClsACgkQEg2wmwP4 2IacrQ/6AsOXPqZ/69u7Yssr5efUefe1ABdArQ7NL3nOuHq51pSOz6+P4yaL0nLV 8JM3REE/6n/moezidCRw9CRCWja0do3aqYJeibC9II8w11oCmFWfYe3GUmMmjs2f oF9dgwUY5CrcvzKxw48q40lpLqYLVRcqd9CybEA7bGhYcGCBhC9OUlcRMlOlvNQW PAeyM01DVebyBWOKHRoEvqkvCAew1f6uP5IH9NZCqQXB6uLQg8aAWuJtwnhCEbHT z539mq2ho/0TsTAi2paTbryNyOOjnNfXL2pH9+kVTBTm2QoxCM2yG409g0hQwL57 IqD0+dFnI+OocQnpa1wPe+P2tZYDUXvCLRdgD3V9FDMY+f86hljgS5m8yHtKCvZ9 X7EqCEubnI6Xn21NI2zyk8D/y/QksrlE/9YQv5Wd27ZjKFLIFjwEjHMKsZRmHVil jNNDjZhkYoMXuipNKX1igdt9PqOmUyDqYAEI4f0YSVT8c7q0q5CExPG3k4dTZNgi vXPg0g2VCLTzZp577mIU7A7AJ2HL4dQfb4FGPd6o0LSVclmV6x5ZBK9OKEKIxhac +R7u0aT10a7bmh6bSyjBlGPdtezwzlnmr4Jue/PdDsrle+bzwxfm9WQy9p7u/sk8 N/+iw9pnx47ZvrYoQfmIsRf1xQP0dAygUPkYEzbohJbL6JdaeQQ= =2BuR -----END PGP SIGNATURE----- --=_p3gxBz2LtTE2NeI3kjiPm6c--