• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

NFSv4 Client Shows “nobody” As Owner And Group For Mount Point (CentOS/RHEL)

by admin

The Problem

One or more NFSv4 mount points incorrectly show ownership by “nobody:nobody” instead of the correct ownership.

The Solution

This is as-designed behavior and not an O/S-related issue. Instead, this is an NFSv3 versus NFSv4 behavioral difference.

NFSv3 Behavior

In NFSv3, usernames and groupnames are mapped from the UserID (UID) and GroupID (GID) values in /etc/passwd. Remember, with NFSv3 UID and GID must be consistent across the entire client set.

If there is no local match for these UID or GID, the numeric value will be shown instead of a name.

NFSv4 Behavior

In NFSv4, the concept is user@domainname; if there is no centralized user mapping, the user will be mapped to the properties defined in /etc/idmapd.conf; by default the name nobody will be used.

Troubleshooting

1. Ensure the proper domain is in the /etc/idmapd.conf file.

2. Restart the rpcidmapd service.

# service rpcidmapd restart

3. Remount the NFSv4 file system.

# /bin/mount -o remount /nfs/mount/point

Uniform UID and GID Assignment

It is a common misconception that the UID’s and GID’s can differ when using NFSv4. The sole purpose of ID mapping is to correlate the ID to a user name and vice-versa. ID mapping is not intended to replace proper management of network-wide UID and GID values.

If the above process does not remedy the issue, clear the idmapd cache:

# /sbin/nfsidmap -c

Filed Under: CentOS/RHEL 5, CentOS/RHEL 6, Linux

Some more articles you might also be interested in …

  1. Unable To Remove Files From Directory with Error “Argument list too long”
  2. CentOS / RHEL : How to exclude kernel or other packages from getting updated using YUM Versionlock Plugin
  3. http_load Command Examples in Linux
  4. Beginners Guide to NFS in CentOS / RHEL
  5. locate: command not found
  6. expect: command not found
  7. CentOS / RHEL 7 : How to reinstall GRUB2 from rescue mode
  8. gedit: command not found
  9. conky Command Examples in Linux
  10. How to run rsyslog as a non-root user in CentOS/RHEL 7

You May Also Like

Primary Sidebar

Recent Posts

  • aws ec2: CLI for AWS EC2 (Command Examples)
  • aws cur – Create, query, and delete AWS usage report definitions (Command Examples)
  • aws configure – Manage configuration for the AWS CLI (Command Examples)
  • aws cognito-idp: Manage Amazon Cognito user pool and its users and groups using the CLI

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright