NFS doesn't work

Often NFS in container does not work because of misconfiguration. This article contains known reasons of such problems as well as solutions for those.

Contents

Mount hangsEdit

SymptomsEdit

mount command hangs or takes a very long time to complete:

# mount <ip address>:/pub /data
(...hangs here...)

ReasonsEdit

• Lockd is not running on the NFS server
• Portmap (older) or rpcbind (newer) is not running on the NFS client
• Networking is broken (e.g. scripts brought up default route but not IP address yet)

SolutionEdit

Two options are possible:

• run lockd on the server
• mount with nolock option

LinksEdit

• OpenVZ Bug #620

Permission denied after mountEdit

SymptomsEdit

After a successful mount it is not possible to enter the mounted directory.

Reasons and SolutionEdit

• Possible the wrong authentification method for NFS is used. Try to add the mount option sec=sys to use the system mount option [1]