From: Jim Salter <jim@jrs-s.net>
To: dsterba@suse.cz, linux-btrfs <linux-btrfs@vger.kernel.org>,
jbacik@fb.com
Subject: Re: btrfs send: page allocation failure
Date: Mon, 13 Jan 2014 14:03:52 -0500 [thread overview]
Message-ID: <52D43898.5080801@jrs-s.net> (raw)
In-Reply-To: <20140113185636.GU6498@suse.cz>
OK, thanks. If kernel memory fragmentation is a big factor, that would
also explain why it succeeds after a reboot but does not succeed after
weeks of uptime...
On 01/13/2014 01:56 PM, David Sterba wrote:
> On Mon, Jan 13, 2014 at 01:37:31PM -0500, Jim Salter wrote:
>> What makes you believe that? The bug filed there appears to be related to
>> defragging, which I am not doing either manually or automatically.
> The quota groups are on and the symptoms match the known problem when
> there are lots of backrefs.
> krealloc is on the stack although not mentioned explicitly, called
> through ulist_add_merge. The allocation order is 6 from the OOM report,
> means that somebody wanted a large congiguous chunk of memory, which is
> what the krealloc did and failed. Kernel memory is fragmented and this
> kind of allocations is hard to satisfy in the long run.
>
> david
next prev parent reply other threads:[~2014-01-13 19:03 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
2014-01-13 18:37 ` Jim Salter
2014-01-13 18:56 ` David Sterba
2014-01-13 19:03 ` Jim Salter [this message]
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=52D43898.5080801@jrs-s.net \
--to=jim@jrs-s.net \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--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