public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Chris Allen <chris@cjx.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS stack space crashes - current status?
Date: Wed, 02 Aug 2006 13:59:38 -0500	[thread overview]
Message-ID: <44D0F61A.5070200@sandeen.net> (raw)
In-Reply-To: <44D0A296.9020307@cjx.com>

Chris Allen wrote:

> So..... questions:
> 
> 1. How much is known about this problem? Seeing as it is 100% reproducible,
> is there any active development underway to fix it?

XFS is a lot less stack-heavy than it used to be, but if you put enough 
IO code between sys_write and your disks, it can all add up to a problem.

> 2. I have seen postings that say compiling a kernel with 8K stacks will 
> fix the
> problem. Is this the case? Or will I be able to trigger it again by 
> running 100 or
> 200 simultaneous writes?

More threads probably won't matter.

> 3. Any suggestions as to what I should try? At present it looks like I 
> am stuck between
> finding a fix for XFS and splitting the box into 2 or 3 EXT3 partitions 
> (which I really don't
> want to do). I have tried ReiserFS (max FS size is 8TB even though the 
> FAQ says 16), and
> JFS (jfs_fsck segfaults which doesn't fill me with confidence).

If you can run w/ 8k stacks you will probably be in better shape.

If you want to do a bit of testing, go into do_IRQ() and change the 
warning threshold (STACK_WARN) to something slightly bigger, so that 
you'll get the warning message earlier, and you should also get a 
backtrace that tells you how you got there.

-Eric

> 
> Many thanks for any suggestions,
> 
> Chris Allen.
> 
> 
> 
> 

  reply	other threads:[~2006-08-02 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 13:03 XFS stack space crashes - current status? Chris Allen
2006-08-02 18:59 ` Eric Sandeen [this message]
2006-08-02 21:32 ` Russell Cattelan

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=44D0F61A.5070200@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=chris@cjx.com \
    --cc=linux-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