Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Apr 2024 03:35:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 277886] ZFS boot loader gives up too easily on unsupported zpool flags
Message-ID:  <bug-277886-227-9QS5g1MWZ1@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-277886-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-277886-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277886

Warner Losh <imp@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imp@FreeBSD.org

--- Comment #4 from Warner Losh <imp@FreeBSD.org> ---
efibootmgr makes it harder to find the right loader.efi...  You'd need to l=
ook
at the kenv vars we set to see what was actually booted...

Though, to be honest, maybe we just take a page from that and have the boot
loader export all the ZFS features in the read only set. We can use *THAT* =
to
know whether or not to update. Nothing exported, then you gotta force maybe=
? Or
we hard code the list the day the feature is committed (though it wouldn't =
save
you from older code, so maybe the list of the 13.2 loader.efi). Having the =
boot
loader export what it can do...

Though if you *do* update loader.efi, then this won't work, so maybe not.
Unless we update the list from install, though we don't know for sure what's
going to boot...

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277886-227-9QS5g1MWZ1>