From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: E V <eliventer@gmail.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 4.8rc8 & OOM panic
Date: Wed, 28 Sep 2016 21:45:37 +0200 [thread overview]
Message-ID: <57EC1DE1.90608@applied-asynchrony.com> (raw)
In-Reply-To: <CAJtFHUTUvJpMSzBXy+Ub+_iPRPocWXHfubA=5p4TyQqCj-29AQ@mail.gmail.com>
On 09/28/16 20:46, E V wrote:
> I just booted my backup box with 4.8rc8 and started an rsync onto
> btrfs and it panic'd with OOM a couple hours later. I thought the OOM
> problems from 4.7 we're supposed to be fixed in 4.8, or did I get that
> wrong? No users or anything else on the system.
Keep in mind that those problems are generic, other filesystems also
suffer: http://www.spinics.net/lists/linux-mm/msg114123.html
I don't see any recent compaction-related patches in Linus' tree at
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/mm/
..so it seems they have not been merged yet.
So unless they get merged in the last minute it looks like 4.8 will
be DOA.
-h
next prev parent reply other threads:[~2016-09-28 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:46 4.8rc8 & OOM panic E V
2016-09-28 19:45 ` Holger Hoffstätte [this message]
2016-10-03 18:37 ` Holger Hoffstätte
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=57EC1DE1.90608@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=eliventer@gmail.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 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.