[Bug 193128] New: NFSv3 Solaris 10 Server < - > NFSv3 Freebsd 10.1 Client

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Aug 29 18:22:02 UTC 2014


            Bug ID: 193128
           Summary: NFSv3 Solaris 10 Server < - > NFSv3 Freebsd 10.1
           Product: Base System
           Version: 10.0-PRERELEASE
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jnaughto at ee.ryerson.ca

Okay seems that there's a problem with NFSv3 implementation on Freebsd 10.1.  
I have gone through and compiled and configured a GENERIC build with the new
NFSD kernel option in place.  If I mount a NFSv3 filesystem from a Solaris 10
server to the Freebsd 10.0 client which is running dovecot 2.2.13.   Now don't
jump to say well this is a dovecot issue not a base kern issue.  As if I mount
the filesystem:

root at NFSCLIENT:<NFSv3 Mount>/mail # ls -lh A1
----------  1 bob  wheel     0B Aug 29 13:55 A1

Now if I mount the exact same filesystem this time with the -2 option in the

NFSSERVER:<NFS Filesystem>     <MOUNT POINT>    nfs rw,soft,-2  0 0

Re-mount the filesystem and using the dovecot to create the same file on the
same filesystem I get:

root at NFSCLIENT:<NFSv2 Mount>/mail # ls -lh A1
-rw-r--r--  1 bob  wheel     0B Aug 29 12:53 A1

So it seems that with NFSv3 on Freebsd10.1 it doesn't carry the perms over.  
Yet if I change to NFSv2 the problem goes away.  Yet of course I'll end up with
issues with files greater than 2gb which is an issue as a few users have 2gb
mbox files...

I actually this this issue with dovecot writing to the NFSv3 filesystem is
somehow linked to the same problem illustrated in BugID: 186293.

Please help.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list