NFSv4, Network File System version 4, is the new version of NFS (for setting up the older NFSv3, see Nfs) with new features like strong authentication and integrity via Kerberos and SPKM-3, improved performance, safe file caching, lock migration, UTF-8, ACLs and better support for Windows file sharing semantics.
This article covers installing and configuring NFSv4.
Both client and servers require the nfs-utils package. Install nfs-utils with pacman.
The server configuration is very thorough.
First, we will need to edit our exports in /etc/exports
.
A typical NFSv4 export would look like this:
/export 192.168.0.12(rw,fsid=0,no_subtree_check,async,no_root_squash) /export/music 192.168.0.12(rw,no_subtree_check,async,no_root_squash)
/export
is the NFS root here (due to the fsid=0
entry). Everything else that you want to be shared over NFS must be accessible under /export
.
For exporting directories outside the NFS root, see below.
To do this, you will need to use bind mounts. For example, to bind /home/john
to /export/john
:
# mount --bind /home/john /export/john
Then, /export/john
needs to be added to /etc/exports
:
/export 192.168.0.12(rw,fsid=0,no_subtree_check,async,no_root_squash) /export/music 192.168.0.12(rw,no_subtree_check,async,no_root_squash) /export/john 192.168.0.12(rw,no_subtree_check,async,no_root_squash,nohide)
The nohide
option is required, because the kernel NFS server automatically hides mounted directories.
To add the bind mount to /etc/fstab
:
/home/john /export/john none bind 0 0
Then, /etc/idmapd.conf
needs to be edited. You'll need to at the very least specify your Domain there. Example:
[General] Verbosity = 1 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = archlinux.org [Mapping] Nobody-User = nobody Nobody-Group = nobody
To start the NFS server, just do:
# rc.d start rpcbind nfs-common nfs-server
If you want to tweak the configuration, feel free to edit /etc/conf.d/nfs-server.conf
to fit your needs.
The client configuration is more simple.
/etc/idmapd.conf
needs to be edited on all clients and the Domain entry should be identical to the one on the server. Example:
[General] Verbosity = 1 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = archlinux.org [Mapping] Nobody-User = nobody Nobody-Group = nobody [Translation] Method = nsswitch
On the client, to mount the NFSv4 partition: Make sure that nfs module is loaded. (lsmod | grep nfs). If not execute the next command "modprobe nfs"
# /etc/rc.d/rpcbind start # /etc/rc.d/nfs-common start # mount -t nfs4 server:/ /mnt/server/ # mount -t nfs4 server:/music /mnt/music/ # mount -t nfs4 server:/john /mnt/john
Replacing 'server' with the hostname or IP address of your NFS server and of course 'server', 'music' and 'john' with the names of whatever directories you exported on the server.
If you want the NFS volumes to mount automatically on bootup, add them to fstab
. For example:
server: /mnt/server nfs4 async,user 0 0
Remember to add netfs in the daemons array at /etc/rc.conf in order to mount nfs volumes at boot.
In order for NFS to function properly, both server and client must have closely matching time values. If the clocks on the clients differ from the server too much, then basic functions like file copy operations may hang for a very long time leaving the system unusable until they resume. The clocks do not have to match to micro/nano second accuracies, but ideally they should be within 1 second of each other.
The NTP system is recommended to sync both the server and the clients to the highly accurate NTP servers available on the Internet. For a small system like a home network, the ntpdate utility may be used to sync both servers and clients to the same time. For a larger installation, it may be desirable to install an OpenNTP server (see NTP) onto the same machine acting as the NFS server, and then all clients on the network would sync time values from the server. This has the advantage of lowering the stress on the external NTP servers, and in assuring that the NFS clients will use the exact time that the NFS server has, even if the NFS server experiences some drift.
Add nfsd
to /etc/rc.conf
's MODULES array.
Delete all space from the option list in /etc/exports
Check that you have loaded the nfs
module
lsmod | grep nfs
and if previous returns empty or only nfsd-stuff, do
modprobe nfs
Check that the permissions on your client's folder are correct. Try using 755.
If you find that you cannot set the permissions on files properly, make sure the user/group you are chowning are on both the client and server.
If that does not help, try modifying these lines in /etc/conf.d/nfs-common.conf
# /etc/conf.d/nfs-common.conf # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD="no" # Do you want to start the idmapd daemon? It is only needed for NFSv4. NEED_IDMAPD="yes"
Restart the nfs-common daemon for the changes to take effect. I restarted all the other daemons as well, just to be sure.
If NFS shares mount fine, and are fully accessible to the owner, but not to group members; check the number of groups that user belongs to. NFS has a limit of 16 on the number of groups a user can belong to. If you have users with more then this, you need to enable the --manage-gids
start-up flag for rpc.mountd
on the NFS server.
/etc/conf.d/nfs-server.conf # Options for rpc.mountd. # If you have a port-based firewall, you might want to set up # a fixed port here using the --port option. # See rpc.mountd(8) for more details. MOUNTD_OPTS="--manage-gids"
联系客服