So, I am resurrecting this thread, since I now have Win10 Enterprise and trying to do an NFS mount on it
I have done the mount using a non-priv cmd window
If I create a file on the windows box, a few things happen:
1) I get the error everyone sees above
2) The file IS created. It seems like any first operation on the file fails. I can edit it, get the annoying message and complete the edit
3) The file ownership shows some huge uid/gid, like 4867453431 for uid and gid
4) No other user can set/edit the file since the owner is set so wierd, until set to the valid values
5) Files end up at 755 protection, even though I use a mount switch to set to 777
So, to make it work, required '-o nolock'. There also seems to be a bug in MS mount program, as it does not allow multiple -o switches, but if you
comma seperate items, it is allowed, but ignored, ie:
'mount -o nolock -o casesensitive=yes' fails with a parse error
'mount -o nolock,casesensitive=yes' is allowed, but the arguments past the first seem ignored
So, after great consideration, I will do SMB mounts. If I need to turn off locking to make it work, it isn't any better than smb/nfs mounting, so
why kludge things?