Skip to main content
NetApp Knowledge Base

NFSv4.x mounts show file and group owner as nobody

Last Updated:

Applies to

  • ONTAP 9
  • NFSv4


  • The file ownership of the files mounted through NFSv4 from a Linux client is shown as root or nobody.
  • 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 find user1@NTAP.LOCAL (uid 1234, gid 1234). If the user in ONTAP is USER1@NTAP.LOCAL, then it won’t match.
  • The reason for this is because NFSv4 clients send symbolic user/group names rather than numeric userid/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 use nobody:nobody for the user/group file ownership.




Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device