Using Linux NFS with Other OSes

Linux NFS-HOWTO
Prev |  |

# 8. Using Linux NFS with Other OSes

Every operating system, Linux included, has quirks and deviations in the behavior of its NFS implementation -- sometimes because the protocols are vague, sometimes because they leave gaping security holes. Linux will work properly with all major vendors' NFS implementations, as far as we know. However, there may be extra steps involved to make sure the two OSes are communicating clearly with one another. This section details those steps.

In general, it is highly ill-advised to attempt to use a Linux machine with a kernel before 2.2.18 as an NFS server for non-Linux clients. Implementations with older kernels may work fine as clients; however if you are using one of these kernels and get stuck, the first piece of advice we would give is to upgrade your kernel and see if the problems go away. The user-space NFS implementations also do not work well with non-Linux clients.

Following is a list of known issues for using Linux together with major operating systems.

## 8.1. AIX

### 8.1.1. Linux Clients and AIX Servers

The format for the `/etc/exports` file for our example in Section 3 is:

      /usr   slave1.foo.com:slave2.foo.com,access=slave1.foo.com:slave2.foo.com
      /home  slave1.foo.com:slave2.foo.com,rw=slave1.foo.com:slave2.foo.com

### 8.1.2. AIX clients and Linux Servers

AIX uses the file `/etc/filesystems` instead of `/etc/fstab`. A sample entry, based on the example in Section 4, looks like this:

    /mnt/home:
            dev             = "/home"
            vfs             = nfs
            nodename        = master.foo.com
            mount           = true
            options         = bg,hard,intr,rsize=1024,wsize=1024,vers=2,proto=udp
            account         = false

1. Version 4.3.2 of AIX, and possibly earlier versions as well, requires that file systems be exported with the `insecure` option, which causes NFS to listen to requests from insecure ports (i.e., ports above 1024, to which non-root users can bind). Older versions of AIX do not seem to require this.

2. AIX clients will default to mounting version 3 NFS over TCP. If your Linux server does not support this, then you may need to specify `vers=2` and/or `proto=udp` in your mount options.

3. Using netmasks in `/etc/exports` seems to sometimes cause clients to lose mounts when another client is reset. This can be fixed by listing out hosts explicitly.

4. Apparently automount in AIX 4.3.2 is rather broken.

## 8.2. BSD

### 8.2.1. BSD servers and Linux clients

BSD kernels tend to work better with larger block sizes.

### 8.2.2. Linux servers and BSD clients

Some versions of BSD may make requests to the server from insecure ports, in which case you will need to export your volumes with the `insecure` option. See the man page for exports(5) for more details.

## 8.3. Tru64 Unix

### 8.3.1. Tru64 Unix Servers and Linux Clients

In general, Tru64 Unix servers work quite smoothly with Linux clients. The format for the `/etc/exports` file for our example in Section 3 is:

    /usr         slave1.foo.com:slave2.foo.com \
         -access=slave1.foo.com:slave2.foo.com \

    /home        slave1.foo.com:slave2.foo.com \
             -rw=slave1.foo.com:slave2.foo.com \
           -root=slave1.foo.com:slave2.foo.com

(The `root` option is listed in the last entry for informational purposes only; its use is not recommended unless necessary.)

Tru64 checks the `/etc/exports` file every time there is a mount request so you do not need to run the exportfs command; in fact on many versions of Tru64 Unix the command does not exist.

### 8.3.2. Linux Servers and Tru64 Unix Clients

There are two issues to watch out for here. First, Tru64 Unix mounts using Version 3 NFS by default. You will see mount errors if your Linux server does not support Version 3 NFS. Second, in Tru64 Unix 4.x, NFS locking requests are made by `daemon`. You will therefore need to specify the `insecure_locks` option on all volumes you export to a Tru64 Unix 4.x client; see the exports man pages for details.

## 8.4. HP-UX

### 8.4.1. HP-UX Servers and Linux Clients

A sample `/etc/exports` entry on HP-UX looks like this:

    /usr -ro,access=slave1.foo.com:slave2.foo.com
    /home -rw=slave1.foo.com:slave2.fo.com:root=slave1.foo.com:slave2.foo.com

(The `root` option is listed in the last entry for informational purposes only; its use is not recommended unless necessary.)

### 8.4.2. Linux Servers and HP-UX Clients

HP-UX diskless clients will require at least a kernel version 2.2.19 (or patched 2.2.18) for device files to export correctly. Also, any exports to an HP-UX client will need to be exported with the `insecure_locks` option.

## 8.5. IRIX

### 8.5.1. IRIX Servers and Linux Clients

A sample `/etc/exports` entry on IRIX looks like this:

    /usr -ro,access=slave1.foo.com:slave2.foo.com
    /home -rw=slave1.foo.com:slave2.fo.com:root=slave1.foo.com:slave2.foo.com

