Editing NFS doesn't work

Often NFS in VE doesn't work because off misconfiguration. 
This article contents known reasons of NFS related problems, that are not bugs,
but misconfigurations.

== Reason #1 ==
===  Symptomps ===
<tt>mount</tt>  command hangs:
<pre>
# mount <ip address>:/pub /data
(...hangs here...)
</pre>

=== Reason ===
Lockd is not running on the NFS server

=== Workaround ===
* run <tt>lockd</tt> on the server
* mount with <tt>nolock</tt> option

=== Links ===
* http://bugzilla.openvz.org/show_bug.cgi?id=620

[[Category:Troubleshooting]]
@@ Line 1: / Line 1: @@
-Often [[NFS]] in container does not work because of misconfiguration.
+Often NFS in VE doesn't work because off misconfiguration.
-This article contains known reasons of such problems as well as solutions for those.
+This article contents known reasons of NFS related problems, that are not bugs,
+but misconfigurations.
-== Mount hangs ==
-===  Symptoms ===
-<tt>mount</tt>  command hangs or takes a very long time to complete:
+== Reason #1 ==
+===  Symptomps ===
+<tt>mount</tt>  command hangs:
 <pre>
 # mount <ip address>:/pub /data
@@ Line 12: / Line 11: @@
 </pre>
-=== Reasons ===
+=== Reason ===
-* Lockd is not running on the NFS server
+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 ===
+=== Workaround ===
-Two options are possible:
 * run <tt>lockd</tt> on the server
 * mount with <tt>nolock</tt> option
 === Links ===
-* {{Bug|620}}
+* http://bugzilla.openvz.org/show_bug.cgi?id=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]]