All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Seth Huang <seth.hg@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: OOM problem caused by fs
Date: Mon, 7 Jun 2010 19:53:41 +1000	[thread overview]
Message-ID: <20100607095341.GM26335@laptop> (raw)
In-Reply-To: <AANLkTiliZt_ml6TCb5RdWqsqv_KFkGcLQqS65TCfktR2@mail.gmail.com>

On Mon, Jun 07, 2010 at 04:34:16PM +0800, Seth Huang wrote:
> Hello everyone,
> 
> Our group is developing a new file system for linux and we got stuck
> with out-of-memory problem.
> 
> When creating large files in our fs, the system will run out of
> memory(I mean the kernel starts to dump memory usage repeatedly and
> the oom killer begins to kill processes) as long as the amount of data
> exceeds the capacity of free memory, even if the kernel is flushing
> out dirty pages.
> 
> If i'm right, when available memory is low, the writes will be blocked
> in page cache allocation until some dirty pages are cleaned. I've
> checked pdflush, it works fine in our system, which means dirty pages
> can be flushed out and cleaned in time. However, it still crashes the
> system. I've no idea how could this happen.
> 
> Has anyone experienced the same thing? Any advices will be appreciated.

Do you have a pointer to your source?

Are you using set_page_dirty to dirty the pages?

Are you sure you don't have a refcount leak?


  parent reply	other threads:[~2010-06-07  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07  8:34 OOM problem caused by fs Seth Huang
2010-06-07  8:42 ` Boaz Harrosh
2010-06-07  9:53 ` Nick Piggin [this message]
2010-06-07 17:34   ` Seth Huang
2010-06-09  4:01     ` Tao Ma
2010-06-09  8:16       ` Seth Huang

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=20100607095341.GM26335@laptop \
    --to=npiggin@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=seth.hg@gmail.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.