NFS doesn't work

From OpenVZ Virtuozzo Containers Wiki
Revision as of 21:28, 6 June 2012 by Kkeller (talk | contribs) (mention rpcbind)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

Mount hangs[edit]

Symptoms[edit]

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

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

Reasons[edit]

  • 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)

Solution[edit]

Two options are possible:

  • run lockd on the server
  • mount with nolock option

Links[edit]

Permission denied after mount[edit]

Symptoms[edit]

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

Reasons and Solution[edit]

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