Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[marco]

On Sun, Sep 06, 2020 at 11:58:23AM -0400, you (Ryan Moeller) sent the following 
to [freebsd-current] :
> 
> 
> 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.

Nice, wasn't aware the port supported zfs --version to show the git hashes.
Would definitely be nice for base ZFS to also support it at runtime.

-- 
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[Ryan Moeller]

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

___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[marco]

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.

-- 
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[Ryan Moeller]

On 9/6/20 5:16 AM, marco wrote:

On Sat, Sep 05, 2020 at 12:02:58AM +0100, you (Graham Perrin) sent the 
following to [freebsd-current] :

FYI 


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.

-Ryan

___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[marco]

On Sat, Sep 05, 2020 at 12:02:58AM +0100, you (Graham Perrin) sent the 
following to [freebsd-current] :
> >
> FYI 
> 

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.

-- 
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[marco]

On Sat, Sep 05, 2020 at 12:02:58AM +0100, you (Graham Perrin) sent the 
following to [freebsd-current] :
> > What's the best advice here?
> > I could switch back to base ZFS in this active BE, see if the system will 
> > be able to import zroot and mount all my datasets and boot, then try to 
> > create another BE using base ZFS and then attempt to update.
> >
> FYI 
> 
>  >> sysutils/openzfs bectl activate … cannot promote … not a cloned 
> filesystem … did not successfully activate boot environment

Thanks Graham

-- 
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
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: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[Graham Perrin]

On 30/08/2020 20:37, marco wrote:

…


However the boot fails dropping me to the mountroot prompt.

Luckily activating r364030-OpenZFS again is not a problem and the system will 
happily boot from that again after attempting to boot from r364030-OpenZFS2.

So now I have only 1 working BE and it feels a bit tricky to try an upgrade in 
place.
What's the best advice here?
I could switch back to base ZFS in this active BE, see if the system will be 
able to import zroot and mount all my datasets and boot, then try to create 
another BE using base ZFS and then attempt to update.


FYI 

>> sysutils/openzfs bectl activate … cannot promote … not a cloned 
filesystem … did not successfully activate boot environment


___
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"

bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem

[marco]

I'm still on r364030 using sysutils/openzfs 2020081800 (compiled from
ports)

pkg info -s openzfs
openzfs-2020081800 15.3MiB

I currently only have 1 BE and would like to attempt to upgrade to
anything past r364746
I don't use encryption, won't attempt an 'zpool upgrade' of zroot so think I 
should be safe to move forward.

# bectl list -aDs
BE/Dataset/Snapshot  Active Mountpoint Space Created

r364030-OpenZFS
  zroot/ROOT/r364030-OpenZFS NR /  15.2G 2020-08-22 22:46


create new BE

# bectl create r364030-OpenZFS2
root@harbinger:~ # bectl list -aDs
BE/Dataset/Snapshot  Active Mountpoint Space 
Created

r364030-OpenZFS
  zroot/ROOT/r364030-OpenZFS NR /  15.2G 
2020-08-22 22:46
  r364030-OpenZFS@2020-08-30-19:23:04-0  -  -  0 
2020-08-30 19:23

r364030-OpenZFS2
  zroot/ROOT/r364030-OpenZFS2-  -  8K
2020-08-30 19:23
zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 -  -  0 
2020-08-30 19:23

activate new BE

# bectl activate r364030-OpenZFS2
cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
Did not successfully activate boot environment r364030-OpenZFS2


# zfs get origin zroot/ROOT/r364030-OpenZFS2
NAME PROPERTY  VALUE
 SOURCE
zroot/ROOT/r364030-OpenZFS2  origin
zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0  -


Despite the warning/erros messages listed a 'bectl list' does show that the new 
BE will be active on reboot

# bectl list -aDs
BE/Dataset/Snapshot  Active Mountpoint Space 
Created

r364030-OpenZFS
  zroot/ROOT/r364030-OpenZFS N  /  15.2G 
2020-08-22 22:46
  r364030-OpenZFS@2020-08-30-19:23:04-0  -  -  0 
2020-08-30 19:23

r364030-OpenZFS2
  zroot/ROOT/r364030-OpenZFS2R  -  8K
2020-08-30 19:23
zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 -  -  0 
2020-08-30 19:23


However the boot fails dropping me to the mountroot prompt.

Luckily activating r364030-OpenZFS again is not a problem and the system will 
happily boot from that again after attempting to boot from r364030-OpenZFS2.

So now I have only 1 working BE and it feels a bit tricky to try an upgrade in 
place.
What's the best advice here?
I could switch back to base ZFS in this active BE, see if the system will be 
able to import zroot and mount all my datasets and boot, then try to create 
another BE using base ZFS and then attempt to update.

-- 
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
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"