public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <dsterba@suse.cz>, Jim Salter <jim@jrs-s.net>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send: page allocation failure
Date: Mon, 13 Jan 2014 13:36:37 -0500	[thread overview]
Message-ID: <52D43235.7060502@fb.com> (raw)
In-Reply-To: <20140113182312.GR6498@twin.jikos.cz>


On 01/13/2014 01:23 PM, David Sterba wrote:
> On Mon, Jan 13, 2014 at 07:58:48AM -0500, Jim Salter wrote:
>> Getting sporadic page allocation failures in btrfs send. This happened once
>> several weeks ago but was fine after a reboot; yesterday I did not reboot,
>> but had the failure back-to-back trying to send two different snapshots.
>> These are full sends, not incremental, of a bit over 600G of data. Test
>> machine has 32G of RAM, with 21G of it free (not including cache):
>>
>> root@gwa-virt1:/data/images/.snapshots# free -m
>>               total       used       free     shared    buffers cached
>> Mem:         32159      31789        369          0          0 21276
>> -/+ buffers/cache:      10513      21646
>> Swap:            0          0          0
>>
>> In both cases (all three, really) the btrfs send failed a bit more than half
>> of the way through the send (somewhere around the 380GB mark).
>>
>> Kern log snippets follow:
>>
>> Jan 12 14:05:36 gwa-virt1 kernel: [535523.627611] btrfs: page allocation
>> failure: order:6, mode:0x104050
>> Jan 12 14:05:36 gwa-virt1 kernel: [535523.627818] [<ffffffffa01876dd>] ?
>> ulist_add_merge+0xcd/0x270 [btrfs]
> That's the krealloc failure, Josef has a patch that came out of
> https://bugzilla.kernel.org/show_bug.cgi?id=60579
> but I don't see it merged anywhere.
That patch isn't quite right which is why it isn't merged, I'll come up 
with something better and send it out soonish.  Thanks,

Josef

  reply	other threads:[~2014-01-13 18:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 12:58 btrfs send: page allocation failure Jim Salter
2014-01-13 15:17 ` Wang Shilong
2014-01-13 15:20   ` Jim Salter
2014-01-13 15:29     ` Wang Shilong
2014-01-13 15:44       ` Wang Shilong
2014-01-13 16:00         ` Jim Salter
2014-01-13 16:09           ` Wang Shilong
2014-01-13 16:01         ` Jim Salter
2014-01-13 18:23 ` David Sterba
2014-01-13 18:36   ` Josef Bacik [this message]
2014-01-13 18:37   ` Jim Salter
2014-01-13 18:56     ` David Sterba
2014-01-13 19:03       ` Jim Salter
2014-01-14 13:13         ` David Sterba
2014-01-14 14:58           ` Jim Salter

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=52D43235.7060502@fb.com \
    --to=jbacik@fb.com \
    --cc=dsterba@suse.cz \
    --cc=jim@jrs-s.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox