Date: Wed, 9 Nov 2022 22:47:28 +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: <F450AC9B-15E8-4E60-83CC-1A90404D01BD@hausen.com> In-Reply-To: <40D4F908-CE30-4AAF-89FA-E6849027FB17@hausen.com> 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> <CANCZdfoeDvxSqqEjpnfK=FCY0K1aYEqTw80SKLAZ-5d2qrW5EA@mail.gmail.com> <AFF06A1C-A58F-40E7-9A21-A585F95E447D@hausen.com> <CANCZdfq0Q67tqE-6%2BSjbdJVH_p0oMh5Xz_bW=SWWM%2BhWnDLZYw@mail.gmail.com> <20221109220540.Horde.6GRfN8bbUC4AsLcvjhWbUgm@webmail.leidinger.net> <65689194-1F56-4429-9A52-794A8354D995@hausen.com> <20221109222600.Horde.yo1Ry8tPu9udiPqUgtdDHNG@webmail.leidinger.net> <40D4F908-CE30-4AAF-89FA-E6849027FB17@hausen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Am 09.11.2022 um 22:38 schrieb Patrick M. Hausen <pmh@hausen.com>: >> Am 09.11.2022 um 22:26 schrieb Alexander Leidinger = <Alexander@leidinger.net>: >> On quick look I haven't found a place where a compatibility setting = is used for the rpool during the creation, so I can't point out what the = exact difference is. >> Given that empty_bpobj is not in the list of the boot code, it can't = be the same, some limit of enabled features has to be in place during = initial install, and your example has to be different. >=20 > That feature was imported into FreeBSD in 2012 so it should be > enabled in every pool created since then. I apologize, should have included that in the last mail. This is a current FreeBSD 13.1-p2 hosting system we run. Boots quite fine ;-) Kind regards, Patrick ----------- [ry93@pdn006 ~]$ zpool get all zroot|grep feature zroot feature@async_destroy enabled = local zroot feature@empty_bpobj active = local zroot feature@lz4_compress active = local zroot feature@multi_vdev_crash_dump enabled = local zroot feature@spacemap_histogram active = local zroot feature@enabled_txg active = local zroot feature@hole_birth active = local zroot feature@extensible_dataset active = local zroot feature@embedded_data active = local zroot feature@bookmarks enabled = local zroot feature@filesystem_limits enabled = local zroot feature@large_blocks enabled = local zroot feature@large_dnode enabled = local zroot feature@sha512 enabled = local zroot feature@skein enabled = local zroot feature@userobj_accounting active = local zroot feature@encryption enabled = local zroot feature@project_quota active = local zroot feature@device_removal enabled = local zroot feature@obsolete_counts enabled = local zroot feature@zpool_checkpoint enabled = local zroot feature@spacemap_v2 active = local zroot feature@allocation_classes enabled = local zroot feature@resilver_defer enabled = local zroot feature@bookmark_v2 enabled = local zroot feature@redaction_bookmarks enabled = local zroot feature@redacted_datasets enabled = local zroot feature@bookmark_written enabled = local zroot feature@log_spacemap active = local zroot feature@livelist active = local zroot feature@device_rebuild enabled = local zroot feature@zstd_compress enabled = local zroot feature@draid enabled = local -----------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F450AC9B-15E8-4E60-83CC-1A90404D01BD>