Changes
NFS
,no edit summary
== Mounting NFS ==
Make sure that packages <code>nfs-utils</code> and <code>nfs-utils-lib</code> or similar are installed in a container. Also make sure that the <code>portmap</code> (or <code>rpcbind</code>) service is started, otherwise the mount with default options will fail and require the <code>-nolock</code> option.<ref>For Ubuntu/Debian OpenVZ containers, See the portmap/rpcbind service do not start automatically[[NFS#Known issues|known issues]] for more information. However, you can enable it by editing the <code>/etc/default/nfs-common</code> configuration file.</ref>
Assuming that you already have NFS server set up at <code>192.168.0.1:/nfs_pub</code>, mounting will be simple
* There are quite a few parameters in NFS, so sometimes it doesn't work due to misconfiguration. We've created a separate page describing such situations: [[NFS doesn't work]].
* Package nfs-common can not be installed. Make sure you start <code>portmap</code> before trying to install nfs-common.
** For Ubuntu/Debian OpenVZ containers, the <code>portmap/rpcbind</code> service may not start automatically. However, you can enable it by editing the <code>/etc/default/nfs-common</code> configuration file.
== See also ==
* [http://nfs.sourceforge.net/nfs-howto/ar01s04.html NFS-client HOWTO]
[[Category: HOWTO]]