Re: remnants after major upgrade

void <void_at_f-m.fm> wrote on
Date: Sat, 03 Sep 2022 11:07:32 UTC :
> Hello arm@,
> 
> After source upgrading from 13.1-p2 to 14-current, I notice the following in zfs list
> 
> # zfs list
> NAME                                        USED  AVAIL  REFER  MOUNTPOINT
> zroot                                      64.2G  1.68T    96K  /zroot
> zroot/ROOT                                 13.2G  1.68T    96K  none
> zroot/ROOT/13.1-RELEASE_2022-08-31_153934     8K  1.68T   750M  /
> zroot/ROOT/default                         13.2G  1.68T  12.7G  /
> 
> there's no beadm installed - it's a plain almost default installation.
> Should I delete the zroot/ROOT/13.1-RELEASE_2022-08-31_153934 ?

"zfs mount" shows just what is mounted.

"zfs list" shows data sets from imported pools no matter if
they are mounted at the time or not. The MOUNTPOINT column
is a property indicating where a mount would show up by
default. Some may be mounted at the time and others may not
be.

Your later:

QUOTE
bectl list
BE                             Active Mountpoint Space Created
13.1-RELEASE_2022-08-31_153934 -      -          498M  2022-08-31 15:39
default                        NR     /          14.6G 2022-05-12 09:50
END QUOTE

indicates only one of the 2 is mounted: it shows
"/" only for boot environment active mounts. (Having
both mounted would normally be obvious: things would
not be operating like normal at all.)

It is possible to replace the "/"s that "zfs list" shows
with "none". In fact there is a page that recommends
such:

https://wiki.freebsd.org/BootEnvironments

under "Pool Layout/Design". Part of the point being that
accidentally ending up with both zroot/ROOT/default
and zroot/ROOT/13.1-RELEASE_2022-08-31_153934 mounted
would not be a good thing and the way things are in
your environment makes it easier to end up with such
accidents. (But having both those "/"s is a normal
default configuration despite this.)

===
Mark Millard
marklmi at yahoo.com