Date: Tue, 30 Aug 2016 21:00:04 +0200 From: Julien Cigar <julien@perdition.city> To: Lev Serebryakov <lev@FreeBSD.org> Cc: Willem Jan Withagen <wjw@digiware.nl>, freebsd-fs@freebsd.org Subject: Re: ZFS + NFS + multiple hosts/mount options ..? Message-ID: <20160830190004.GM1779@mordor.lan> In-Reply-To: <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org> References: <20160829211001.GI1779@mordor.lan> <7a508630-3bcc-2e3d-a78e-8d5e0675ab85@FreeBSD.org> <dab0002c-61d7-3bf9-cadd-faf564d1f413@digiware.nl> <5aee018f-51aa-2aeb-0964-7bfc88b7bf54@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--sy9WyBOsCRoUO165 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 30, 2016 at 06:46:44PM +0200, Lev Serebryakov wrote: > On 30.08.2016 18:31, Willem Jan Withagen wrote: >=20 > >>> Is there a way through the zfs set sharenfs=3D"..." property to share > >>> data/somefs readonly to host "dev.lan" _and_ read/write to host=20 > >>> "duvel.prod.lan" ? Or should I just set sharenfs=3D"off" and use > >>> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple > >>> hosts/options/... when the sharenfs property is used .. > >> No luck here. I've raised this question multiple times withoput any > >> reaction. Here is (very old) PRs with patch, which implements this: > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D147881 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202820 > >> > >=20 > > I'd say, forget about getting any flexible through sharenfs. > WHY?! >=20 > > Did that discussion about 3 years ago, and it boiled down. Don't dare to > I don't see any good reason to not support this, aside "It will not be > compatible with Illumos". I don't buy this, sorry. Any other reasons? >=20 > > change it because the people doing ZFS don't like it. > There is one BIG problem: deep ZFS hierarchies. If I need to export 100 > FSes (100 users' home directories, for example) in one ZFS tree to 4 > networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports > by hands. All these lines will be virtually the same, and good luck to > maintain this mess. I agree with you, although in my case it's not so much an issue as everything is managed by SaltStack ... but it's rather ugly to have 100+ lines in /etc/exports. What's more problematic is that it's virtually impossible (without ugly=20 hacks) to share a simple zfs fs "ro" to one net, and "rw" to another=20 one with the sharenfs property Anyway, I ditched sharenfs, zfs share, ... and I use /etc/exports >=20 > If "sharenfs" supports multiple hosts/networks, I need to set this > property ONCE (on zpool/home, parent of all FSes in question) and IT'S > ALL! And if I need to change same options, I need to change it ONCE and > re-export ZFS. >=20 > Unfortunately, it is NOT enough to export parent FS :( >=20 > --=20 > // Lev Serebryakov --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --sy9WyBOsCRoUO165 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXxdewAAoJELK7NxCiBCPAq8oP/23of3AKnzKRg0QXJWn2P1Py lVca2VI4skItpDT97Vr3BGmjnF3DuWd1e6UThR55HafvuCj8fEje8DJsh/sgJtBH x4cDYH0SZ+B92cQqux+p1SuJTtcdv1gqj3OczQfrOLU1RsRhBvaLz40hVar0lBiH uTUzKWBEtHbcxmYtlKDMmLwJqH/gP3wewmUhxxuHuvfxDKV+0DQ7eDf7OBiFM3rT B/iaWpwoqcBFe5oRpfLIhcKL3jkQHZrGWGhLXFEAZyxkNG/YxeE0yNcSkf48Ol98 RygB0c8hF/yBj8y7rga1Xm93olQUXw/UHUmwbRrlSq0puGHlmrlhEK4GjUKQ/YW/ X7Khg0V4hfqMlv8UbMiWG/umzVQtE6iai9YMG4Z9RVA1O2cVm4DjHJmsFkHvEnu4 2V2T7+moank05FnWl4Bz59rVYbjKaR2yB4MPM8JMInZvZ+9sNacMIIACprSyGA3k WLj/i7KVAR3dT8hkcacYPTpv5iuDsS4GDZQRjFhbg9l+QBeSbvHsKLItU5r8vAa/ PA3tm7VzlbX4uMs83BJz5ldxAK/XMd3t7iBCCUv2Vu4b9gAmKkarW026+yLYcBt5 VmpLE09OjXpXG9OG1E6NYWDghdA/JodNioYZD03P34+psmNRQfa63gCO64mCMAak pvp5zqxam/FIZ5WE5ng6 =K9Ky -----END PGP SIGNATURE----- --sy9WyBOsCRoUO165--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160830190004.GM1779>