Date: Tue, 13 Jan 2004 11:50:41 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Ollie Cook <ollie@uk.clara.net> Cc: freebsd-stable@freebsd.org Subject: Re: nfs send errors 32 and 35 on RELENG_4 Message-ID: <20040113114525.L63732@carver.gumbysoft.com> In-Reply-To: <20040113154932.GE354@mutare.noc.clara.net> References: <20040113154932.GE354@mutare.noc.clara.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jan 2004, Ollie Cook wrote: > For a while I have been seeing errors of this nature on a cluster of i386 > FreeBSD RELENG_4 hosts which mount a volume from a NetApp F825 filer using > NFSv3 over a mixture of UDP and TCP, depending on whether the host is on the > same local LAN as the filer or not: > > Jan 13 14:02:02 mese /kernel: nfs server 192.168.1.1:/vol/vol1/claramail: not responding > Jan 13 14:02:03 mese /kernel: nfs server 192.168.1.1:/vol/vol1/claramail: is alive again There's some tuning options for this, which I don't immediately recall. Under heavy load these are somewhat normal. > Jan 13 14:09:37 mese /kernel: nfs send error 35 for server 192.168.1.1:/vol/vol1/claramail > Jan 13 14:09:42 mese /kernel: nfs send error 35 for server 192.168.1.1:/vol/vol1/claramail > Jan 13 14:09:47 mese /kernel: nfs send error 35 for server 192.168.1.1:/vol/vol1/claramail > Jan 13 14:09:52 mese /kernel: nfs send error 35 for server 192.168.1.1:/vol/vol1/claramail > Jan 13 14:09:53 mese /kernel: nfs send error 32 for server 192.168.1.1:/vol/vol1/claramail These errors tend to imply resource shortages. Monitor netstat -m output and make sure you aren't running out of mbuf or mbuf clusters. Also check for network errors and dropped packets (netstat -s, switch statistics). Are you running rpc.lockd? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040113114525.L63732>