ERROR: send ioctl failed with -12: Cannot allocate memory

ERROR: send ioctl failed with -12: Cannot allocate memory

[Jim Salter]

Sending a 585G snapshot from box1 to box2:

     # ionice -c3 btrfs send daily*2013-12-01* | pv -L40m -s585G | ssh 
-c arcfour 10.0.0.40 btrfs receive /data/.snapshots/data/images
     At subvol daily_[1385956801]_2013-12-01_23:00:01
     At subvol daily_[1385956801]_2013-12-01_23:00:01
     ERROR: send ioctl failed with -12: Cannot allocate 
memory=======================================> ]     59% ETA 2:04:01
      347GB 3:00:12 [32.8MB/s]
[=====================================================================> ]
     59%
     ERROR: unexpected EOF in stream.

Send failed a little over halfway through with "Cannot allocate memory" 
error.  Which is surprising, given that this is a relatively lightly 
loaded 32G server.  Output of free -m, taken immediately after seeing 
the error above:

     root@gwa-virt1:/data/.snapshots/data/images# free -m
                  total       used       free     shared buffers     cached
     Mem:         32158      31798        360          0 0      22092
     -/+ buffers/cache:       9705      22453
     Swap:            0          0          0

Anybody got any suggestions?

Re: ERROR: send ioctl failed with -12: Cannot allocate memory

[Duncan]

Jim Salter posted on Thu, 05 Dec 2013 01:16:09 -0500 as excerpted:

> Sending a 585G snapshot from box1 to box2:

>      59%
>      ERROR: unexpected EOF in stream.
> 
> Send failed a little over halfway through with "Cannot allocate memory"
> error.  Which is surprising, given that this is a relatively lightly
> loaded 32G server.

What kernel are you running?  There are a number of very recent memory 
leak patches, so recently that even 3.12 may not have them, especially if 
you're not on the latest stable update.  If you're running the latest 
3.13-r2 or a live-git kernel, you'll have those fixes, but there may be 
others still in the pipeline, as memory leaks seem to be the focus right 
now and as I said several have been very recently fixed.

If you're running the very latest 3.13 git kernels and are still seeing 
it, then I expect the devs will be very interested indeed, because that 
does seem to be one of the major focuses ATM, so might as well get it 
fixed while it's hot!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman