NS0-191 · Question #27
A user on an NFSv4 client is listing a directory and sees the file in an is -1 listing shown below. "rwr------1 nobody nobody 10767 Mar 24 2016 party.txt" The customer would like to know why the…
The correct answer is B. There is an NFSv4 ID domain mismatch. https://kb.netapp.com/support/s/article/ka11A00000015igQAA/troubleshooting-workflow-user- and-the-user-group-displayed-as-nobody-in-nfs-v4?language=en_US Cause 1: The id-domain settings are out of order How to determine if this is the cause On an NFS v4 mounted directory, all…
Question
A user on an NFSv4 client is listing a directory and sees the file in an is -1 listing shown below. "rwr------1 nobody nobody 10767 Mar 24 2016 party.txt" The customer would like to know why the user and group shows as "nobody". Which statement would explain why this is happening?
Options
- AThe permissions does not allow for listing the owner.
- BThere is an NFSv4 ID domain mismatch.
- CThere is no owner or group set on the file.
- DThe file resides on an NTFS style volume.
How the community answered
(40 responses)- A13% (5)
- B78% (31)
- C5% (2)
- D5% (2)
Explanation
https://kb.netapp.com/support/s/article/ka11A00000015igQAA/troubleshooting-workflow-user- and-the-user-group-displayed-as-nobody-in-nfs-v4?language=en_US Cause 1: The id-domain settings are out of order How to determine if this is the cause On an NFS v4 mounted directory, all the files and directories are listed as 'owned', and group as owned by 'nobody'. Additionally, the following EMS message is displayed, which indicates that the client's domain does not match the Vserver's domain: Nblade.Nfsv4NsdbDomainMismatch. The EMS message is displayed when the error is encountered.
Topics
Community Discussion
No community discussion yet for this question.