Re: ZFS feature compatibility?

[Toomas Soome via freebsd-current]

> On 26. Jan 2021, at 00:23, John Kennedy  wrote:
> 
>> Thanks, I am new to the EFI world.  Does the name now have to be
>> BOOTx64.efi ?
>> 
>> root@zoo2:/boot # ls -l /mnt/EFI/freebsd/
>> total 824
>> -rwxr-xr-x  1 root  wheel  843776 Nov 21 10:50 loader.efi
>> root@zoo2:/boot #
> 


if there is no UEFI bootmanager configured (see man efibootmgr), then (ESP) 
efi/boot/bootx64.efi is default. with efibootmgr(8), you can configure custom 
path, such as (ESP) efi/freebsd/loader.efi

rgds,
toomas



>  I don't know.  This came out of an email thread I had a while ago:
> 
>   Date: Thu, 9 Jul 2020 14:18:54 -0700
>   From: John Kennedy 
>   To: Kyle Evans 
>   Cc: FreeBSD-STABLE Mailing List 
>   Subject: Re: 12.1p7 no longer boots after doing zpool upgrade -a
> 
>  The "new" documentation was here:
> 
>   https://wiki.freebsd.org/UEFI
> 
>  The older stuff is still mentioned here:
> 
>   https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[John Kennedy]

> Thanks, I am new to the EFI world.  Does the name now have to be
> BOOTx64.efi ?
> 
> root@zoo2:/boot # ls -l /mnt/EFI/freebsd/
> total 824
> -rwxr-xr-x  1 root  wheel  843776 Nov 21 10:50 loader.efi
> root@zoo2:/boot #

  I don't know.  This came out of an email thread I had a while ago:

Date: Thu, 9 Jul 2020 14:18:54 -0700
From: John Kennedy 
To: Kyle Evans 
Cc: FreeBSD-STABLE Mailing List 
Subject: Re: 12.1p7 no longer boots after doing zpool upgrade -a

  The "new" documentation was here:

https://wiki.freebsd.org/UEFI

  The older stuff is still mentioned here:

https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[Toomas Soome via freebsd-current]

> On 25. Jan 2021, at 23:08, Allan Jude  wrote:
> 
> On 2021-01-25 16:03, Toomas Soome via freebsd-current wrote:
>> 
>> 
>>> On 25. Jan 2021, at 22:15, mike tancsa  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 
>  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 
> r...@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  
>>> >, m...@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,
>> toomas
>> ___
>> freebsd-current@freebsd.org  mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current 
>> 
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org 
>> "
>> 
> 
> Toomas: how difficult do we think it would be to make a ports version of
> the updated boot code, especially for the case of people using the
> openzfs-kmod on 12.2?
> 
> 

zstd would be interesting…  

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[mike tancsa]

On 1/25/2021 4:51 PM, John Kennedy wrote:
> On Mon, Jan 25, 2021 at 04:17:18PM -0500, mike tancsa wrote:
>> Is there a way to check from the bin if its the right version ? strings
>> of the file doesnt seem to show anything useful.  I wonder if its the
>> UEFI boot that got missed ?  Just
>>
>> gpart bootcode -p /boot/boot1.efifat -i 1ada8
>> gpart bootcode -p /boot/boot1.efifat -i 1ada9
>>
>> I take it ?
>   I don't think that is the way to update UEFI anymore (although last time I
> looked it was still documented that way in one place).
>
>   For my last bootcode (which had UEFI & BIOS) update, I basically did this:
>
>   gpart show nvd0
>   =>   40  976773088  nvd0  GPT  (466G)
>40 409600 1  efi  (200M)
>409640   1024 2  freebsd-boot  (512K)
>410664984- free -  (492K)
>411648   16777216 3  freebsd-swap  (8.0G)
>  17188864  959584256 4  freebsd-zfs  (458G)
> 976773120  8- free -  (4.0K)
>
>   gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 nvd0
>   partcode written to nvd0p2
>   bootcode written to nvd0
>
>   mount -vt msdosfs /dev/nvd0p1 /mnt
>   /dev/nvd0p1 on /mnt (msdosfs, local, writes: sync 1 async 0, 
> reads: sync 13 async 0, fsid 5c003200)
>   install -p -m755 /boot/loader.efi /mnt/efi/boot/BOOTx64.efi
>   umount -v /mnt
>   /dev/nvd0p1: unmount from /mnt

Thanks, I am new to the EFI world.  Does the name now have to be
BOOTx64.efi ?

root@zoo2:/boot # ls -l /mnt/EFI/freebsd/
total 824
-rwxr-xr-x  1 root  wheel  843776 Nov 21 10:50 loader.efi
root@zoo2:/boot #

    ---Mike


