All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: ERROR: send ioctl failed with -12: Cannot allocate memory
Date: Thu, 5 Dec 2013 10:40:17 +0000 (UTC)	[thread overview]
Message-ID: <pan$4241a$4b7f93$d94ca09a$ad1032fe@cox.net> (raw)
In-Reply-To: 52A01A29.3020005@jrs-s.net

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


      reply	other threads:[~2013-12-05 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  6:16 ERROR: send ioctl failed with -12: Cannot allocate memory Jim Salter
2013-12-05 10:40 ` Duncan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$4241a$4b7f93$d94ca09a$ad1032fe@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.