NFS/Troubleshooting

From ArchWiki
Revision as of 10:53, 10 December 2012 by Giddie (Talk | contribs) (Doing some tidying up; mostly just moving around and new headings.)

Jump to: navigation, search
Summary help replacing me
Dedicated article for common problems and solutions.
Related
NFS - Main NFS article.

Server Configuration Issues

exportfs: /etc/exports:2: syntax error: bad option list

Delete all space from the option list in /etc/exports

Group/gid permissions issues

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"

Client Configuration Issues

mount.nfs4: No such device

Check that you have loaded the nfs module

lsmod | grep nfs

and if previous returns empty or only nfsd-stuff, do

modprobe nfs

mount.nfs4: access denied by server while mounting

Check that the permissions on your client's folder are correct. Try using 755.

Lock problems

If you got error such as this:

mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

To fix this, you need to change the "NEED_STATD" value in /etc/conf.d/nfs-common.conf to YES.

Remember to start all the required services (see NFS or NFSv3), not just the nfs service.

Other Issues

Permissions Issues

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 all your files are owned by nobody, and you are using NFSv4, on both the client and server, you should:

  • For initscripts, ensure that NEED_IDMAPD is set to YES in /etc/conf.d/nfs-common.conf.
  • For systemd, ensure that the rpc-idmapd service has been started.