Difference between revisions of "NFSv4"

From ArchWiki
Jump to navigation Jump to search
(Goals)
m (Exports)
Line 22: Line 22:
 
A typical NFSv4 export would look like this:
 
A typical NFSv4 export would look like this:
 
  /export    *(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
 
  /export    *(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
  /export/music *(rw,async)
+
  /export/music 192.168.0.12(rw,async)
 
/export is the NFS root here (specifying multiple NFSv4 roots seems impossible; you will need to do something with bind mounts if you want to export directories that are not under the NFS root) and everything else has to be placed under /export.
 
/export is the NFS root here (specifying multiple NFSv4 roots seems impossible; you will need to do something with bind mounts if you want to export directories that are not under the NFS root) and everything else has to be placed under /export.
  

Revision as of 11:45, 6 November 2007



Goals

The goal of this article is getting NFSv4 running on ArchLinux.
NFSv4 is the new version of NFS with new features like strong authentication and integrity via Kerberos and SPKM-3, improved performance, safe file caching, lock migration, ACLs and better support for Windows file sharing semantics.

Required packages

Required packages for both client and server (from AUR):

  1. libgssglue
  2. librpcsecgss
  3. nfs4-utils

Download the packages, makepkg and install them.
Note: currently pacman doesn't seem to handle replacing when invoked with pacman -U. Therefore, you'll need to remove nfs-utils before installing nfs4-utils (which is a complete drop-in replacement).

Exports

First we'll need to edit our exports in /etc/exports. A typical NFSv4 export would look like this:

/export    *(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
/export/music 192.168.0.12(rw,async)

/export is the NFS root here (specifying multiple NFSv4 roots seems impossible; you will need to do something with bind mounts if you want to export directories that are not under the NFS root) and everything else has to be placed under /export.

Then, /etc/idmapd.conf needs to be edited. You'll need to specify the Domain there on both client and server, so that they are identical.

Starting the server

To start the NFS server, just

/etc/rc.d/nfsd start
/etc/rc.d/nfs4-common start

If you want to tweak the configuration, feel free to edit /etc/conf.d/nfs to your needs.

Mounting the partitions on the client

On the client, to mount the NFSv4 partition:

/etc/rc.d/nfs4-common start
mount -t nfs4 server:/ /mnt/server/
mount -t nfs4 server:/music /mnt/music/

Note that the root of the path on the server is the NFS root specified; all paths must be specified relative to that.

See also

Take a look at the gentoo wiki for further instructions on configuring the exports.
Some general instructions: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
On migrating from NFSv3 to NFSv4: http://nfsv4.bullopensource.org/tools/tests/page40.php
For NFSv4 with Kerberos authentication: http://www.itp.uzh.ch/~dpotter/howto/kerberos