Date: Fri, 4 Sep 2020 14:13:18 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: freebsd-current <freebsd-current@freebsd.org> Subject: Fw: OpenZFS support merged: problem mounting ZFS within JAILs Message-ID: <20200904141314.566d1d38@freyja>
next in thread | raw e-mail | index | archive | help
Begin forwarded message: Date: Fri, 4 Sep 2020 14:06:12 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: Matthew Macy <mmacy@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org>, freebsd-fs <freebsd-fs@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: OpenZFS support merged: problem mounting ZFS within JAILs On Mon, 24 Aug 2020 19:38:53 -0700 Matthew Macy <mmacy@freebsd.org> wrote: > r364746 merged OpenZFS support in to HEAD. > > The change should be transparent unless you want to use new features. > I caution against 'zpool upgrade' for the next few weeks. > > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D364746 > > If you encounter problems please report them to me, Ryan Moeller, and > -current. _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" Hello. We just upgraded several boxes running CURRENT to r365325. These systems a= re 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 instal= led by misusage of ezjail. So far the environemnt. One of the jails is a dedicated poudriere jail using ZFS. This worked so f= ar. Every pool this specific jail or any other jail is mounting is located bel= ow POOL/ezjail therefore we consider enforce_statfs=3D "1"; 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=3D "1"; isn't sufficient anymore, the jais fail to = startup with a mount error complaining about insufficient access rights. The probl= em partially disappear by setting enforce_statfs=3D "0";, but this isn't what= we want and personally I consider it a risk. But furthermore, several ZFS dat= asets 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 pool= s of the main hosts have been left untouched so far, no feature upgrade has bee= n performed. Some hints would be nice. Kind regards, oh _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200904141314.566d1d38>