linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel20120920@schottelius.org>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: David Rientjes <rientjes@google.com>,
	Nico Schottelius <nico-kernel20120920@schottelius.org>,
	Arend van Spriel <arend@broadcom.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Dave Kleikamp <shaggy@kernel.org>,
	jfs-discussion@lists.sourceforge.net
Subject: Re: Out of memory on 3.5 kernels
Date: Wed, 26 Sep 2012 08:03:12 +0200	[thread overview]
Message-ID: <20120926060312.GC16575@schottelius.org> (raw)
In-Reply-To: <5061C8A2.1020605@oracle.com>

Good morning,

Dave Kleikamp [Tue, Sep 25, 2012 at 10:07:14AM -0500]:
> >>  Active / Total Objects (% used)    : 1165130 / 1198087 (97.2%)
> >>  Active / Total Slabs (% used)      : 81027 / 81027 (100.0%)
> >>  Active / Total Caches (% used)     : 69 / 101 (68.3%)
> >>  Active / Total Size (% used)       : 1237249.81K / 1246521.94K (99.3%)
> >>  Minimum / Average / Maximum Object : 0.01K / 1.04K / 15.23K
> >>
> >>   OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME                   
> >> 993607 993607 100%    1.21K  75358       26   2411456K jfs_ip
> > 
> > Well that doesn't look good.  100% of the inode cache for jfs are being 
> > used which either means
> > 
> >  - there's a memory leak, or
> 
> maybe a missing iput() somewhere?
> 
> Nico, does unmounting the usb drive after killing the backup clean up
> the jfs inode cache?

Iirc, it does not. I'll check this evening, because doing the backup
currently forces me to reboot my productive system.

> >  - there's some sort of throttling issue in jfs.
> > 
> > And those objects are consuming ~2.3GB of slab on your 4GB machine and 
> > seems to only have occurred between v3.4.2 to v3.5.3.
> 
> Almost nothing in jfs has changed between these releases. Only this:
> 
> vfs: Rename end_writeback() to clear_inode()

The other obscurity is that the root filesystem is also jfs - it's not
only the usb disk.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

  reply	other threads:[~2012-09-26  7:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 13:52 Out of memory on 3.5 kernels Arend van Spriel
2012-09-21 19:49 ` Nico Schottelius
2012-09-21 21:02   ` Fwd: " Arend van Spriel
2012-09-24 22:43   ` David Rientjes
2012-09-25 15:07     ` Dave Kleikamp
2012-09-26  6:03       ` Nico Schottelius [this message]
2012-09-26  6:06     ` Nico Schottelius
2012-09-26  8:57       ` Nico Schottelius
2012-09-27  5:52         ` Nico Schottelius
2012-10-03 21:23           ` Nico Schottelius
2012-10-05 15:48             ` Valdis.Kletnieks
2012-10-05 17:51               ` Nico Schottelius
2012-10-30 10:35                 ` Nico Schottelius
2012-11-01 18:04                   ` [Jfs-discussion] " Tino Reichardt
2012-11-21 22:37                   ` Dave Kleikamp
2012-11-27 15:56                     ` [Jfs-discussion] " Dave Kleikamp
2012-11-27 16:11                       ` Nico Schottelius

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=20120926060312.GC16575@schottelius.org \
    --to=nico-kernel20120920@schottelius.org \
    --cc=arend@broadcom.com \
    --cc=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=shaggy@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).