path: root/nfs-utils-rdma-client.install
diff options
authorJames Harvey2015-08-02 07:53:51 +0000
committerJames Harvey2015-08-02 07:53:51 +0000
commitca076087809a9777c24a3f84f53e640a74662614 (patch)
tree73cb2fc1430d297f9b1e6e16a5134a0cc0f70cd9 /nfs-utils-rdma-client.install
Initial import
Diffstat (limited to 'nfs-utils-rdma-client.install')
1 files changed, 26 insertions, 0 deletions
diff --git a/nfs-utils-rdma-client.install b/nfs-utils-rdma-client.install
new file mode 100755
index 00000000000..7bbca4db85e
--- /dev/null
+++ b/nfs-utils-rdma-client.install
@@ -0,0 +1,26 @@
+post_install() {
+ echo "nfs-utils-rdma-client
+ After nfs-utils-rdma-server is installed, configured, and running on the
+ server, run:
+ mount -t nfs4 -o rdma,port=<server port>,vers=4.0
+ <ip address or name>:/<share name> /<mount point>
+ server port:
+ Use the value in the server's /etc/nfs-utils-rdma-server.conf
+ (default 20049)
+ ip address or name:
+ Using an ip address is recommended, since you likely have two routes to
+ the server, this forces it to use the RDMA-capable interface.
+ NOTE: The ip address is used for basic communication. The actual file
+ data transfers happen using RDMA.
+ share name:
+ The full path of the directory shared on the server. i.e. /home/user
+ mount point:
+ The local mount point you want to use
+ NOTE: If you omit "vers=4.0", it will default to using v4.2. v4.1 and
+ v4.2 do not yet support RDMA, and you will experience undefined
+ behavior - likely the mount will look complete, but when you use
+ it (even cd or ls), the command will hang.