linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Russell Coker <russell@coker.com.au>
Cc: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14?
Date: Fri, 4 Jul 2014 08:07:10 -0700	[thread overview]
Message-ID: <20140704150710.GM26932@merlins.org> (raw)
In-Reply-To: <3262371.bchVJ2xl3c@xev>

On Sat, Jul 05, 2014 at 12:45:55AM +1000, Russell Coker wrote:
> > But the last times I had this OOM problem with 3.15.1 it was happening
> > within 6 hours sometimes, and I was not starting scrub every time the
> > system booted, so scrub may be partially responsible but it's not the
> > core problem.
> 
> It would be a good idea to run a few scrubs and see if this is a repeatable 
> problem.  If it's a repeatable problem then it's something to fix regardless 
> of whether it's the only issue you have.

Fair point. Re-running scrub now. That will take 36H or so :)
 
> If a scrub can reliably trigger the problem it would be good to test 3.14 for 
> the same behavior.  Knowing whether it's a regression would help the 
> developers.
 
I'm already back to 3.14. 3.15 was dying about once a day without scrub,
enough that this was causing me real problems (it's a server that is
supposed to do work :) ).

> Even without much swap 8G should be a plenty.  My main workstation has 4G of 
> RAM and 6G of swap.  I almost never use more than 3G of swap because the 
> system becomes so slow as to be almost unusable when swap gets to 4G (Chromium 
> is to blame).  However that is for a 120G non-RAID filesystem.  Presumably a 
> RAID array will need some more kernel memory and a larger filesystem will also 
> need a little more, but it still shouldn't be that much.

You're correct. I only have more swap than ram, both as a habit in case
I ever want to hibernate a system (I don't with this one) and in case
some userland stuff leaks a lot (I've had versions of Xorg leak and that
would improve the time between which I had to restart X and lose all my
window state :) ).

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2014-07-04 15:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  1:19 Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14? Marc MERLIN
2014-07-04  4:33 ` Russell Coker
2014-07-04  6:04   ` Marc MERLIN
2014-07-04  6:23   ` Satoru Takeuchi
2014-07-04 14:24     ` Marc MERLIN
2014-07-04 14:45       ` Russell Coker
2014-07-04 15:07         ` Marc MERLIN [this message]
2014-07-04 22:13       ` Duncan
2014-07-05 13:47 ` Andrew E. Mileski
2014-07-05 14:43   ` Marc MERLIN
2014-07-05 15:17     ` Andrew E. Mileski
2014-07-06 14:58     ` Marc MERLIN
2014-07-13 14:29       ` btrfs is " Marc MERLIN
2014-07-13 15:37         ` Marc MERLIN
2014-07-13 15:45           ` btrfs quotas " Marc MERLIN
2014-07-14  1:36             ` Qu Wenruo
2014-07-14  2:43               ` Marc MERLIN
2014-07-14  1:24         ` btrfs is " Qu Wenruo
2014-07-16  0:36           ` Jérôme Poulin
2014-07-16 15:55           ` Marc MERLIN
2014-07-17  2:22             ` Marc MERLIN
2014-07-16  0:45       ` Is btrfs " Jérôme Poulin
2014-07-05 14:27 ` Andrew E. Mileski

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=20140704150710.GM26932@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    --cc=takeuchi_satoru@jp.fujitsu.com \
    /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;
as well as URLs for NNTP newsgroup(s).