NFSv4.x mounts show file and group owner as nobody
Applies to
- ONTAP 9
- NFSv4
Issue
- The file ownership of the files mounted through NFSv4 from a Linux client is shown as
root
ornobody
. - Attempts to change ownership of the file are unsuccessful.
- When you see
nobody
for the user and/or group in file listings, that generally means something in NFSv4.x is misconfigured. - For example, if
user1@NTAP.LOCAL
(uid 1234, gid 1234) is accessing an export, then ONTAP must be able to finduser1@NTAP.LOCAL
(uid 1234, gid 1234). If the user in ONTAP isUSER1@NTAP.LOCAL
, then it won’t match. - The reason for this is because NFSv4 clients send symbolic
user/group
names rather than numericuserid/groupid
as it was in NFSv3 and the cluster needs a way to map this symbolic names to numeric IDs. - If the information in
/etc/passwd
and/etc/group
information between the cluster and the Linux host does not match, the cluster will usenobody:nobody
for theuser/group
file ownership.