NFS - Revision history

Kir: /* Prepare the HN */

2016-06-17T19:34:29Z

‎Prepare the HN

2016-06-17T12:58:31Z

2013-02-25T16:07:35Z

2013-02-25T14:35:08Z

‎See also

2013-02-25T14:34:27Z

‎Mounting NFS: added portmap entry

2013-02-23T11:51:48Z

‎Prepare the container

2013-02-23T11:48:59Z

‎Prepare the container

2011-08-06T16:19:21Z

‎Prepare the HN: other way of loading the module on boot

2011-06-07T13:29:51Z

Bind mounts

2011-05-04T19:49:48Z

‎Known issues

@@ Line 25: / Line 25: @@
 RHEL7-based kernels support [https://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html three different NFS protocol versions]:
-<pre>
+{{Quote|
 NFS version 2 (NFSv2) is older and is widely supported.
 NFS version 3 (NFSv3) has more features, including 64bit file handles, Safe Async writes and more robust error handling.
 NFS version 4 (NFSv4) works through firewalls and on the Internet, no longer requires portmapper, supports ACLs, and utilizes stateful operations.
 Red Hat Enterprise Linux supports NFSv2, NFSv3, and NFSv4 clients, and when mounting a file system via NFS, Red Hat Enterprise Linux uses NFSv3 by default, if the server supports it.
-</pre>
+}}
-There are three kernel modules accordingly: <code>nfs</code> (for NFSv2), <code>nfsv3</code>, <code>nfsv4</code>. As [[NFS server inside container]] by this moment supports only NFSv3, it's very likely that you'll need to load <code>nfsv3</code> module for clients.
   # modprobe nfs

← Older revision		Revision as of 12:58, 17 June 2016
Line 23:		Line 23:

	For NFS mounts to work in the containers with the RHEL5-based kernels you must enable kernel threads in the container by setting <code>kernel.ve_allow_kthreads=1</code> in <code>/etc/sysctl.conf</code>.		For NFS mounts to work in the containers with the RHEL5-based kernels you must enable kernel threads in the container by setting <code>kernel.ve_allow_kthreads=1</code> in <code>/etc/sysctl.conf</code>.
		+
		+	RHEL7-based kernels support [https://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html three different NFS protocol versions]:
		+	<pre>
		+	NFS version 2 (NFSv2) is older and is widely supported.
		+	NFS version 3 (NFSv3) has more features, including 64bit file handles, Safe Async writes and more robust error handling.
		+	NFS version 4 (NFSv4) works through firewalls and on the Internet, no longer requires portmapper, supports ACLs, and utilizes stateful operations.
		+	Red Hat Enterprise Linux supports NFSv2, NFSv3, and NFSv4 clients, and when mounting a file system via NFS, Red Hat Enterprise Linux uses NFSv3 by default, if the server supports it.
		+	</pre>
		+	There are three kernel modules accordingly: <code>nfs</code> (for NFSv2), <code>nfsv3</code>, <code>nfsv4</code>. As [[NFS server inside container]] by this moment supports only NFSv3, it's very likely that you'll need to load <code>nfsv3</code> module for clients.

	# modprobe nfs		# modprobe nfs

@@ Line 52: / Line 52: @@
 == 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, the portmap/rpcbind service do not start automatically. However, you can enable it by editing the <code>/etc/default/nfs-common</code> configuration file.</ref>
+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.  See the [[NFS#Known issues|known issues]] for more information.
 Assuming that you already have NFS server set up at <code>192.168.0.1:/nfs_pub</code>, mounting will be simple
@@ Line 72: / Line 72: @@
 * 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.
 == See also ==
 * [http://nfs.sourceforge.net/nfs-howto/ar01s04.html NFS-client HOWTO]
 [[Category: HOWTO]]

@@ Line 75: / Line 75: @@
 == See also ==
 * [http://nfs.sourceforge.net/nfs-howto/ar01s04.html NFS-client HOWTO]
 [[Category: HOWTO]]

@@ Line 52: / Line 52: @@
 == Mounting NFS ==
-Make sure that packages <code>nfs-utils</code> and <code>nfs-utils-lib</code> or similar are installed in a container.
+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, the portmap/rpcbind service do not start automatically. 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

@@ Line 35: / Line 35: @@
 To allow a container to use NFS filesystem, you will need to start it with "nfs" feature enabled. If the container is running while you set the <code>--features nfs:on</code>, you will need to reboot it.
-  # vzctl set 101 --features "nfs:on nfsd:on" --save
+  # vzctl set 101 --features "nfs:on" --save
   # vzctl start 101

← Older revision		Revision as of 16:19, 6 August 2011
Line 29:		Line 29:

	modprobe nfs		modprobe nfs
		+
		+	Alternatively, you can add a new line with <code>nfs</code> to your /etc/modules or /etc/modules.conf file.

	=== Prepare the container ===		=== Prepare the container ===

@@ Line 1: / Line 1: @@
 This page describes how to use '''NFS client''' inside a container.
-{{Note|see [[NFS server inside container]] for info about nfsd.}}
+{{Note|see [[NFS server inside container]] for info about nfsd.
 == Preparations ==