[Bug 281003] NFS client can open the server on ZFS with sharenfs dataset
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 23 Aug 2024 22:54:57 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281003 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Individual Port(s) |bin CC| |rmacklem@FreeBSD.org Assignee|fs@FreeBSD.org |rmacklem@FreeBSD.org Version|Latest |Unspecified Product|Ports & Packages |Base System --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- This appears to be a bug in mountd. -ro=192.168.1.56 is bogus, but mountd does not spot it as an error. Btw, both of your sharenfs settings are bogus, since -ro is not supposed to have "=192.168.1.56" after it. All the sharenfs property does is autogenerate an exports line. It can be found in /etc/zfs/exports and should obey the same syntax as "man 5 exports" describes. (Althougn the sharenfs parser in OpenZFS should be improved, the bogus case should not get past mountd.) I'll take a look at mountd.c and try to come up with a patch. I am not sure what you were trying to do by specifying one IP address followed by ro=anther-ip, but you cannot mix read/write and read-only exports on the same line. --> Until you have the very recent patch in PR#147881, you cannot generate multiple lines via sharenfs. --> To do multiple lines, you need to create them manually in /etc/exports and not use the sharenfs property. Thanks for reporting it, rick ps: And never put a "=XXX" after "ro" for an exports option. -- You are receiving this mail because: You are the assignee for the bug.