ZFS ZFS - Datasets created by freebsd-update upgrade patches

[s2r]

FreeBSD freebsd.local 13.2-RELEASE-p8 FreeBSD 13.2-RELEASE-p8 GENERIC amd64

Everytime a patch was applied via freebsd-update a new dataset was created:

[freebsd:/ $]> zfs list
NAME                                                    USED  AVAIL     REFER  MOUNTPOINT
zroot                                                   122G  1.62T       88K  /zroot
zroot/ROOT                                              118G  1.62T       88K  none
zroot/ROOT/13.2-RELEASE-p1_2023-08-06_180926              8K  1.62T     34.0G  /
zroot/ROOT/13.2-RELEASE-p2_2023-09-10_235747              8K  1.62T     34.3G  /
zroot/ROOT/13.2-RELEASE-p3_2023-10-05_123918              8K  1.62T     34.3G  /
zroot/ROOT/13.2-RELEASE-p4_2023-11-08_124951              8K  1.62T     34.4G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090222              8K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341            340M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1       340M  1.62T      781M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146            746M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare  44.0M  1.62T     8.98G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/sync       401M  1.62T     2.29G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/ubuntu2    301M  1.62T     22.1G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308             40K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/smbshare     8K  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/sync         8K  1.62T     2.06G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/ubuntu2      8K  1.62T     22.0G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE_2023-06-22_164022                 8K  1.62T     33.9G  /
zroot/ROOT/default                                      117G  1.62T     35.7G  /
zroot/ROOT/default/adc1                                 722M  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/default/mailrelay                            361M  1.62T      228M  /usr/jails/jails-data/mailrelay-data
zroot/ROOT/default/smbshare                            9.04G  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/default/sync                                2.36G  1.62T     2.07G  /usr/jails/jails-data/sync-data
zroot/ROOT/default/ubuntu2                             62.5G  1.62T     21.5G  /usr/jails/vm/ubuntu2
zroot/ROOT/default/ubuntu2/dsk2.vhd                      56K  1.62T       56K  -
zroot/ROOT/default/ubuntu2/dsk_sqldata.vhd             2.57G  1.65T     2.57G  -
zroot/tmp                                              52.1M  1.62T     51.5M  /tmp
zroot/usr                                              3.24G  1.62T       88K  /usr
zroot/usr/home                                         6.97M  1.62T     6.81M  /usr/home
zroot/usr/ports                                        1.84G  1.62T     1.14G  /usr/ports
zroot/usr/src                                          1.39G  1.62T       88K  /usr/src
zroot/var                                              21.9M  1.62T       88K  /var
zroot/var/audit                                         144K  1.62T       88K  /var/audit
zroot/var/crash                                         144K  1.62T       88K  /var/crash
zroot/var/log                                            21M  1.62T     19.0M  /var/log
zroot/var/mail                                          440K  1.62T      336K  /var/mail
zroot/var/tmp                                           152K  1.62T       88K  /var/tmp
zssd                                                   14.2G   201G       96K  /zssd
zssd/encrypted                                         14.2G   201G     14.2G  /encrypted

Also a zfs mount shows:

[freebsd:/ $]> zfs mount
zroot/ROOT/default              /
zroot/ROOT/default/adc1         /usr/jails/jails-data/adc1-data
zroot/ROOT/default/mailrelay    /usr/jails/jails-data/mailrelay-data
zroot/ROOT/default/smbshare     /usr/jails/jails-data/smbshare-data
zroot/ROOT/default/ubuntu2      /usr/jails/vm/ubuntu2
zssd                            /zssd
zroot/var/mail                  /var/mail
zroot/var/audit                 /var/audit
zroot/var/crash                 /var/crash
zroot/usr/src                   /usr/src
zroot/var/log                   /var/log
zroot                           /zroot
zroot/var/tmp                   /var/tmp
zroot/usr/home                  /usr/home
zroot/usr/ports                 /usr/ports
zroot/tmp                       /tmp
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/sync  /usr/jails/jails-data/sync-data
zssd/encrypted                  /usr/jails/jails-data/sync-data/encrypted

