Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Nov 1996 01:04:20 -0600 (CST)
From:      Michael Borowiec <mikebo@Mcs.Net>
Cc: (Michael Borowiec)
Subject:   /kernel: nfsd send error 55 (No buffer space available)
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
Greetings -
I have a Toshiba Tecra 720CDT w/48MB and a 3Com 3C589C PCCARD ethernet.
I'm configuring this machine as an NFS server with 4 nfsd's running...

My client machine is a 486DX50 w/16MB and a WD8013EPC ISA ethernet.
I'm configuring this machine as the NFS client with 4 nfsiod's running...

Both are running 2.1.5R. After copying a few files from server to client,
the transfer freezes, and the server (laptop) starts displaying this error
message, approx. once every 30 seconds:

server /kernel: nfsd send error 55

Of course, this is the dreaded mbuf problem, confirmed by trying a ping:
server# ping client
PING client ( 56 data bytes
ping: sendto: No buffer space available
ping: wrote client 64 chars, ret=-1

I rebuilt the server's kernel with more mbuf's, thinking this might
solve it:
options		"NMBCLUSTERS=2048"
but get the same problem... and the client must be rebooted each time.
The server can be restored to "sanity" by killing all nfsd's and
down-ing, then up-ing the interface (zp0). But to play it safe, both
client and server were rebooted - same problem.

server# netstat -m
155 mbufs in use:
	115 mbufs allocated to data
	34 mbufs allocated to packet headers
	4 mbufs allocated to protocol control blocks
	2 mbufs allocated to socket names and addresses
34/34 mbuf clusters in use
87 Kbytes allocated to network (100% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

It doesn't look like many clusters are allocated at all...
Does anyone know what might be causing this? Any suggestions?
- Mike

Want to link to this message? Use this URL: <>