|Summary help replacing me|
|Dedicated article for common problems and solutions.|
|NFS - Main NFS article.|
exportfs: /etc/exports:2: syntax error: bad option list
Delete all space from the option list in
mount.nfs4: No such device
Check that you have loaded the
lsmod | grep nfs
and if previous returns empty or only nfsd-stuff, do
mount.nfs4: access denied by server while mounting
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 # 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.
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"
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:
Remember to start all the services - nfsd.service rpc-idmapd.service rpc-mountd.service rpcbind.service, not just the nfsd.