Date: Mon, 25 Jan 2021 16:17:18 -0500 From: mike tancsa <mike@sentex.net> To: Toomas Soome <tsoome@me.com> Cc: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org>, Mateusz Guzik <mjguzik@gmail.com> Subject: Re: ZFS feature compatibility? Message-ID: <d34bfe20-567e-14a5-074e-66aed6083da0@sentex.net> In-Reply-To: <207F268A-30E3-45BE-9377-79C3DC31C328@me.com> References: <28fbf9cd-0f56-f6a0-1ddf-186aeed59b95@protected-networks.net> <CC26196B-AAFB-4E5E-AAC9-B93EB3C6FD03@me.com> <9e183db9-2ca5-a7bd-2665-cc468d4b69db@sentex.net> <207F268A-30E3-45BE-9377-79C3DC31C328@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/25/2021 4:03 PM, Toomas Soome wrote: > > >> On 25. Jan 2021, at 22:15, mike tancsa <mike@sentex.net >> <mailto: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 <mailto: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 >>>> <http://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 >>>> <mailto:root@toshi.auburn.protected-networks.net>:/usr/obj/usr/src/a= md64.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 >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0still be used, but some features= are unavailable. >>>> action: Enable all features using 'zpool upgrade'. Once this is done= , >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0the pool may no longer be access= ible by software that does >>>> not support >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0the 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=C2=A0zoo.freebsd.org >> <http://zoo.freebsd.org/>,=C2=A0mjg@freebsd.org >> <mailto:mjg@freebsd.org>=C2=A0and I could not boot >> again because v2 bookmarks were on the boot pool.=C2=A0 I had to boot = from >> another disk, remove the bookmarks and then boot. This was on RELENG_1= 3 >> (stable/13-c256203-g51d73a3e46c) >> >> =C2=A0=C2=A0=C2=A0 =E2=80=94Mike > > /* > =C2=A0* List of ZFS features supported for read > =C2=A0*/ > static const char *features_for_read[] =3D { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.illumos:lz4_compress", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:hole_birth", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:extensible_dataset", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:embedded_data", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.open-zfs:large_blocks", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.illumos:sha512", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.illumos:skein", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.zfsonlinux:large_dnode", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.joyent:multi_vdev_crash_dump", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:spacemap_histogram", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:zpool_checkpoint", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:spacemap_v2", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.datto:encryption", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.datto:bookmark_v2", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.zfsonlinux:allocation_classes", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.datto:resilver_defer", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:device_removal", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:obsolete_counts", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.intel:allocation_classes", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "org.freebsd:zstd_compress", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "com.delphix:bookmark_written", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 NULL > }; > > Are you sure you have bootblocks updated? ESP for UEFI boot and > freebsd-boot for BIOS boot. > > mjg did them IIRC.=C2=A0 I just checked to make sure both were done and t= hey seem identical root@zoo2:/home/mdtancsa # dd if=3D/dev/ada8p2 of=3D/tmp/8 1024+0 records in 1024+0 records out 524288 bytes transferred in 0.046479 secs (11280092 bytes/sec) root@zoo2:/home/mdtancsa # dd if=3D/dev/ada9p2 of=3D/tmp/9 1024+0 records in 1024+0 records out 524288 bytes transferred in 0.054717 secs (9581751 bytes/sec) root@zoo2:/home/mdtancsa # md5 /tmp/8 /tmp/9 MD5 (/tmp/8) =3D e294b1344cbb49c751474facc39998ec MD5 (/tmp/9) =3D e294b1344cbb49c751474facc39998ec root@zoo2:/home/mdtancsa # Is there a way to check from the bin if its the right version ? strings of the file doesnt seem to show anything useful.=C2=A0 I wonder if its th= e UEFI boot that got missed ?=C2=A0 Just gpart bootcode -p /boot/boot1.efifat -i 1ada8 gpart bootcode -p /boot/boot1.efifat -i 1ada9 I take it ? MD5 (/tmp/81) =3D ff8762fa2b885347a0030b45b0f3844e MD5 (/tmp/91) =3D e0fa5369ddb0471373bca6b29e027680 MD5 (/boot/boot1.efi) =3D c023e2c74479b2f0710ab0337a7bab4f root@zoo2:/boot # dd if=3D/dev/ada9p1 of=3D/tmp/91 bs=3D1m 200+0 records in 200+0 records out 209715200 bytes transferred in 0.557007 secs (376503669 bytes/sec) root@zoo2:/boot # dd if=3D/dev/ada8p1 of=3D/tmp/81 bs=3D1m 200+0 records in 200+0 records out 209715200 bytes transferred in 0.475806 secs (440757874 bytes/sec) root@zoo2:/boot # md5 /tmp/81 /tmp/91 /boot/boot1 boot1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 boot1.efi* root@zoo2:/boot # md5 /tmp/81 /tmp/91 /boot/boot1.efi MD5 (/tmp/81) =3D ff8762fa2b885347a0030b45b0f3844e MD5 (/tmp/91) =3D e0fa5369ddb0471373bca6b29e027680 MD5 (/boot/boot1.efi) =3D c023e2c74479b2f0710ab0337a7bab4f I am guessing they extracted boot blocks should match, no ? =C2=A0=C2=A0=C2=A0 ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d34bfe20-567e-14a5-074e-66aed6083da0>