public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Tap <tap@anti-paladin.com>, xfs@oss.sgi.com
Subject: Re: Exponential memory usage?
Date: Fri, 28 Mar 2014 20:24:24 -0500	[thread overview]
Message-ID: <533620C8.1010204@sandeen.net> (raw)
In-Reply-To: <DF4B0D0E-6D5A-4670-9301-A1DCD0EEAE6E@anti-paladin.com>

On 3/28/14, 12:53 PM, Tap wrote:
> I have a Linux CentOs-based (6.5) system, running Linux 3.10.29
> beneath xen 4.2.3-26 with a raid array as follows:

<snip>

> Anyway at some point the system had become unusable.  Something as
> simple as:
> 
> find  /raid -type f -- or -- ls -lR /raid
> 
> Would walk the entire system out of RAM.  Looking at slabtop it looks
> like this is due mostly to xfs_inode memory usage.  Note that since
> these problems began I stopped running all sub-ordinate domains and
> am now only running dom0.  In fact I've allocated all 32 GB to that
> domain, and memory problems still persist.

Out of?  Did the OOM-killer actually show up, or did you simply see
memory usage rise?

The dcache is tenacious.  dentries are cached pretty aggressively, and
those in turn will pin the vfs/xfs inodes.

But memory is there to be used; unless you actually see problems,
then the system is likely working as it should be.

<snip>

> Note:  FWIW Un-mounting the filesystem also recovers the memory.

Yep, that would clear out the cache.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2014-03-29  1:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 17:53 Exponential memory usage? Tap
2014-03-28 20:09 ` Stefan Ring
2014-03-29  1:03 ` Stan Hoeppner
2014-03-29  1:24 ` Eric Sandeen [this message]

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=533620C8.1010204@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=tap@anti-paladin.com \
    --cc=xfs@oss.sgi.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