Date: Sat, 29 Sep 2012 16:32:12 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Tim Gustafson <tjg@soe.ucsc.edu> Cc: freebsd-fs@freebsd.org Subject: Re: Exporting ZFS File System to Multiple Subnets Message-ID: <20120929143212.GG1402@garage.freebsd.pl> In-Reply-To: <CAG27QgTz2MsQPRw7Vjj9Q_hmh%2B0-m2Zpq56A0VXaAA26_iVDWA@mail.gmail.com> References: <CAG27QgQbwot1%2Bfu=2PmQYpaqKqb8Ob8sieb28XuXJDaWbZnKqQ@mail.gmail.com> <CAG27QgTz2MsQPRw7Vjj9Q_hmh%2B0-m2Zpq56A0VXaAA26_iVDWA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--6AFz5yWxU/FsGPwt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 26, 2012 at 12:50:13PM -0700, Tim Gustafson wrote:
> > And it seems that ZFS somehow
> > gets in the way of /etc/exports for ZFS file systems, so that if I
> > turn off sharenfs ("zfs inherit sharenfs tank/export; zfs inherit
> > sharenfs tank/projects") it actually blocks the export lines in
> > /etc/exports from being mounted.
>=20
> So, this was incorrect. Something else was going on that was
> preventing the exports in /etc/exports from working; after a few
> reboots, with sharenfs set to "inherited" for all file systems, we are
> able to specify exports in /etc/exports again.
And this is what I would recommend. sharenfs property syntax is very
limited, but you can turn off that property and just use /etc/exports
as for any other file system.
--=20
Pawel Jakub Dawidek http://www.wheelsystems.com
FreeBSD committer http://www.FreeBSD.org
Am I Evil? Yes, I Am! http://tupytaj.pl
--6AFz5yWxU/FsGPwt
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlBnBmsACgkQForvXbEpPzSwEACghPjjzRHa3ojYhDUVsUzePFQF
si0AoLohObgJEAVMiqJkqxb1Yp2Adrbh
=d9sA
-----END PGP SIGNATURE-----
--6AFz5yWxU/FsGPwt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120929143212.GG1402>