Am 2023-10-12 07:08, schrieb Mark Millard:
I use the likes of:BE Active Mountpoint Space Created build_area_for-main-CA72 - - 1.99G 2023-09-20 10:19 main-CA72 NR / 4.50G 2023-09-21 10:10 NAME CANMOUNT MOUNTPOINT zopt0 on /zopt0 . . . zopt0/ROOT on none zopt0/ROOT/build_area_for-main-CA72 noauto none zopt0/ROOT/main-CA72 noauto nonezopt0/poudriere on /usr/local/poudriere zopt0/poudriere/data on /usr/local/poudriere/data zopt0/poudriere/data/.m on /usr/local/poudriere/data/.m zopt0/poudriere/data/cache on /usr/local/poudriere/data/cache zopt0/poudriere/data/images on /usr/local/poudriere/data/images zopt0/poudriere/data/logs on /usr/local/poudriere/data/logs zopt0/poudriere/data/packages on /usr/local/poudriere/data/packages zopt0/poudriere/data/wrkdirs on /usr/local/poudriere/data/wrkdirs zopt0/poudriere/jails on /usr/local/poudriere/jails zopt0/poudriere/ports on /usr/local/poudriere/portszopt0/tmp on /tmp zopt0/usr off /usr zopt0/usr/13_0R-src on /usr/13_0R-src zopt0/usr/alt-main-src on /usr/alt-main-src zopt0/usr/home on /usr/home zopt0/usr/local on /usr/local
[...]
If such ends up as unsupportable, it will effectively eliminate my reason for using bectl (and, so, zfs): the sharing is important to my use.
Additionally/complementary to what Kyle said... The -r option is about zop0/ROOT/main-CA72 zop0/ROOT/main-CA72/subDS1 zop0/ROOT/main-CA72/subDS2A shallow clone is only taking zop0/ROOT/main-CA72 into account, while a -r clone is also cloning subDS1 and subDS2.
So as Kyle said, your (and my) use case are not affected by this. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature