Sharing the File System With NFS Client Systems

This section describes how to share the file system with network file system (NFS) clients.

Some NFS mount parameters can affect the performance of an NFS-mounted Sun Storage Archive Manager file system. You can set these parameters in the /etc/vfstab file as follows:

timeo = n. This value sets the NFS timeout to n tenths of a second. The default is eleven tenths of a second. For performance purposes, use the default value. You can increase or decrease the value appropriately for your system.
rsize = n. This value sets the read buffer size to n bytes. In NFS 2, change the default value (8192) to 32768. In NFS 3, retain the default value of 32768.
wsize = n. This value sets the write buffer size to n bytes. In NFS 2, change the default value (8192) to 32768. In NFS 3, retain the default value of 32768. For more information about these parameters, see the mount_nfs(1M) man page.

How to NFS Share the File System

This procedure uses the Oracle Solaris share command to make the file system available for mounting by remote systems. The share commands are typically placed in the /etc/dfs/dfstab file and are executed automatically by the Oracle Solaris OS when you enter init state 3.

Add a share command to the /etc/dfs/dfstab file.

For example:

# share -F nfs -o rw=client1:client2 -d "SAM-FS" /samfs1

Use the ps command to determine whether nfs.server is running.

For example:

# ps -ef | grep nfsd
    root   694     1  0   Apr 29 ?        0:36 /usr/lib/nfs/nfsd -a 16
en17     29996 29940  0 08:27:09 pts/5    0:00 grep nfsd
# ps -ef | grep mountd
    root   406     1  0   Apr 29 ?       95:48 /usr/lib/autofs/automountd
    root   691     1  0   Apr 29 ?        2:00 /usr/lib/nfs/mountd
en17     29998 29940  0 08:27:28 pts/5    0:00 grep mountd

In this sample output, the lines that contain /usr/lib/nfs indicate that the NFS server is mounted.

If nfs.server is not running, start it:
```
# svcadm enable nfs/server
```
(Optional) . If you want to NFS-share the file system immediately, type the share command at a root shell prompt.
If no NFS-shared file systems exist when the Oracle Solaris OS boots, the NFS server is not started.
The following example shows the commands to use to enable NFS sharing. You must change to run level 3 after adding the first share entry to this file.
```
# init 3
# who -r
.       run-level 3  Dec 12 14:39     3    2  2
# share
-          /samfs1  -   "SAM-FS"
```

How to Mount the File System on Clients

On the client systems, mount the server's file system at a convenient mount point.

Note - There can be a significant delay in the file system's response to NFS client requests if a requested file resides on a cartridge that must be loaded into a DLT tape drive, if all tape drives are full, or if drives are slow. As a consequence, the system might generate an error instead of retrying the operation. To avoid this situation, it is recommended that you mount the file system with either the hard option enabled or with the soft, retrans, and timeo options enabled. If you use the soft option, also specify retrans=120 (or greater) and timeo=3000.

On an NFS client system, add a line to the /etc/vfstab file to mount the server's file system at a convenient mount point.
The following example mounts server:/samfs1 on the /samfs1 mount point:
```
server:/samfs1   -   /samfs1   nfs -      yes   hard,intr,timeo=60
```
Save and close the /etc/vfstab file.
Issue the mount command.
For example, the following mount command mounts the samfs1 file system:
```
# mount /samfs1
```
Alternatively, the automounter can do this, if you prefer. Follow your site procedures for adding server :/samfs1 to your automounter maps. For more information, see the automountd(1M) man page.

Skip Navigation Links
Exit Print View
	Sun Storage Archive Manager 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library