From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.iobjects.de ([188.40.134.68]:34016 "EHLO mail02.iobjects.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751111AbcJCShX (ORCPT ); Mon, 3 Oct 2016 14:37:23 -0400 Subject: Re: 4.8rc8 & OOM panic To: E V , linux-btrfs References: <57EC1DE1.90608@applied-asynchrony.com> From: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?= Message-ID: <57F2A560.9070702@applied-asynchrony.com> Date: Mon, 3 Oct 2016 20:37:20 +0200 MIME-Version: 1.0 In-Reply-To: <57EC1DE1.90608@applied-asynchrony.com> Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 09/28/16 21:45, Holger Hoffstätte wrote: > 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/ Sorry, that was not quite correct. -stable 4.7.x and 4.8 contain a workaround (http://goo.gl/DiwfPH) that is supposed to help. That went into 4.8rc8 already, so not sure what happened in your case. > So unless they get merged in the last minute it looks like 4.8 will > be DOA. Running 4.8 final now, let's see what happens.. -h