Multiple entries in ZFS "sharenfs" property?

[Rick Macklem]

Julian Elischer wrote:
> On 8/3/15 8:30 PM, Rick Macklem wrote:
> > Lev wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA512
> >>
> >> On 02.08.2015 23:56, Willem Jan Withagen wrote:
> >>
> >>> Nope, that doesn't work, as far as I can tell. You'd have to revert
> >>> to editting /etc/exports.
> >>   Yep, I know.
> >>
> > Btw, even if the "hack" Julian Elischer requested was in the system,
> > you would still have to export all the volumes, so this discussion
> > doesn't really change.
> > The only difference would be that the clients could use an NFSv3 mount
> > and not an NFSv4 one.
> I don't believe we use a separate export entry for each sub-fs
> but I'd have to go  look again.
> 
Maybe you use the "inherited" feature of ZFS's sharenfs?
(I'm pretty sure the exports will be stored/checked on a per-file system
 basis and will need to exist for all file systems in the hierarchy. Maybe
 your patch changed that, but it wasn't in what you emailed me months ago.)

rick

> 
> > Just wanted to make this clear, rick
> >
> >>> Or hack on 'zfs set sharenfs' to generate multiple lines, in some
> >>> sort of format. Like making ';' a line separator, and then prefix
> >>> each part with the volume we are modifying.
> >>>
> >>> Place to give it a go are in:
> >>> cddl/compat/opensolaris/misc/fsshare.c:213 if (share) {
> >>> fprintf(newfd, "%s\t%s\n", mountpoint, translate_opts(shareopts));
> >>> } And there split the shareopts on the split char (eg. ';') in
> >>> several shareopts and then loop over them. Disadvantage is that the
> >>> max length op the options is: MAXPATHLEN. So you can easily run out
> >>> of space if you have many exports to do.
> >>   Here is PR with patch about this, from 2012 :(
> >>
> >> - --
> >> // Lev Serebryakov
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v2
> >>
> >> iQJ8BAEBCgBmBQJVv1kyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> >> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
> >> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EeP9d0P/229Jje1vw8QB9LuWkNH81xE
> >> SIeYOnXRs4OoJDBmxW1xi5kaKqT+j6A9m7lWEXjm/nWGsULNcjDtP4uqQehVZDl3
> >> 7d/eGZDQgrZa5zUxvxMfb0hoWxCZNYFf6N1sPB+98ZwPVH2ADD+7h4ljusoI19gD
> >> ZVjTEDeWKBln2YWWHXDDJwjFeF/AqwZzf6o0Nn6Wg2k49pAW4hjvRfVFBXYVo8CA
> >> sWsD9ilgYteD6LEPdHbPy2pgprlsmIwLV84zjGb2Lk0Txs7k4CP5RnRo276wkmKY
> >> lFdvlyDOFna2UsJqTbAdYD5XeTC0Zx08sqd0dPvgmugYICpgFou1rClTd6HYLDTC
> >> +n1kmY8CrGn6omOwLeuckzkroPVFV/RgzRfKFdCabTfAoRe1a60Y7MTFCKUVmZnc
> >> OOz2F1Ph3PJAyl5aiIZAuDikj+PEkeqbYJPQxeh2neKwOLTLj4G9oGx+CFo8t6Fk
> >> Y793GqkrmIkh4O7o8LrLqhT7/II/MybC2a31RjZRfdukofIgC+CEw56IcP7tgb8U
> >> L2f+QxprnQDbwFwkjJAvU/x6dPvy4cztF5vA3qtY5HAW21u+ROrAHBorANq83nZT
> >> Y7Ab4vrcThoXTJnNgzN0usOz0OUdtHtVz+5OOoLNJsPVbFFrdIa2I67jW4giDiVv
> >> +Vo4KfE2/wL2MpiviQQ7
> >> =GB/t
> >> -----END PGP SIGNATURE-----
> >> _______________________________________________
> >> freebsd-fs at freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
> >>
> > _______________________________________________
> > freebsd-fs at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
> >
> 
>