nfs server not responding / is alive again

Alex de Kruijff freebsd at
Mon Oct 4 22:22:52 PDT 2004

On Mon, Oct 04, 2004 at 12:22:30AM -0300, Marc G. Fournier wrote:
> I'm using an nfs mount to get at the underlying file system on a system 
> that uses unionfs mounts ... instead of using nullfs, which, last time I 
> used it over a year ago, caused the server to crash to no end ...
> But, as soon as there is any 'load', I'm getting a whack of:
> Oct  3 22:46:16 neptune /kernel: nfs server not 
> responding
> Oct  3 22:46:16 neptune /kernel: nfs server is alive 
> again
> Oct  3 22:48:30 neptune /kernel: nfs server not 
> responding
> Oct  3 22:48:30 neptune /kernel: nfs server is alive 
> again
> in /var/log/messages ...
> I'm running nfsd with the standard flags:
> 	nfs_server_flags="-u -t -n 4"
> Is there something that I can do to reduce this problem?  increase number 
> of nfsd processes?  force a tcp connection?

You could try giving the nfsd processes more priority as root with
rtprio. If the file /var/run/ exist then you could try something
like: rtprio 10 -`cat /var/run/`.

You could also try giving the other porcesses less priority like
nice -n 2 rsync. But i'm am not show how this works at the other end. 

> The issue is more prevalent when I have >4 processes trying to read from 
> the nfs mounts ... should there be one mount per process?  the process(es) 
> in question are rsync, if that helps ... they tend to be a bit more 'disk 
> intensive' then most processes, which is why I thought of increasing -n 
> ...

I think you're problem is not that you disk is used havely but that
you're NIC (rsync kinda does that) is. The warnings you get indicate
that you're computer can't get a responce from you're server. It acts
normaly as soon as it can.

Why do you have rsync sync mounted nfs disks?


Articles based on solutions that I use:

More information about the freebsd-questions mailing list