Linux NFS Troubleshooting: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 73: Line 73:
</pre>
</pre>


This error means that the NFS client host is not getting a TCP/IP ACK back from the NFS server. <font color=red>The problem may be related to [[iptables]] configuration and/or [[SELinux]] configuration.</tt>
This error means that the NFS client host is not getting a TCP/IP ACK back from the NFS server. <font color=red>The problem may be related to [[iptables]] configuration and/or [[selinux|SELinux]] configuration.</tt>

Revision as of 08:03, 21 August 2016

Internal

List Filesystems Exported by a NFS Server

exportfs: list filesystems exported by a NFS server

Verbose mount

Try to mount with -v (verbose)

Other Useful Commands

showmount

showmount -e

on the server to see what is exported.

rpcinfo

rpcinfo

exportfs

exportfs

Failures

mount hangs

I've seen cases when trying to mount a filesystem from other machine hangs if nfs is not started on that machine (service nfs start).

mount.nfs: access denied by server while mounting

I've also seen cases when I get the following error message when not using -t nfs, so use -t nfs:

mount.nfs: access denied by server while mounting f01:/opt/shared

mount(2): No such file or directory

mount -v yields:

mount.nfs: trying text-based options 'bg,vers=4,addr=172.31.20.184,clientaddr=172.31.21.24'
mount.nfs: mount(2): No such file or directory
...

I get this because I use the wrong exported path in /etc/fstab.

mount(2): No route to host

mount -v yields:

mount -v -t nfs 192.168.1.2:/volume3/dropbox /mnt/tmp
mount.nfs: timeout set for Sun Aug 21 00:44:48 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.2,clientaddr=192.168.1.9'
mount.nfs: mount(2): No route to host

This error means that the NFS client host is not getting a TCP/IP ACK back from the NFS server. The problem may be related to iptables configuration and/or SELinux configuration.