linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Nico Schottelius <nico-kernel20120920@schottelius.org>,
	Valdis.Kletnieks@vt.edu, David Rientjes <rientjes@google.com>,
	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>,
	jfs-discussion@lists.sourceforge.net
Subject: Re: [Jfs-discussion] Out of memory on 3.5 kernels
Date: Tue, 27 Nov 2012 09:56:58 -0600	[thread overview]
Message-ID: <50B4E2CA.6060508@oracle.com> (raw)
In-Reply-To: <50AD5791.5010702@oracle.com>

On 11/21/2012 04:37 PM, Dave Kleikamp wrote:
> On 10/30/2012 05:35 AM, Nico Schottelius wrote:
>> Good morning,
>>
>> update: this problem still exists on 3.6.2-1-ARCH and it got worse:
>>
>> I reformatted the external disk to use xfs, but as the my
>> root filesystem is still jfs, it still appears:
>>
>>  Active / Total Objects (% used)    : 642732 / 692268 (92.8%)
>>  Active / Total Slabs (% used)      : 24801 / 24801 (100.0%)
>>  Active / Total Caches (% used)     : 79 / 111 (71.2%)
>>  Active / Total Size (% used)       : 603522.30K / 622612.05K (96.9%)
>>  Minimum / Average / Maximum Object : 0.01K / 0.90K / 15.25K
>>
>>   OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME                   
>> 475548 467649  98%    1.21K  18722       26    599104K jfs_ip

...

>>
>> I am wondering if anyone is feeling responsible for this bug or if the mid-term
>> solution is to move away from jfs?
> 
> Sorry, I haven't taken too close a look at this, but I did notice
> another conversation that may be related:
> 
> https://lkml.org/lkml/2012/11/17/26
> 
> The commit in question first showed up in 3.5-rc1, which coincides with
> your problem.

I believe this commit will fix the problem:
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4eff96d

It is targeted for the stable kernels.

  reply	other threads:[~2012-11-27 15:57 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
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                     ` Dave Kleikamp [this message]
2012-11-27 16:11                       ` [Jfs-discussion] " 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=50B4E2CA.6060508@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=arend@broadcom.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nico-kernel20120920@schottelius.org \
    --cc=rientjes@google.com \
    /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).