From: Michal Suchanek <hramrach@gmail.com>
To: linux-mm@kvack.org, 699277@bugs.debian.org
Subject: Re: doing lots of disk writes causes oom killer to kill processes
Date: Mon, 11 Mar 2013 14:15:43 +0100 [thread overview]
Message-ID: <CAOMqctRiLa-uVaD=omeOT5o-UdcOJo6WgOm8nBaN6S-x+Dh1KA@mail.gmail.com> (raw)
In-Reply-To: <CAOMqctTf9+sz7Ffm-mLLeGNqH27yvuM+vORrG65Yoh3JKDFLnQ@mail.gmail.com>
On 8 February 2013 17:31, Michal Suchanek <hramrach@gmail.com> wrote:
> Hello,
>
> I am dealing with VM disk images and performing something like wiping
> free space to prepare image for compressing and storing on server or
> copying it to external USB disk causes
>
> 1) system lockup in order of a few tens of seconds when all CPU cores
> are 100% used by system and the machine is basicaly unusable
>
> 2) oom killer killing processes
>
> This all on system with 8G ram so there should be plenty space to work with.
>
> This happens with kernels 3.6.4 or 3.7.1
>
> With earlier kernel versions (some 3.0 or 3.2 kernels) this was not a
> problem even with less ram.
>
> I have vm.swappiness = 0 set for a long time already.
>
>
I did some testing with 3.7.1 and with swappiness as much as 75 the
kernel still causes all cores to loop somewhere in system when writing
lots of data to disk.
With swappiness as much as 90 processes still get killed on large disk writes.
Given that the max is 100 the interval in which mm works at all is
going to be very narrow, less than 10% of the paramater range. This is
a severe regression as is the cpu time consumed by the kernel.
The io scheduler is the default cfq.
If you have any idea what to try other than downgrading to an earlier
unaffected kernel I would like to hear.
Thanks
Michal
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-03-11 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:31 Michal Suchanek
2013-03-11 13:15 ` Michal Suchanek [this message]
2013-03-12 2:15 Hillf Danton
2013-03-12 9:03 ` Michal Suchanek
2013-08-26 13:51 ` Michal Suchanek
2013-09-05 10:12 ` Michal Suchanek
2013-09-17 13:31 ` Michal Suchanek
2013-09-17 21:13 ` Jan Kara
2013-09-17 22:22 ` Michal Suchanek
2013-09-18 14:56 ` Michal Suchanek
2013-09-19 10:13 ` Jan Kara
2013-10-09 14:19 ` Michal Suchanek
2013-10-15 14:15 ` Michal Suchanek
2014-07-07 11:34 ` Michal Suchanek
[not found] ` <CAJd=RBD_6FMHS3Dg_Zqugs4YCHHDeCgrxypANpPP5K2xTLE0bA@mail.gmail.com>
2013-09-20 11:20 ` Michal Suchanek
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='CAOMqctRiLa-uVaD=omeOT5o-UdcOJo6WgOm8nBaN6S-x+Dh1KA@mail.gmail.com' \
--to=hramrach@gmail.com \
--cc=699277@bugs.debian.org \
--cc=linux-mm@kvack.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