From: Stan Hoeppner <stan@hardwarefreak.com>
To: daiguochao <dx-wl@163.com>, xfs@oss.sgi.com
Subject: Re: 10GB memorys occupied by XFS
Date: Fri, 04 Apr 2014 15:24:12 -0500 [thread overview]
Message-ID: <533F14EC.6040705@hardwarefreak.com> (raw)
In-Reply-To: <1396596386220-35015.post@n7.nabble.com>
On 4/4/2014 2:26 AM, daiguochao wrote:
> Hello folks,
Hello,
Note that your problems are not XFS specific, but can occur with any
Linux filesystem.
> I used xfs file system in kernel-2.6.32-220.13.1.el6.x86_64 for store
> pictures. About 100 days system memorys is lost and some nginx process is
> killed by oom-killer.So,I looked /proc/meminfo and find memorys is
> lost.Finally, I try to umount xfs system and 10GB memorys is coming back. l
> look xfs bugzilla no such BUG.I have no idea for it.
>
> Cheers,
>
> Guochao.
>
> some memorys info:
>
> 0> free -m
> total used free shared buffers cached
> Mem: 11887 11668 219 0 0 2
> -/+ buffers/cache: 11665 222
> Swap: 0 0 0
First problem: no swap
Second problem: cache is not being reclaimed
Read vfs_cache_pressure at:
https://www.kernel.org/doc/Documentation/sysctl/vm.txt
You've likely set this value to zero. Changing it to 200 should prompt
the kernel to reclaim dentries and inodes aggressively, preventing the
oom-killer from kicking in.
Cheers,
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-04-04 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 7:26 10GB memorys occupied by XFS daiguochao
2014-04-04 20:24 ` Stan Hoeppner [this message]
[not found] ` <76016fc7.13c84.14546bad411.Coremail.dx-wl@163.com>
2014-04-10 1:41 ` 答复: " 戴国超
2014-04-11 5:09 ` Stan Hoeppner
2014-04-11 2:40 ` daiguochao
2014-04-11 4:26 ` Dave Chinner
2014-04-11 21:35 ` Stan Hoeppner
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=533F14EC.6040705@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=dx-wl@163.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 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.