Date: Mon, 25 Jan 2021 23:03:59 +0200 From: Toomas Soome <tsoome@me.com> To: mike tancsa <mike@sentex.net> Cc: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: ZFS feature compatibility? Message-ID: <207F268A-30E3-45BE-9377-79C3DC31C328@me.com> In-Reply-To: <9e183db9-2ca5-a7bd-2665-cc468d4b69db@sentex.net> References: <28fbf9cd-0f56-f6a0-1ddf-186aeed59b95@protected-networks.net> <CC26196B-AAFB-4E5E-AAC9-B93EB3C6FD03@me.com> <9e183db9-2ca5-a7bd-2665-cc468d4b69db@sentex.net>
index | next in thread | previous in thread | raw e-mail
> On 25. Jan 2021, at 22:15, mike tancsa <mike@sentex.net> wrote: > > On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: >> >>> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current <freebsd-current@freebsd.org> wrote: >>> >>> I have a few machines on which I've been hesitant to run 'zpool upgrade' as I'm not sure of the (boot?) implications. They report like this .. >>> >>> imb@toshi:/home/imb> uname -a >>> FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-eb61de5b78: Fri Jan 22 10:03:02 EST 2021 root@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI amd64 >>> >>> imb@toshi:/home/imb> zpool status >>> pool: zroot >>> state: ONLINE >>> 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(5) for details. >>> >>> Is it safe to upgrade the root pool? >>> >>> imb >> We can not boot from encrypted pool and draid. Rest is all ok. Please note, you may need to update the bootblocks. >> > last Friday on zoo.freebsd.org <http://zoo.freebsd.org/>, mjg@freebsd.org <mailto:mjg@freebsd.org> and I could not boot > again because v2 bookmarks were on the boot pool. I had to boot from > another disk, remove the bookmarks and then boot. This was on RELENG_13 > (stable/13-c256203-g51d73a3e46c) > > —Mike /* * List of ZFS features supported for read */ static const char *features_for_read[] = { "org.illumos:lz4_compress", "com.delphix:hole_birth", "com.delphix:extensible_dataset", "com.delphix:embedded_data", "org.open-zfs:large_blocks", "org.illumos:sha512", "org.illumos:skein", "org.zfsonlinux:large_dnode", "com.joyent:multi_vdev_crash_dump", "com.delphix:spacemap_histogram", "com.delphix:zpool_checkpoint", "com.delphix:spacemap_v2", "com.datto:encryption", "com.datto:bookmark_v2", "org.zfsonlinux:allocation_classes", "com.datto:resilver_defer", "com.delphix:device_removal", "com.delphix:obsolete_counts", "com.intel:allocation_classes", "org.freebsd:zstd_compress", "com.delphix:bookmark_written", NULL }; Are you sure you have bootblocks updated? ESP for UEFI boot and freebsd-boot for BIOS boot. rgds, toomashelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?207F268A-30E3-45BE-9377-79C3DC31C328>