I've got a jail running samba as a AD from the mounts listed above I've got two datasets able to provide the data for the jail. Why is that?
[freebsd:/usr/jails/jails-data $]> sudo zfs mount | grep adc1
zroot/ROOT/default/adc1         /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1  /usr/jails/jails-data/adc1-data

sudo zfs unmount -f zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1
cannot unmount '/usr/jails/jails-data/adc1-data': pool or dataset is busy

I'm confused. I would like ideally not to have those extra dataset, how can I destroy them safely? Would they be created again with the following freebsd-update patch?

 

[s2r]

After running freebsd-update install, it aborted but created new datasets.

[freebsd:/ $]> sudo freebsd-update install
src component not installed, skipped
Creating snapshot of existing boot environment... cannot create 'zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622/ubuntu2/dsk_sqldata.vhd': 'canmount' does not apply to datasets of this type
error when calling zfs_clone() to create boot env
error when calling zfs_clone() to create boot env
error when calling zfs_clone() to create boot env
error when calling zfs_clone() to create boot env
Failed to create bootenv 13.2-RELEASE-p9_2024-02-27_210622
failed.
[freebsd:/ $]> zfs list
NAME                                                    USED  AVAIL     REFER  MOUNTPOINT
zroot                                                   122G  1.62T       88K  /zroot
zroot/ROOT                                              118G  1.62T       88K  none
zroot/ROOT/13.2-RELEASE-p1_2023-08-06_180926              8K  1.62T     34.0G  /
zroot/ROOT/13.2-RELEASE-p2_2023-09-10_235747              8K  1.62T     34.3G  /
zroot/ROOT/13.2-RELEASE-p3_2023-10-05_123918              8K  1.62T     34.3G  /
zroot/ROOT/13.2-RELEASE-p4_2023-11-08_124951              8K  1.62T     34.4G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090222              8K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341            340M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1       340M  1.62T      781M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146            746M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare  44.0M  1.62T     8.98G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/sync       401M  1.62T     2.29G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/ubuntu2    301M  1.62T     22.1G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308             40K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/smbshare     8K  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/sync         8K  1.62T     2.06G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/ubuntu2      8K  1.62T     22.0G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622             40K  1.62T     35.7G  /
zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622/smbshare     8K  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622/sync         8K  1.62T     2.07G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p9_2024-02-27_210622/ubuntu2      8K  1.62T     21.5G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE_2023-06-22_164022                 8K  1.62T     33.9G  /
zroot/ROOT/default                                      117G  1.62T     35.7G  /
zroot/ROOT/default/adc1                                 722M  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/default/mailrelay                            361M  1.62T      228M  /usr/jails/jails-data/mailrelay-data
zroot/ROOT/default/smbshare                            9.04G  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/default/sync                                2.36G  1.62T     2.07G  /usr/jails/jails-data/sync-data
zroot/ROOT/default/ubuntu2                             62.5G  1.62T     21.5G  /usr/jails/vm/ubuntu2
zroot/ROOT/default/ubuntu2/dsk2.vhd                      56K  1.62T       56K  -
zroot/ROOT/default/ubuntu2/dsk_sqldata.vhd             2.57G  1.65T     2.57G  -
zroot/tmp                                              52.1M  1.62T     51.5M  /tmp
zroot/usr                                              3.24G  1.62T       88K  /usr
zroot/usr/home                                         6.97M  1.62T     6.81M  /usr/home
zroot/usr/ports                                        1.84G  1.62T     1.14G  /usr/ports
zroot/usr/src                                          1.39G  1.62T       88K  /usr/src
zroot/var                                              21.9M  1.62T       88K  /var
zroot/var/audit                                         144K  1.62T       88K  /var/audit
zroot/var/crash                                         144K  1.62T       88K  /var/crash
zroot/var/log                                            21M  1.62T     19.0M  /var/log
zroot/var/mail                                          440K  1.62T      336K  /var/mail
zroot/var/tmp                                           152K  1.62T       88K  /var/tmp
zssd                                                   14.2G   201G       96K  /zssd
zssd/encrypted                                         14.2G   201G     14.2G  /encrypted

 

[SirDice]

I would like ideally not to have those extra dataset, how can I destroy them safely?

Look at bectl list and use bectl destroy to remove them.

