topic Re: one NFS v4 mount on Ubuntu but permission error "Nobody" in ONTAP Discussions

one NFS v4 mount on Ubuntu but permission error "Nobody"

Noorain02 — Tue, 04 Sep 2018 10:17:17 GMT

We have mounted one volume using NFS v4 on Ubanto server on Ontap cloud and regardless of given permission to the client at Netapp side Ubunto server (client) is getting "Nobody" "Nobody " permission error. See the output from server and help me with getting cause of this issue if anyone had the same.

Output from Ubunto server:

root@ip-10-78-1-XXX:/mnt/it-gitlab# ls -ld /mnt/it-gitlab/

drwxr-xr-x 9 nobody 4294967294 4096 Sep 4 03:21 /mnt/it-gitlab/

root@ip-IP_ADD:~# lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 14.04.5 LTS

Release: 14.04

Codename: trusty

Output from netapp cloud

CorpStg::>

Policy Rule Access Client RO

Vserver Name Index Protocol Match Rule

------------ --------------- ------ -------- --------------------- ---------

svm_CorpStg

export_it_gitlab1

1 nfs 10.78.1.XXX any

svm_CorpStg

export_it_gitlab1

2 nfs 0.0.0.0/0 any

Ontap version - 9.1

Re: one NFS v4 mount on Ubuntu but permission error "Nobody"

moep — Wed, 12 Sep 2018 11:22:39 GMT

Ensure that the NFSv4 Domain Setting on the vServer matches the FQDN of your Ubuntu client.

vserver nfs modify -vserver <foo> -v4-id-domain <bar.com>

Re: one NFS v4 mount on Ubuntu but permission error "Nobody"

wareer — Mon, 30 Dec 2024 02:33:22 GMT

With NFSv4, simply naming the domain isn't enough. You have to have one to one mapping of username@nfsv4iddomain to UID. The NFS client and NFS server both need to be able to come to the same conclusion about the name.

If you're using no name service server (like LDAP or NIS) and are relying only on local files, then there needs to be an entry for the user on the storage's passwd file and the client's passwd file. These entries must match EXACTLY.
This is a kb of the official website, you can refer to it：https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFSv4_client_shows_user_and_group_as_nobody