Troubleshooting NFS servers

OMFG, NFS servers are SUCH a pain in the backside.  But anyway, here are some useful tricks:

On server:
   netstat -l
lists which services are listening on which port.

   rpcinfo -p
also lists rpc processes, with program numbers and ports

   /etc/services
The file portmapper uses to see which port the services should run on.  Names of the relevant services are: mountd lockd and status

HOWEVER:
   sysctl -w fs.nfs.nlm_tcpport=blah
   sysctl -w fs.nfs.nlm_udpport=blah
might be needed to set the port of nlockmgr.  Why it doesn't listen to portmapper, I've no idea.

Debug logs:
   - kill the server process (nfsd, mountd, or whichever)
   - run the server process with a -F or without the -D to force it to run in the foreground (you also might have to include a debug or verbose mode option.
   - try to mount the nfs share from the client.  Now you should get a load of meaningful output on the command line.

If you're dealing with TinyCore, REMEMBER TO filetool.sh -b BEFORE REBOOTING!

On client:
  mount.nfs -v
Useful verbose output

  mount.nfs ..... -o vers=3
If you're not having any luck, try mounting with nfs version 3.  Long shot, but you never know...

Comments

Popular posts from this blog

Micro:Bit and SPI display

DCS World with TrackIR under Ubuntu

Cardboard Mock-up of USB Joystick