We just upgraded several boxes running CURRENT to r365325. These systems are
running customized kernels with ZFS statically compiled in. the host's OS is
derived from "make buildworld buildkernel" in /usr/src.
Jails on that hosts are maintained vi /etc/jail.conf, but system is installed
by misusage of ezjail. So far the environemnt.
One of the jails is a dedicated poudriere jail using ZFS. This worked so far.
Every pool this specific jail or any other jail is mounting is located below
therefore we consider
in /etc/jail.conf as sufficient. After updating all /etc/default/ and
/etc/rc.d of those poudriere-jails with ZFS everything should be inline
regarding new requests for OpenZFS .
But now enforce_statfs= "1"; isn't sufficient anymore, the jais fail to startup
with a mount error complaining about insufficient access rights. The problem
partially disappear by setting enforce_statfs= "0";, but this isn't what we
want and personally I consider it a risk. But furthermore, several ZFS datasets
prior to the upgrade successfully being exported from the hosts pools and mount
from withing the jail are now invisible within the jail.
According to /usr/src/UPDATING, tag 20200824, the features of the ZFS pools of
the main hosts have been left untouched so far, no feature upgrade has been