I've got an odd issue with how the user/group ownership is being presented to my NFS clients from a Win2k8R2 server.
For some (seemingly random) files, the group or user or both is showing up as 'nfsnobody'. Applied permissions are correct - a user in the right group can write where they should be able to (and those new files show up correctly) and a user without the correct permissions does not.
As an example, let's take a directory "dept".
On the Windows Security tab for the dir, "dept" shows it's owned by a specific user (DOM\user), writable by a specific group (DOM\group), plus all the additional security entries for the Windows machine and Administrators.
The Windows server shows the correct thing using nfsfile:
E:\path> nfsfile dept
W drwxrwxr-x (0775) DOM\user DOM\group E:\path\dept
The NFS client shows this, however:
[root@linux path]# ls -lart
drwxrwxr-x 2 nfsnobody nfsnobody 4096 Feb 25 22:04 dept
The server has the right data, but something about how it's exporting via NFS is promoting Everyone/nfsnobody as the user/group for the file. Technically, it works - but a lot of daemons will see those permissions and refuse to do anything.
Any ideas? The files were originally copied to this Windows file server over rsync through NFS mounts from a NAS appliance, where the permissions show up correctly - so the Windows NFS server is getting the files written with the correct (Unix) permissions, then translating that to NTFS, then applying any inherited perms. (AFAIU)
Thanks!
Mark