[lkml]   [2007]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectLinux machines dieing in swap storms
    I've got a problem I keep running into. My computers have buggy software
    which can sometimes run out of control. Two specific examples:

    Evolution: Sometimes its memory usage decides to suddenly grow out of
    control. It usually idles at around 300MB, you can watch it in top,
    doubling, trebling and ending up going past the 1200MB mark. My system
    has 1.5GB ram and you notice it swapping heavily past say 800MB.

    Spamassassin: If my mail server log files hit the 2GB file size limit of
    the filesystem something strange happens and for whatever reason spamd
    suddenly starts growing in memory usage until it uses up all available
    system memory.

    Arguably both pieces of software are buggy, I accept that, fine.

    In both machines in totally different circumstances what happens next is
    bad. The systems swap more and more heavily trying to cope with these
    out of control processes. Network interactivity stops. The swap storm
    gets so bad you can't log onto the console any more. I've left machines
    in this state for 1-2 hours and they don't come back. Watching the
    console, the OOM killer does kick in but it never kills the problem
    process (both spamd and evolution are long running processes that have
    suddenly gone out of control). In then end, you have to hit the reset
    switch :(. This happened to my desktop once again about 10 minutes ago
    and its *extremely* frustrating. Sometimes I can catch and kill the
    offending process but I shouldn't have to.

    This isn't a new problem. My mail server used to be running an ancient
    2.6.12 kernel and I upgraded it to 2.6.22.X in an effort to solve this
    problem which no change. My desktop shows exactly the same kind of OOM
    swap storm behaviour (2.6.20 based).

    I realise that tuning the OOM killer is a really tricky problem but
    something needs improving as the current user experience is broken.

    I'm seriously tempted to add a "kill the process using the most memory"
    key combination into SysRq which might let me save the desktop but won't
    help with my remote server. I could also just disable swap I guess.

    Advice on solving this welcome preferably in mainline but I'll happily
    hack my kernels with a workaround if need be.



    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-10-25 17:23    [W:0.031 / U:5.724 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site