Difference between revisions of "NFS doesn't work"
Botinki Kira (talk | contribs) m (Robot: Automated text replacement (-VE +container)) |
(other reasons why nfs might not work) |
||
| Line 5: | Line 5: | ||
=== Symptoms === | === Symptoms === | ||
| − | <tt>mount</tt> command hangs: | + | <tt>mount</tt> command hangs or takes a very long time to complete: |
| + | |||
<pre> | <pre> | ||
# mount <ip address>:/pub /data | # mount <ip address>:/pub /data | ||
| Line 11: | Line 12: | ||
</pre> | </pre> | ||
| − | === | + | === Reasons === |
| − | Lockd is not running on the NFS server. | + | * 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 === | === Solution === | ||
Revision as of 11:29, 10 February 2009
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
[hide]Mount hangs
Symptoms
mount command hangs or takes a very long time to complete:
# mount <ip address>:/pub /data (...hangs here...)
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 lockd on the server
- mount with nolock option
