When will nobody show as owner of NFS mounts?
Applies to
- ONTAP
- NFSv4
- NFS Mounts
Answer
Nobody is seen in the one of the following three scenarios:
- The client does not know who the user is
getent passwd <uid>
andgetent group <gid>
on a client can be used in conjunction withfile-directory show
from ONTAP to see if there is a mismatch- If
getent
doesn't show a user or group, then the client has no idea who the user/group is and will say "nobody". - In NFSv3, the client could instead display the uid/gid, but for NFSv4 ONTAP will not send a uid/gid if it can obtain a name.
- If the client and ONTAP disagree on the user it will show 'nobody'
- Example: Client reports uid 1111 maps to 'user' but ONTAP has local mapping for 1111 to 'adminuser'
- Example: Client reports uid 1111 maps to 'user' but ONTAP has local mapping for 1111 to 'adminuser'
- If
- The ID Domain does not match - if the ID Domain does not match, the client will not attempt to look up the user/group.
- It will assume that it cannot obtain an accurate result.
- Reference KB: NFSv4.x client shows user and group as nobody NFSv3 shows as correct owner
- The file/directory is legitimately owned by 'nobody'
- common nobody uid/gids are 99, 65534, and 65535
- This can be the result of files written by users squashed to the anonymous user via export policy, e.g. if the security type is null on the mount or in the case of root squashing
Additional Information
NFS export displays owner and group as nobody - Resolution Guide - NetApp Knowledge Base