Bug 275199

Summary:	ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2
Product:	Base System	Reporter:	Thierry Thomas <thierry>
Component:	kern	Assignee:	freebsd-fs (Nobody) <fs>
Status:	New ---
Severity:	Affects Only Me	CC:	bsd, grahamperrin, imp, marklmi26-fbsd, michaelo
Priority:	---
Version:	15.0-CURRENT
Hardware:	Any
OS:	Any
See Also:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270409

Description Thierry Thomas freebsd_committer

2023-11-19 14:26:43 UTC

When booting my laptop Alienware 17 R 4 (Dell), it displays the error "ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2".

The complete boot sequences is:

BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2

ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2
/

Consoles: internal video/keyboard
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS 625kB/1444224kB available memory

FreeBSD/x86 bootstrap loader. Revision 1.1
(Sun Sep 24 02:21:18 CEST 2023 thierry@alien)

Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
/

and then the normal boot menu.

Note 1: details on this laptop are available at <https://wiki.freebsd.org/Laptops/Dell_Alienware_17R4>.

Note 2: this is the same machine that the one with the NVME problem reported in <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270409>, but I cannot say if this message is recent or if it was already displayed at this time. The display is very fast, and this message can be unnoticed.

Comment 1 Mark Millard 2023-11-20 03:37:31 UTC

vdev_zaps_v2 is new, openzfs-2.2 being the first official openzfs
release to contain it.

main (CURRENT) got it in:

author	rob-wing <98866084+rob-wing@users.noreply.github.com>	2023-04-20 17:07:56 +0000
committer	GitHub <noreply@github.com>	2023-04-20 17:07:56 +0000
commit	3e4ed4213d7b4e8892e9def8b06363391d8dbd60 (patch)
. . .
Create zap for root vdev
And add it to the AVZ, this is not backwards compatible with older pools
due to an assertion in spa_sync() that verifies the number of ZAPs of
all vdevs matches the number of ZAPs in the AVZ.

Granted, the assertion only applies to #DEBUG builds - still, a feature
flag is introduced to avoid the assertion, com.klarasystems:vdev_zaps_v2
. . .

But there was also:

author	Warner Losh <imp@FreeBSD.org>	2023-05-04 14:25:46 +0000
committer	Warner Losh <imp@FreeBSD.org>	2023-05-04 14:25:46 +0000
commit	5fd34912b4a51f6ebe55d0d832fab4f3c60228e7 (patch)
. . .
stand: Fix oversight in updating OpenZFS: Add com.klarasystems:vdev_zaps_v2
com.klarasystems:vdev_zaps_v2 is a new feature that the last OpenZFS
import brought in. It needs to be on the list of supported features, but
that update didn't happen so I woke up to a mailbox with multiple
complaints.
. . .


If I gather right, your report's text indicates that the loader complained,
not the kernel.

If so, it suggests that your loader is out of date by over 0.5 year and
should be updated.

Comment 2 Sam 2023-11-21 12:55:03 UTC

Having same issue on a remote HP Proliant server, always kept up to date until latest 13.2-RELEASE

> If so, it suggests that your loader is out of date by over 0.5 year and
should be updated.

Would you kindly point to a page on how to do that?

Comment 3 Sam 2023-11-21 12:56:19 UTC

Sorry, I did not read carefully, this ticket is about FreeBSD 15, my issue is in regards to FreeBSD 14.0-RELEASE.

Comment 4 Warner Losh freebsd_committer

2023-11-21 14:49:45 UTC

14.0 release notes have update procedure

Comment 5 Sam 2023-11-21 15:39:40 UTC

Thank you.

For future reference, from that document:

> After a system upgrade, but before doing a zpool upgrade, the boot loader on the ESP must be updated, or the system may become unbootable.