Difference between revisions of "NFS doesn't work"
(other reasons why nfs might not work) |
|||
| Line 24: | Line 24: | ||
=== Links === | === Links === | ||
* {{Bug|620}} | * {{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]] | [[Category:Troubleshooting]] | ||
Revision as of 16:26, 27 April 2011
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 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
Links
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
sec=systo use the system mount option [1]
