CentOS 6: Files Now Owned By Nobody:nobody

Home » CentOS » CentOS 6: Files Now Owned By Nobody:nobody
CentOS 6 Comments


We are running a cluster under CentOS 6.6. We recently attached a new NAS device, running CentOS 6.8 and rsync’d our user file system to it.
We noticed that all the files were owned by nobody (with nobody as the group). We copied over the /etc/passwd and /etc/group files from our front-end server to our NAS server. If we log in to the NAS server we see the files owned by their correct owners. However, doing an ls from the front-end server or any of the compute nodes still shows the files owned by “nobody”. We rebooted one of the compute nodes but it still sees the files owned by nobody.

Any advice would be greatly appreciated.


6 thoughts on - CentOS 6: Files Now Owned By Nobody:nobody

  • a CentOS server isn’t really a ‘NAS device’, as NAS implies an appliance storage device.

    this is NFS? NFSv3, or NFSv4? what NFS options are on the server and on the NFS mount? quite often NFS servers force root to nobody.

  • Here are my notes for dealing with this issue:

    If all users come up as nobody on a nfs mount:

    Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server

    /sbin/service rpcidmapd restart
    /sbin/service nfslock restart
    /sbin/service nfs restart

    Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server


  • If its NFSv4, then its most likely a problem with your idmapper. Make sure that the rpc.idmapd is running on your client, and that your server has appropriate ID mapping enabled.

    If its NFSv4, are you using sec=krb5*?

  • Jonathan Billings wrote:

    I gather other folks have been saying to fix Domain =, and make sure Method = nsswitch is not commented out, in /etc/idmapd.conf. Other things:
    1. *also* in /etc/idmapd.conf, go further down, and comment out or
    delete the *other* schema – for example, the UMICH schema is
    by default enabled, for some reason. *Definitely* disable that.
    Scroll to the bottom of the file, to make sure nothing else is
    on by default.
    2. nsswitch – check /etc/nsswitch.conf

    Then restart idmapd.