Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Sep 2020 11:58:23 -0400
From:      Ryan Moeller <freqlabs@FreeBSD.org>
To:        freebsd-current@freebsd.org
Subject:   Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
Message-ID:  <91342af7-944f-76ee-5b4f-841b70c4263f@FreeBSD.org>
In-Reply-To: <20200906154939.GA1799@freedom.nl>
References:  <20200830193756.GA6325@freedom.nl> <320492e8-4dee-22f3-443b-829fdb2c3e8b@gmail.com> <20200906091649.GA2517@freedom.nl> <360dd0d5-5026-9714-417f-d05691b78618@FreeBSD.org> <20200906154939.GA1799@freedom.nl>

next in thread | previous in thread | raw e-mail | index | archive | help

On 9/6/20 11:49 AM, marco wrote:
> On Sun, Sep 06, 2020 at 10:22:33AM -0400, you (Ryan Moeller) sent the following to [freebsd-current] :
>>> I switched back to base ZFS whilst on r364030 and upgraded to r365336 and deinstalled
>>> openzfs and openzfs-kmod for now.
>>> ZFS in base nicely auto-imported both zroot and backup pools for the 1st
>>> time.
>> I need to update the port, it's a little behind what's in base now.
> Thanks Ryan
>
> How does one verify which version of OpenZFS is actually in base?
> sysutils/openzfs{-kmod} has/have 20200821, UPDATING has the 20200824 listing.
> I can't find any version reference of OpenZFS in base from svn log
> either.
>

The git hashes are the most unambiguous way to see what you have. The 
svn log shows the last vendor update for zfs brought it to fd20a81b, and 
the most recent version of the port is at 6fe3498ca.

For the port I have hijacked zfs --version to show the git hash in the 
version string, but the base zfs does not do this, so it is not as easy 
to determine at runtime there.

-Ryan




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91342af7-944f-76ee-5b4f-841b70c4263f>