linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: 3.10.11 scrub OOM crash
Date: Sun, 10 Nov 2013 10:48:17 +1100	[thread overview]
Message-ID: <201311101048.17277.russell@coker.com.au> (raw)

I've got an AMD64 system with 8G of RAM and 1G of swap.  It runs as a home 
file server with 2*3TB disks in a RAID-1 array and a 120G SSD for root and 
/home.  It also does some light desktop work (running KDE and web browsing 
with Chromium).

When a btrfs scrub is run from cron the system gives an OOM and then locks up 
after apparently killing some processes (after a reboot I see syslog entries 
about some processes being killed - even though it didn't appear to kill X or 
anything the system is hung).

The system really shouldn't have a OOM.  For light desktop use a total of 8G 
of RAM and 1G of swap should be more than enough.  Most of the time swap is 
hardly used and there are several gigs of RAM used for cache.

The kernel is Debian package 3.10.11-1.

This is the same system about which I reported the 3.11.5 kernel infinite loop 
bug.  I had this crash on scrub issue before I upgraded to 3.11.5.  I'm not 
certain that 3.11.5 fixed the crash on scrub problem, maybe 3.11.5 just 
crashed the system before it could be up for long enough.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

             reply	other threads:[~2013-11-09 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09 23:48 Russell Coker [this message]
2013-11-10 10:29 ` 3.10.11 scrub OOM crash Duncan
2013-11-10 13:01   ` Russell Coker

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=201311101048.17277.russell@coker.com.au \
    --to=russell@coker.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).