All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Titov <a.titov@host.bg>
To: Chase Venters <chase.venters@clientec.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: OOM Killer killing whole system
Date: Fri, 20 Jan 2006 23:48:05 +0200	[thread overview]
Message-ID: <1137793685.11771.58.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0601201401500.14198@turbotaz.ourhouse>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

On Fri, 2006-01-20 at 14:04 -0600, Chase Venters wrote:
> On Fri, 20 Jan 2006, Andrew Morton wrote:
> >> Jan 15 06:05:09 vip 216477 pages slab
> >
> > It's all in slab.  800MB.
> >
> > I'd be suspecting a slab memory leak.  If it happens again, please take a
> > copy of /proc/slabinfo, send it.
> >
> 
> Andrew & Anton,
>  The culprit was 1.5 million SCSI commands in the scsi command cache. 
> 
> Thanks,
> Chase

I currently have this:
scsi_cmd_cache    1458778 1458790    384   10    1 : tunables   54 27
8 : slabdata 145879 145879      0

in /proc/slabinfo, which is pretty close to 1.5 million. The system is
working fine but it should be not very loaded anyway, so a mem leakage
will not show up early. Just checked, that scsi_cmd_cache on other
machines of mine is under 100, so it seems like a problem.

Unfortunately, while being a programmer, I'm totally unaware
what /proc/slabinfo means, but I'm perfectly willing to provide a shell
(in case of Andrew or other famous developer it may be even root) on
this machine.

I'm attaching the /proc/slabinfo

Thanks for help,
Anton



[-- Attachment #2: slab.gz --]
[-- Type: application/x-gzip, Size: 1863 bytes --]

  reply	other threads:[~2006-01-20 21:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 15:05 OOM Killer killing whole system Anton Titov
2006-01-20 12:11 ` Andrew Morton
2006-01-20 20:04   ` Chase Venters
2006-01-20 21:48     ` Anton Titov [this message]
2006-01-20 22:50       ` Andrew Morton
2006-01-21  0:09         ` Anton Titov
2006-01-21  0:19         ` Chase Venters
2006-01-21  0:50           ` Andrew Morton
2006-01-21  1:17             ` James Bottomley
2006-01-21  3:29               ` Anton Titov
2006-01-21  3:44                 ` Andrew Morton
2006-01-25 22:20                 ` Matthias Urlichs
2006-01-21  3:45               ` Anton Titov
2006-01-21  3:53                 ` Chase Venters
2006-01-21  4:21                   ` Anton Titov
2006-01-21  4:35                     ` Chase Venters
2006-01-23  2:56                       ` Kalin KOZHUHAROV
2006-01-23  3:28                         ` Chase Venters
2006-01-23  8:39           ` Jens Axboe
2006-01-23  8:41             ` Arjan van de Ven
2006-01-23  9:10               ` Chase Venters
  -- strict thread matches above, loose matches on Subject: below --
2006-01-23 12:55 Nicolas Mailhot

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=1137793685.11771.58.camel@localhost \
    --to=a.titov@host.bg \
    --cc=akpm@osdl.org \
    --cc=chase.venters@clientec.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.