Skip to main content

Issue with idmappings between NFS server and client

  • Updated
We moved this page to our Documentation Portal. You can find the latest updates here.

Issue

Customers using NFS 4 share may experience issues with idmappings between NFS server and client.

 

Resolution

Use one of the following workarounds to fix this problem:

  1. Switch to the NFSv3.
  2. Make sure that both NFS servers have the same domain name. To check this, run the  following command: # dnsdomainname
  3. Also, if you are using NFSv4, open the /etc/idmap.conf file and make the following changes:
    Uncomment and set "Domain variable from "Global" section. For example, set NFS domain to onapp:

     
    [General]
    #Verbosity = 0
    # The following should be set to the local NFSv4 domain name
    # The default is the host's DNS domain name.
    Domain = onapp
  4. If you are not using a dedicated backup server in your cloud setup, configure NFS server with the following options to preserve files owner and group settings during template unpacking on NFS storage, as not doing so can lead to permissions errors during provisioning:  
    • no_root_squash
    • no_all_squash