scp: Write Failed: Cannot allocate memory

Scott Sipe cscotts at
Mon Jul 25 13:59:16 UTC 2011

On Jul 24, 2011, at 10:07 PM, Adrian Chadd wrote:

> Has someone asked for the output of netstat -mb? That error message is
> mbuf related, so I bet it's something to do with mbuf allocation.
> Is it possible that the system is incorrectly tuned when virtualbox is enabled?
> Adrian

I never ran netstat -mb when I was encountering the network memory allocation error. At the moment I have adjusted net.graph.maxdata from the default value to 8192, rebooted, and have not encountered any more network memory allocation errors (and vmstat -z shows 0 NetGraph data item failures). If, at this maxdata setting, they show up again I'll post the output of netstat -mb. If it's worth anything, current output of netstat -mb is below.

# netstat -mb
1027/6668/7695 mbufs in use (current/cache/total)
1024/4034/5058/25600 mbuf clusters in use (current/cache/total/max)
1024/3456 mbuf+clusters out of packet secondary zone in use (current/cache)
0/1303/1303/12800 4k (page size) jumbo clusters in use (current/cache/total/max)
0/0/0/6400 9k jumbo clusters in use (current/cache/total/max)
0/0/0/3200 16k jumbo clusters in use (current/cache/total/max)
2304K/14947K/17251K bytes allocated to network (current/cache/total)
0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
0/0/0 requests for jumbo clusters denied (4k/9k/16k)
0/0/0 sfbufs in use (current/peak/max)
0 requests for sfbufs denied
0 requests for sfbufs delayed
19 requests for I/O initiated by sendfile
0 calls to protocol drain routines


More information about the freebsd-stable mailing list