Editing 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.

== Mount hangs ==

===  Symptoms ===
<tt>mount</tt>  command hangs or takes a very long time to complete:

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

=== Reasons ===
* Lockd is not running on the NFS server
* Portmap is not running on the NFS client
* Networking is broken (e.g. scripts brought up default route but not IP address yet)

=== Solution ===
Two options are possible:
* run <tt>lockd</tt> on the server
* mount with <tt>nolock</tt> option

=== Links ===
* {{Bug|620}}

== Permission denied after mount ==

===  Symptoms ===

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

=== Reasons and Solution ===

* Possible the wrong authentification method for NFS is used. Try to add the mount option <code>sec=sys</code> to use the system mount option [http://workaround.org/node/265]


[[Category:Troubleshooting]]