This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs.

`fs-nfs3`

NFS 3 client filesystem (QNX Neutrino)

You must be root to start this manager.

Syntax:

fs-nfs3 [-b num] [-B size] [-D] [-e] [-h] 
        [-i nodes] [-r] [-S] [-t] 
        [-u] [-v[v]...] [-w sync=hard] 
        [-Z n] server:export mountpoint
        [[-erStu] [-Z n] server:export mountpoint ...]

Options:

server: The name of the NFS server.
export: The directory to be exported from the server.
mountpoint: The name under which the exported directory is to be mounted.

The following options apply to all mountpoints:

-b num: Use num buffers (default: 200).
-B size: Set the buffer size to size bytes. The default is set by the first server, and is usually 8K.
-D: Run in the foreground.
-h: Display usage information.
-i nodes: Set the number of inodes to nodes.
-v[v]...: Verbose output; add more v characters for more verbosity. In order to capture the log messages, you need to have syslogd running.

The following options apply only to the next mountpoint specified on the command line:

-e

Set the NO EXEC flag for the mounted filesystem.

-r

Set the READ ONLY flag for the mounted filesystem.

-S

Don't cache symlinks.

-t

Use TCP instead of UDP. If this fails, fs-nfs3 uses UDP.

-u

Use UDP (which is the default). If this fails, fs-nfs3 fails.

-w sync=hard

Turn off write caching.

-Z n

The value of n indicates how to attach to the path:

B or b -- attach before other managers.
A or a -- attach after other managers.
O or o -- make the attachment opaque; don't resolve to mountpoints with shorter pathname matches. The pathname resolver tries to find the longest match against all pathnames attached.

The default is none of these.

Description:

The fs-nfs3 filesystem manager is an NFS 3 client operating over TCP/IP. To use it, you must have an NFS server.

When you use fs-nfs3 with write caching (default), you achieve performance enhancements with respect to interoperability issues if more than one client accesses the same files on the server. You may use -w sync=hard to turn off write caching.

This filesystem manager requires a TCP/IP transport layer, such as the one provided by io-net with the npm-tcpip.so. It also needs socket.so and libc.so.

By default, this utility does not set any upper limit for number of inodes.

You can also create mountpoints with the mount command by specifying nfs for the type and -o ver3 as an option. You must start fs-nfs3 before creating mountpoints in this manner. If you start fs-nfs3 without any arguments, it runs in the background so you can use mount. The options that you can use with mount include the following:

tcp: Use TCP instead of UDP. If this fails, mount uses UDP.
udp: Use UDP (which is the default). If this fails, mount fails.
nocachesymlink: Don't cache symlinks.
ver3: Use fs-nfs3 instead of fs-nfs2.
soft: Use a soft mount (i.e. break the connection if unable to reach the server).

Examples:

Mount the qnx_bin export as /bin from an NFS server named server_node:

fs-nfs3 server_node:/qnx_bin /bin &

Mount /nfs1 using TCP, and /nfs3 using UDP:

fs-nfs3 -t host1:/ /nfs1 host2:/ /nfs3

Mount both using TCP:

fs-nfs3 -t host1:/ /nfs1 -t host2:/ /nfs3

Mount an NFS filesystem (fs-nfs3 must be running first):

mount -t nfs -o ver3 server_node:/qnx_bin /bin

Mount an NFS filesystem, using TCP (fs-nfs3 must be running first):

mount -t nfs -o tcp,ver3 server:/tmp /mnt

Files:

io-net: Networking I/O manager.
npm-tcpip.so: Full TCP/IP stack.
npm-ttcpip.so: Tiny TCP/IP stack.

Caveats:

If possible, you should use fs-nfs3 instead of fs-nfs2.