Date: Fri, 27 Feb 2015 22:55:41 +0100 From: Christian Baer <christian.baer@uni-dortmund.de> To: freebsd-fs@freebsd.org Subject: Re: The magic of ZFS and NFS (2nd try) Message-ID: <2401301.b3eZRBi7it@falbala.rz1.convenimus.net> References: <4257601.p3oiXZFr4n@falbala.rz1.convenimus.net> <54E7A2CF.60804@pinyon.org> <2437038.yvsE2IGTDZ@falbala.rz1.convenimus.net> <201502231413.t1NEDITT000687@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin Simmons wrote: > According to exports(5), that reduces it to zero: > The third form has the string ``V4:'' followed by a single absolute path > name, > to specify the NFSv4 tree root. This line does not export any file > system, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > but simply marks where the root of the server's directory tree is for > NFSv4 > clients. The exported file systems for NFSv4 are specified via the other > lines in the exports file in the same way as for NFSv2 and NFSv3. I see the part in the manpage you are referring to. The way nfs reacts doesn't seem to be that way though. I have changed the contents of /etc/exports to /usr/archive/Shared -alldirs -network 192.168.100/24 I still cannot mount that share. The V4: at the beginning of the line did not change anything I could notice. If I let the path point to a ZFS file system, I get permission denied, when it points to a path on UFS, it works fine. Die directories in question have the correct owner and group. Is there some way that ZFS may have a different setting for this? Kind regards, Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2401301.b3eZRBi7it>