Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Aug 2017 11:35:05 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 221275] Unable to use zfsbootcfg
Message-ID:  <bug-221275-8-pqhPkE0OdQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221275-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-221275-8@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=3D221275

Fabian Keil <fk@fabiankeil.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fk@fabiankeil.de

--- Comment #1 from Fabian Keil <fk@fabiankeil.de> ---
zfsbootcfg actually checks for kenv(1) variables (which sysctl(8) doesn't
show).

Having said that, I can reproduce the problem that the variables aren't
set when running in bhyve.

They are set on all the physical systems I checked, though.

You can still set them manually with kenv(1) using the values from the
vdev label:

[fk@test-vm ~]sudo zdb -l /dev/gpt/bpool-vtbd1
[...]
    name: 'bpool'=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
[...]
    pool_guid: 14860026282992656750=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
[...]
    guid: 6160965258301852628=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
[...]
[fk@test-vm ~]sudo kenv vfs.zfs.boot.primary_pool=3D14860026282992656750
vfs.zfs.boot.primary_pool=3D"14860026282992656750"
[fk@test-vm ~]sudo kenv vfs.zfs.boot.primary_vdev=3D6160965258301852628
vfs.zfs.boot.primary_vdev=3D"6160965258301852628"

At least for me this resulted in zfsbootcfg reporting success:

[fk@test-vm ~]$ sudo zfsbootcfg zfs:rpool
zfs next boot options are successfully written

As I currently don't use boot environments (not yet supported by cloudiatr),
I couldn't easily test if this has any effect in bhyve, though.

--=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-221275-8-pqhPkE0OdQ>