Or in one fell swoop (use at your discretion, this will be destructive):
bectl list -H | grep RELEASE | cut -w -f1 | xargs -n1 bectl destroy

Would they be created again with the following freebsd-update patch?

Yes. You should keep them, they can be a life saver after a botched update. But once you're confident the system runs properly you need to clean up. If you really, really don't want them, in /etc/freebsd-update.conf:

# Create a new boot environment when installing patches
# CreateBootEnv yes

 

[sko]

FreeBSD freebsd.local 13.2-RELEASE-p8 FreeBSD 13.2-RELEASE-p8 GENERIC amd64

Everytime a patch was applied via freebsd-update a new dataset was created:

[freebsd:/ $]> zfs list
NAME                                                    USED  AVAIL     REFER  MOUNTPOINT
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1       340M  1.62T      781M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_094647/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-02_104532/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557             16K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_161557/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146            746M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare  44.0M  1.62T     8.98G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/sync       401M  1.62T     2.29G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/ubuntu2    301M  1.62T     22.1G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308             40K  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/smbshare     8K  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/sync         8K  1.62T     2.06G  /usr/jails/jails-data/sync-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-05_143308/ubuntu2      8K  1.62T     22.0G  /usr/jails/vm/ubuntu2
zroot/ROOT/13.2-RELEASE_2023-06-22_164022                 8K  1.62T     33.9G  /
zroot/ROOT/default                                      117G  1.62T     35.7G  /
zroot/ROOT/default/adc1                                 722M  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/default/mailrelay                            361M  1.62T      228M  /usr/jails/jails-data/mailrelay-data
zroot/ROOT/default/smbshare                            9.04G  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/default/sync                                2.36G  1.62T     2.07G  /usr/jails/jails-data/sync-data
zroot/ROOT/default/ubuntu2                             62.5G  1.62T     21.5G  /usr/jails/vm/ubuntu2
zroot/ROOT/default/ubuntu2/dsk2.vhd                      56K  1.62T       56K  -
zroot/ROOT/default/ubuntu2/dsk_sqldata.vhd             2.57G  1.65T     2.57G  -

why on earth are those jails within the zroot/ROOT dataset? 'zroot/ROOT' is exclusively intended for the base system root, not for jails...

I suspect freebsd-update chokes because it doesn't know how to deal with jails that are descendands (also clones?) of system snapshots/clones created by freebsd-update.
You might be able to create full copies of those jail datasets by zfs send | recv them (without -R), but no guarantee this will solve the dependency hell that have been created when cloning and snapshotting jails off of other clones...

You should always use a distinct parent dataset for jails (e.g. zroot/jails) and not intermingle them with (base) system datasets, especially ROOT.

 

[s2r]

They were created by a jail management system. I'm in the process of moving all of those jails from /zroot/ROOT. I don't mind erasing all the snapshots. Do see there would be a problem while deleting all of those datasets created by freebsd-update? But if the process fails should it delete what it has created (freebsd-update)?

 

[s2r]

Look at bectl list and use bectl destroy to remove them.

Or in one fell swoop (use at your discretion, this will be destructive):
bectl list -H | grep RELEASE | cut -w -f1 | xargs -n1 bectl destroy


Yes. You should keep them, they can be a life saver after a botched update. But once you're confident the system runs properly you need to clean up. If you really, really don't want them, in /etc/freebsd-update.conf:

# Create a new boot environment when installing patches
# CreateBootEnv yes

I will destroy all older boot environments. As you suggested I had disabled the creation of boot environments in freebsd-update.conf but just in case I enabled it back yesterday.

 

[s2r]

Look at bectl list and use bectl destroy to remove them.

Or in one fell swoop (use at your discretion, this will be destructive):
bectl list -H | grep RELEASE | cut -w -f1 | xargs -n1 bectl destroy


Yes. You should keep them, they can be a life saver after a botched update. But once you're confident the system runs properly you need to clean up. If you really, really don't want them, in /etc/freebsd-update.conf:

# Create a new boot environment when installing patches
# CreateBootEnv yes

I ran the command and it seems that some jails are using some of the datasets.

