public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: simon@thekelleys.org.uk
Cc: xfs@oss.sgi.com
Subject: Re: XFS stack overflow?
Date: Thu, 31 Mar 2011 10:37:10 -0400	[thread overview]
Message-ID: <20110331143710.GA12821@infradead.org> (raw)
In-Reply-To: <1301581135.748149.10230.nullmailer@thekelleys.org.uk>

On Thu, Mar 31, 2011 at 03:18:55PM +0100, simon@thekelleys.org.uk wrote:
> x86_64
> Storage is fibrechannel attached and the filesystem is hosted on a 
> LVM block device that concatentates four partitions, so the block access
> is going via a stack of LVM, multipath and Q-logic drivers.
> Network is Intel 10G ethernet (gxbe driver)
> Kernel is 2.6.32 with Debian patches. (both kernels)

Yes, this very much looks like a stack overflow caused by direct
reclaim from a context with a lot of stack usage into a filesystem (XFS
in this case) with a deep storage stack underneath.

The fix for this is to disable direct reclaim, which the VM maintainers
refuse.  We finally gave in and added a hack similar to the other
modern filesystems to prevent this from inside XFS.

Try backporting commits:

	"xfs: skip writeback from reclaim context"

and

	"xfs: allow writeback from kswapd"

from current mainline to avoid these kinds of issues.

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

      reply	other threads:[~2011-03-31 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 14:18 XFS stack overflow? simon
2011-03-31 14:37 ` Christoph Hellwig [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=20110331143710.GA12821@infradead.org \
    --to=hch@infradead.org \
    --cc=simon@thekelleys.org.uk \
    --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