>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[John Kennedy]

On Mon, Jan 25, 2021 at 04:17:18PM -0500, mike tancsa wrote:
> Is there a way to check from the bin if its the right version ? strings
> of the file doesnt seem to show anything useful.  I wonder if its the
> UEFI boot that got missed ?  Just
> 
> gpart bootcode -p /boot/boot1.efifat -i 1ada8
> gpart bootcode -p /boot/boot1.efifat -i 1ada9
> 
> I take it ?

  I don't think that is the way to update UEFI anymore (although last time I
looked it was still documented that way in one place).

  For my last bootcode (which had UEFI & BIOS) update, I basically did this:

gpart show nvd0
=>   40  976773088  nvd0  GPT  (466G)
 40 409600 1  efi  (200M)
 409640   1024 2  freebsd-boot  (512K)
 410664984- free -  (492K)
 411648   16777216 3  freebsd-swap  (8.0G)
   17188864  959584256 4  freebsd-zfs  (458G)
  976773120  8- free -  (4.0K)

gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 nvd0
partcode written to nvd0p2
bootcode written to nvd0

mount -vt msdosfs /dev/nvd0p1 /mnt
/dev/nvd0p1 on /mnt (msdosfs, local, writes: sync 1 async 0, 
reads: sync 13 async 0, fsid 5c003200)
install -p -m755 /boot/loader.efi /mnt/efi/boot/BOOTx64.efi
umount -v /mnt
/dev/nvd0p1: unmount from /mnt

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[mike tancsa]

On 1/25/2021 4:03 PM, Toomas Soome wrote:
>
>
>> On 25. Jan 2021, at 22:15, mike tancsa > > 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
 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
  14.0-CURRENT FreeBSD
 14.0-CURRENT #25 main-eb61de5b78: Fri Jan 22 10:03:02 EST 2021
 r...@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
>> , m...@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.
>
>
mjg did them IIRC.  I just checked to make sure both were done and they
seem identical

root@zoo2:/home/mdtancsa # dd if=/dev/ada8p2 of=/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=/dev/ada9p2 of=/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) = e294b1344cbb49c751474facc39998ec
MD5 (/tmp/9) = 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.  I wonder if its the
UEFI boot that got missed ?  Just

gpart bootcode -p /boot/boot1.efifat -i 1ada8

gpart bootcode -p /boot/boot1.efifat -i 1ada9

I take it ?

MD5 (/tmp/81) = ff8762fa2b885347a0030b45b0f3844e
MD5 (/tmp/91) = e0fa5369ddb0471373bca6b29e027680
MD5 (/boot/boot1.efi) = c023e2c74479b2f0710ab0337a7bab4f

root@zoo2:/boot # dd if=/dev/ada9p1 of=/tmp/91 bs=1m
200+0 records in
200+0 records out
209715200 bytes transferred in 0.557007 secs (376503669 bytes/sec)
root@zoo2:/boot # dd if=/dev/ada8p1 of=/tmp/81 bs=1m
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  boot1.efi*
root@zoo2:/boot # md5 /tmp/81 /tmp/91 /boot/boot1.efi
MD5 (/tmp/81) = ff8762fa2b885347a0030b45b0f3844e
MD5 (/tmp/91) = e0fa5369ddb0471373bca6b29e027680
MD5 (/boot/boot1.efi) = c023e2c74479b2f0710ab0337a7bab4f

I am guessing they extracted boot blocks should match, no ?

    ---Mike


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[Allan Jude]

On 2021-01-25 16:03, Toomas Soome via freebsd-current wrote:
> 
> 
>> On 25. Jan 2021, at 22:15, mike tancsa  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 
  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 
 r...@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 , m...@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,
> toomas
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

Toomas: how difficult do we think it would be to make a ports version of
the updated boot code, especially for the case of people using the
openzfs-kmod on 12.2?


-- 
Allan Jude
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[Toomas Soome via freebsd-current]

> On 25. Jan 2021, at 22:15, mike tancsa  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 
>>>  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 
>>> r...@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 , m...@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,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[mike tancsa]

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 
>>  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 
>> r...@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, m...@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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[mike tancsa]

I ran into an issue not being able to boot because of v2 bookmarks on
the boot pool on RELENG_13 just last Friday.

    ---Mike

On 1/25/2021 2:31 PM, Michael Butler via freebsd-current 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
> r...@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
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS feature compatibility?

[Toomas Soome via freebsd-current]

> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current 
>  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 
> r...@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.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZFS feature compatibility?

[Michael Butler via freebsd-current]

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 
r...@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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"