From nobody Wed Nov 9 19:39:49 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 4N6wKx6FHhz4VBph for ; Wed, 9 Nov 2022 19:40:21 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N6wKx3FvCz3mwV; Wed, 9 Nov 2022 19:40:21 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; none 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) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "outgoing.leidinger.net", Issuer "R3" (verified OK)) by mailgate.Leidinger.net (Postfix) with ESMTPSA id 5912D226F1; Wed, 9 Nov 2022 20:40:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1668022815; 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=YVY2QMHUuyobbaQZ0VBQD6UrvHqoV5tqWA1jLecNajc=; b=NN1sXY+ZYTrHYgtoWXPdjKXn3ZI6jyYST8nh3zlWdNsOHpcOU10SrepvAEtIMFobF8oQ/n p3qmDCZFHSRdCuIS5k8R98rmpgfgIez/T7XyVLDPdMef70J8EjA9WeDWmZsrC2AJc2viMv O94E99IN7N6ukM0TlvqkIJf+VGvUXjBeoSwOKh2HzjhgkD0Iw22wj4cgEpf64QpbIAAP/x x18C+yKqt0qi9WlCIu3tS72TBq5JkSYCOrqMvHkgk41rfpWEg8LkpK3PRpNYZQVJn3sOCD eQodvSt2O2JSE2d6Rdvvda8tPDf96XufGMNfiKLJOD0Z2YzYiK7Pgl/CIWuJng== 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 562F9368C; Wed, 9 Nov 2022 20:39:51 +0100 (CET) Date: Wed, 09 Nov 2022 20:39:49 +0100 Message-ID: <20221109203949.Horde.qIUauGgF-S3rZjw2-w-VIZT@webmail.leidinger.net> From: Alexander Leidinger To: Warner Losh Cc: marklmi@yahoo.com, tsoome@freebsd.org, Li-Wen Hsu , 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> In-Reply-To: Accept-Language: de,en Content-Type: multipart/signed; boundary="=_iRyGHLeLeeS0LMDvtdHFkCg"; 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-Rspamd-Queue-Id: 4N6wKx3FvCz3mwV X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_iRyGHLeLeeS0LMDvtdHFkCg Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Warner Losh (from Wed, 9 Nov 2022 08:54:33 -0700): > On Wed, Nov 9, 2022 at 5:46 AM Alexander Leidinger > wrote: > >> Quoting Alexander Leidinger (from Tue, 08 >> Nov 2022 10:50:53 +0100): >> > Should the above list be sorted in some way? Maybe in the same order >> > as the zpool-features lists them (sort by feature name after the >> > colon), or alphabetical? >> >> Is it OK if I commit this alphabetical sorting? [diff of feature-sorting] > > This patch looks good because it's a nop and just tidies things up a bit. > > Reviewed by: imp Will do later. >> > As Mark already mentioned some flags, I checked the features marked >> > as read only (I checked in the zpool-features man page, including >> > the dependencies documented there) and here are those not listed in >> > zfsimpl.c. I would assume as they are read-only compatible, we >> > should add them: >> > com.delphix:async_destroy >> > com.delphix:bookmarks >> > org.openzfs:device_rebuild >> > com.delphix:empty_bpobj >> > com.delphix:enable_txg >> > com.joyent:filesystem_limits >> > com.delphix:livelist >> > com.delphix:log_spacemap >> > com.zfsonlinux:project_quota >> > com.zfsonlinux:userobj_accounting >> > com.openzfs:zilsaxattr >> >> If my understanding is correct that the read-only compatible parts >> (according to the zpool-features man page) are safe to add to the zfs >> boot, here is what I have only build-tested (relative to the above >> alphabetical sorting): >> ---snip--- >> --- zfsimpl.c_sorted 2022-11-09 12:55:06.346083000 +0100 >> +++ zfsimpl.c 2022-11-09 13:01:24.083364000 +0100 >> @@ -121,24 +121,35 @@ >> "com.datto:bookmark_v2", >> "com.datto:encryption", >> "com.datto:resilver_defer", >> + "com.delphix:async_destroy", >> "com.delphix:bookmark_written", >> + "com.delphix:bookmarks", >> "com.delphix:device_removal", >> "com.delphix:embedded_data", >> + "com.delphix:empty_bpobj", >> + "com.delphix:enable_txg", >> "com.delphix:extensible_dataset", >> "com.delphix:head_errlog", >> "com.delphix:hole_birth", >> + "com.delphix:livelist", >> + "com.delphix:log_spacemap", >> "com.delphix:obsolete_counts", >> "com.delphix:spacemap_histogram", >> "com.delphix:spacemap_v2", >> "com.delphix:zpool_checkpoint", >> "com.intel:allocation_classes", >> + "com.joyent:filesystem_limits", >> "com.joyent:multi_vdev_crash_dump", >> + "com.openzfs:zilsaxattr", >> + "com.zfsonlinux:project_quota", >> + "com.zfsonlinux:userobj_accounting", >> "org.freebsd:zstd_compress", >> "org.illumos:lz4_compress", >> "org.illumos:sha512", >> "org.illumos:skein", >> "org.open-zfs:large_blocks", >> "org.openzfs:blake3", >> + "org.openzfs:device_rebuild", >> "org.zfsonlinux:allocation_classes", >> "org.zfsonlinux:large_dnode", >> NULL >> ---snip--- >> >> Anyone able to test some of those or confirms my understanding is >> correct and would sign-off on a "reviewed by" level? >> > > I'm inclined to strongly NAK this patch, absent some way to test it. > There's no issues today with any of them being absent causing > problems on boot that have been reported. The ZFS that's in the > boot loader is a reduced copy of what's in base and not everything is > supported. There's no urgency here to rush into this. The ones that > are on the list already are for things that we know we support in the > boot loader because we've gone to the trouble to put blake3 or sha512 > into it (note: Not all boot loaders will support all ZFS features in the > future... x86 BIOS booting likely is going to have to be frozen at its > current ZFS feature set due to code size issues). > > While most of these options look OK on the surface, I'd feel a lot better > if there were tests for these to prove they work. I'd also feel better if > the ZFS experts could explain how those come to be set on a zpool > as well. I'd settle for a good script that could be run as root (better > would be not as root) that would take a filesystem that was created > by makefs -t zfs and turn on these features after an zpool upgrade. > I have the vague outlines of a test suite for the boot loader that I > could see about integrating something like that into, but most of my > time these days is chasing after 'the last bug' in some kboot stuff I'm > working on (which includes issues with our ZFS in the boot loader > integration). > > So not a hard no, but I plea for additional scripts to create images > that can be tested. I didn't want to commit untested or unverified stuff. I fully agree=20=20 with=20your reasoning. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_iRyGHLeLeeS0LMDvtdHFkCg Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmNsAgQACgkQEg2wmwP4 2IZnLg//U34KrUAmwXUtGme8g9fJAZgrXMVotbGsyQVGRZPjKSGDh4W+pc38K2TW FUMV/h/WAbUdhtv6tRZAJmJ1mkrP01RmfRMSsea6L9hBoO5E+0QZ/32EMTBbHYtT awgrbQXgF9TGRKonQgxvTzBCo9NQcdXHz5V9OLl8SlgSwLKbjyVyKRyWfG6ysaF/ 9vZ97VZ9OOa6NRUzWCZ/R5ZDILYuLPV8fUpTFpLQ5tOPY41KpJd/KE9qc9HZw61y jWwbHlNdhCs5kvwLiJqoZ99z7wisSGjXqAdQHBkarNct3I2TPD5AthClJ7ffwUP0 WQ0wVtOMemtTDeo2qnX4I7wH7XWXtPuVgaKQcWsr39GVIq8KjY8ctlUMh2+5GqGW aUvkat+W2/wEO8e702k+Gd528z1eluQScYyNIzZLPnHGlFw+qwz44Lw7ETA5cxLc C4l2aIsBQ5b8wA5MFlvvrhHsc0vnz671kIiwqqObfJvXBMSwFCgH5Yhi1pAvD0DF l6m+JVm5SS7eRe7+/yj5FtVGJxXpcIHggMazmCacREtSE1VYrYYHBTDCrcjTnET2 3FWBTbITBWQGq3hO2cxJPs8MxkMh7PFCrOd1YUThav3lHwKSl2G7MhVqtAMopQYs lClJjrVd11Tvt7O08O11/oc7UdiMX2k+3aW+VoexVfsGH0R1hVo= =y0JE -----END PGP SIGNATURE----- --=_iRyGHLeLeeS0LMDvtdHFkCg--