[freebsd:/usr/jails/vm $]> bectl list -H | grep RELEASE | cut -w -f1 | xargs -n1 bectl destroy
cannot destroy 'zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1': dataset is busy
unknown error
cannot destroy 'zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare': dataset is busy
unknown error

Should I snapshot those jails and then send/recv to zroot/ROOT/default/adc1 and zroot/ROOT/default/smbshare respectively or better send them to the proper new dataset for jails.

At least now zfs list returns less lines:

[freebsd:/usr/jails/vm $]> bectl list
BE                                Active Mountpoint Space Created
13.2-RELEASE-p5_2023-11-28_090341 -      -          270M  2023-11-28 09:03
13.2-RELEASE-p5_2023-12-04_162146 -      -          462M  2023-12-04 16:21
default                           NR     /          116G  2019-01-15 07:59
[freebsd:/usr/jails/vm $]> zfs list
NAME                                                    USED  AVAIL     REFER  MOUNTPOINT
zroot                                                   120G  1.62T       88K  /zroot
zroot/ROOT                                              116G  1.62T       88K  none
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341            264M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-11-28_090341/adc1       264M  1.62T      781M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146            445M  1.62T     34.8G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/adc1         8K  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/smbshare  44.5M  1.62T     8.98G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/13.2-RELEASE-p5_2023-12-04_162146/sync       401M  1.62T     2.29G  /usr/jails/jails-data/sync-data
zroot/ROOT/default                                      116G  1.62T     35.7G  /
zroot/ROOT/default/adc1                                 721M  1.62T      713M  /usr/jails/jails-data/adc1-data
zroot/ROOT/default/mailrelay                            358M  1.62T      228M  /usr/jails/jails-data/mailrelay-data
zroot/ROOT/default/smbshare                            9.03G  1.62T     8.97G  /usr/jails/jails-data/smbshare-data
zroot/ROOT/default/sync                                2.27G  1.62T     2.07G  /usr/jails/jails-data/sync-data
zroot/ROOT/default/ubuntu2                             62.2G  1.62T     21.5G  /usr/jails/vm/ubuntu2
zroot/ROOT/default/ubuntu2/dsk2.vhd                      56K  1.62T       56K  -
zroot/ROOT/default/ubuntu2/dsk_sqldata.vhd             2.57G  1.65T     2.57G  -
zroot/tmp                                              52.1M  1.62T     51.5M  /tmp
zroot/usr                                              3.24G  1.62T       88K  /usr
zroot/usr/home                                         6.97M  1.62T     6.81M  /usr/home
zroot/usr/ports                                        1.84G  1.62T     1.14G  /usr/ports
zroot/usr/src                                          1.39G  1.62T       88K  /usr/src
zroot/var                                              22.0M  1.62T       88K  /var
zroot/var/audit                                         144K  1.62T       88K  /var/audit
zroot/var/crash                                         144K  1.62T       88K  /var/crash
zroot/var/log                                          21.0M  1.62T     19.0M  /var/log
zroot/var/mail                                          440K  1.62T      336K  /var/mail
zroot/var/tmp                                           152K  1.62T       88K  /var/tmp
zssd                                                   14.2G   201G       96K  /zssd
zssd/encrypted                                         14.2G   201G     14.2G  /encrypted

 

[s2r]

why on earth are those jails within the zroot/ROOT dataset? 'zroot/ROOT' is exclusively intended for the base system root, not for jails...

I suspect freebsd-update chokes because it doesn't know how to deal with jails that are descendands (also clones?) of system snapshots/clones created by freebsd-update.
You might be able to create full copies of those jail datasets by zfs send | recv them (without -R), but no guarantee this will solve the dependency hell that have been created when cloning and snapshotting jails off of other clones...

You should always use a distinct parent dataset for jails (e.g. zroot/jails) and not intermingle them with (base) system datasets, especially ROOT.

13.2p5 -> 14.0R - freebsd-update uprade - fails while creating boot environment

Hi all! This week I tried to upgrade to 14.0-RELEASE from 13.2p5 but I failed. I ran into an zfs error while running freebsd-update upgrade and merging all the config changes. I have many datasets that are used as disks for vms. The upgrade fails with the following error: ............. #...

forums.freebsd.org