| View previous topic :: View next topic |
| Author |
Message |
Kate Monster
Apprentice
Joined: 13 Jun 2006
Posts: 226
Location: Clarkston, Michigan
|
 Posted: Fri May 04, 2007 5:39 am Post subject: |
 |
|
| Truin wrote: | | Also, make sure that portmap is running on the client side. |
ahh, that was it, didn't know portmap had to be started. thanks!  |
|
| Back to top |
|
 |
mikers456
n00b
Joined: 07 Jul 2004
Posts: 36
|
| Posted: Fri Jun 29, 2007 5:52 pm Post subject: |
|
|
For crashes or hangs, resulting in an "undead" nfs server (nfsd or other processes can't be killed), can't mount or unmount nfs from client side, etc.
I found that reducing the size of wsize or rsize options in your fstab (client side NFS mount options) helped. The NFS manual recommends that you reduce the size to 1024 and increase slowly while testing for each increase. The manual also recommends not making your wsize, rsize bigger than MTU on network. Also some network switches or routers cannot handle large packets -- check that your switch can support the packet size you are using.
Turns out with large wsize or rsize, udp packet fragmentation can either (a) overload your network card driver/kernel or (b) switch/router on network... I was seeing hard nfs server side lockups.
Use "nfsstat -o all" on client to see number of re-transmissions from client side. If excessively high (eg. > 5%) consider lowering the wsize, rsize options. |
|
| Back to top |
|
|
will824
n00b
Joined: 03 Jul 2003
Posts: 16
Location: Medellin, Colombia
|
| Posted: Sat Jun 30, 2007 7:47 am Post subject: Really usefull! |
|
|
Thanks for this Guide, it was really useful for me, as I am still learning 
_________________
--
Will |
|
| Back to top |
|
|
SkyLine
n00b
Joined: 11 Oct 2006
Posts: 36
|
| Posted: Tue Jan 08, 2008 10:15 am Post subject: |
|
|
On client side
| Code: |
/etc/init.d/nfs start
|
and
| Code: |
rc-update add nfs default
|
not needed.
Only start nfsmount
| Code: |
/etc/init.d/nfsmount start
|
and
| Code: |
rc-update add nfsmout start
|
|
|
| Back to top |
|
|
RayDar
n00b
Joined: 16 Apr 2008
Posts: 3
|
| Posted: Wed Apr 16, 2008 4:17 am Post subject: Re: Howto: NFS Server and Client |
|
|
| deffe wrote: |
The NFS daemon is required on the client:
| Code: |
# /etc/init.d/nfs start
# rc-update add nfs default
|
|
When I tried this, my machine would freeze at "Starting NFS statd ..." for a few minutes before reporting the following error: ERROR: cannot start nfs as rpc.statd could not start
An ifconfig /a revealed that my "lo" interface didn't have an IP address of 127.0.0.1
This was fixed by starting the net.lo
| Code: |
/etc/init.d/net.lo start
|
Of course, I added it to my startup.
| Code: |
rc-update add net.lo default
|
|
|
| Back to top |
|
|
diablo465
Apprentice
Joined: 10 Sep 2013
Posts: 194
|
| Posted: Mon Jul 21, 2014 1:54 am Post subject: |
|
|
Thanks for the post, but I don't know how to use nfs-server in a system with systemd:
| Code: | systemctl enable nfs-server
Failed to execute operation: No such file or directory |
| Code: | ae429-1105 linux # /etc/init.d/nfs start
* WARNING: nfs is already starting
ae429-1105 linux # rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
|
|
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Mon Jul 21, 2014 3:46 am Post subject: |
|
|
| @diablo: then start a thread asking for help, instead of resurrecting one from 6 years ago ;-) |
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