(The `root` option is listed in the last entry for informational purposes only; its use is not recommended unless necessary.)

There are reportedly problems when using the nohide option on exports to linux 2.2-based systems. This problem is fixed in the 2.4 kernel. As a workaround, you can export and mount lower-down file systems separately.

As of Kernel 2.4.17, there continue to be several minor interoperability issues that may require a kernel upgrade. In particular:

- Make sure that Trond Myklebust's seekdir (or dir) kernel patch is applied. The latest version (for 2.4.17) is located at:

  http://www.fys.uio.no/~trondmy/src/2.4.17/linux-2.4.17-seekdir.dif

- IRIX servers do not always use the same `fsid` attribute field across reboots, which results in `inode number mismatch` errors on a Linux client if the mounted IRIX server reboots. A patch is available from:

  http://www.geocrawler.com/lists/3/SourceForge/789/0/7777454/

- Linux kernels v2.4.9 and above have problems reading large directories (hundreds of files) from exported IRIX XFS file systems that were made with `naming version=1`. The reason for the problem can be found at:

  http://www.geocrawler.com/archives/3/789/2001/9/100/6531172/

  The naming version can be found by using (on the IRIX server):

      	xfs_growfs -n mount_point

  The workaround is to export these file systems using the `-32bitclients` option in the `/etc/exports` file. The fix is to convert the file system to 'naming version=2'. Unfortunately the only way to do this is by a `backup`/`mkfs`/`restore`.

  mkfs_xfs on IRIX 6.5.14 (and above) creates `naming version=2` XFS file systems by default. On IRIX 6.5.5 to 6.5.13, use:

      	mkfs_xfs -n version=2 device

  Versions of IRIX prior to 6.5.5 do not support `naming version=2` XFS file systems.

### 8.5.2. IRIX clients and Linux servers

Irix versions up to 6.5.12 have problems mounting file systems exported from Linux boxes - the mount point "gets lost," e.g.,

    	# mount linux:/disk1 /mnt
    	# cd /mnt/xyz/abc
    	# pwd
    	/xyz/abc

This is known IRIX bug (SGI bug 815265 - IRIX not liking file handles of less than 32 bytes), which is fixed in IRIX 6.5.13. If it is not possible to upgrade to IRIX 6.5.13, then the unofficial workaround is to force the Linux nfsd to always use 32 byte file handles.

A number of patches exist - see:

- http://www.geocrawler.com/archives/3/789/2001/8/50/6371896/

- http://oss.sgi.com/projects/xfs/mail_archive/0110/msg00006.html

## 8.6. Solaris

### 8.6.1. Solaris Servers

Solaris has a slightly different format on the server end from other operating systems. Instead of `/etc/exports`, the configuration file is `/etc/dfs/dfstab`. Entries are of the form of a share command, where the syntax for the example in Section 3 would look like

    share -o rw=slave1,slave2 -d "Master Usr" /usr

and instead of running exportfs after editing, you run shareall.

Solaris servers are especially sensitive to packet size. If you are using a Linux client with a Solaris server, be sure to set `rsize` and `wsize` to 32768 at mount time.

Finally, there is an issue with root squashing on Solaris: root gets mapped to the user `noone`, which is not the same as the user `nobody`. If you are having trouble with file permissions as root on the client machine, be sure to check that the mapping works as you expect.

### 8.6.2. Solaris Clients

Solaris clients will regularly produce the following message:

    svc: unknown program 100227 (me 100003)

This happens because Solaris clients, when they mount, try to obtain ACL information - which Linux obviously does not have. The messages can safely be ignored.

There are two known issues with diskless Solaris clients: First, a kernel version of at least 2.2.19 is needed to get `/dev/null` to export correctly. Second, the packet size may need to be set extremely small (i.e., 1024) on diskless sparc clients because the clients do not know how to assemble packets in reverse order. This can be done from `/etc/bootparams` on the clients.

## 8.7. SunOS

SunOS only has NFS Version 2 over UDP.

### 8.7.1. SunOS Servers

On the server end, SunOS uses the most traditional format for its `/etc/exports` file. The example in Section 3 would look like:

    /usr    -access=slave1.foo.com,slave2.foo.com
    /home   -rw=slave1.foo.com,slave2.foo.com, root=slave1.foo.com,slave2.foo.com

Again, the `root` option is listed for informational purposes and is not recommended unless necessary.

### 8.7.2. SunOS Clients

Be advised that SunOS makes all NFS locking requests as `daemon`, and therefore you will need to add the `insecure_locks` option to any volumes you export to a SunOS machine. See the exports man page for details.

Prev | Home |
Troubleshooting |  |