NFS Services Administrator's Guide

Configuring and Administering NFS Services
Configuring and Administering NFS Clients
Chapter 282
• Mounting an NFS Version 2 filesystem using the UDP Transport
mount -o vers=2,proto=udp onc21:/var/mail /var/mail
In this example, the NFS client mounts the /var/mail directory
from the NFS server, onc21, using NFSv2 and the UDP protocol.
• Mounting an NFS filesystem using an NFS URL
mount nfs://onc31/Casey/mail /Casey/mail
In this example, the NFS client mounts the /Casey/mail directory
from NFS server, onc31, using the WebNFS protocol.
• Mounting an NFS filesystem by using a public file handle
mount -o public nfs://onc31/usr/%A0abc /Casey/Clay
If the public option or a URL is specified, the mount command
attempts to connect to the server using the public file handle. The
daemons rpcbind and mountd are not contacted.
In this example, the NFS client mounts /Casey/Clay directory by
using a public file handle, and an NFS URL that has a non 7-bit
ASCII escape sequence from the NFS server, onc31.
• Mounting an NFS filesystem using native path
mount -o public onc31:C:Casey:test1 /Casey/test
A native path is a pathname that is interpreted according to
conventions used on the native operating system of the NFS server.
In this example, the NFS client mounts the /Casey/test directory
using a native path and a public file handle.
• Mounting a replicated set of NFS filesystems with same pathnames
mount -r onc21,onc23,onc25:/Casey/Clay /Casey/Clay
In this example, the NFS client mounts a single filesystem,
/Casey/Clay that has been replicated to a number of servers with
the same pathnames. This enables the NFS client to failover to
either server onc21, onc23, or onc25 if the current server has
become unavailable.
• Mounting replicated set of NFS file systems with different
pathnames
mount -r onc21:/Casey/Clay,onc23:/Var/Clay,nfs://srv-z/Clay
/Casey/Clay