public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: David Chinner <dgc@sgi.com>, Linux-Xfs <linux-xfs@oss.sgi.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: xfs [_fsr] probs in 2.6.24.0
Date: Tue, 12 Feb 2008 13:44:07 -0800	[thread overview]
Message-ID: <47B21327.3080502@tlinx.org> (raw)
In-Reply-To: <47B20E84.6020707@sandeen.net>



Eric Sandeen wrote:
> Linda Walsh wrote:
>> David Chinner wrote:
>>> Filesystem bugs rarely hang systems hard like that - more likely is
>>> a hardware or driver problem. And neither of the lockdep reports
>>> below are likely to be responsible for a system wide, no-response
>>> hang.
>> ---
>> 	"Ish", the 32-bitter, has been the only hard-hanger.
> 
> 4k stacks?
----
	But but but...almost from the day they were introduced.  And
these are more recent probs. Has stack usage increased for some reason,
:-(.  I do have the option to detect stack-overflow turned on as well
-- guess it doesn't work so well?

	If they are that problematic, maybe selecting xfs as a config
option should force 8k stacks (ugly solution, but might eliminate
some lost hair (from pulling it out) for end users....?

	Guess I should go back to 8k's for now...seems odd that it'd
pop up now, but maybe it's the xtra NFS loading?  Sigh.

  reply	other threads:[~2008-02-12 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  1:02 xfs [_fsr] probs in 2.6.24.0 Linda Walsh
2008-02-12  8:58 ` David Chinner
2008-02-12 21:02   ` Linda Walsh
2008-02-12 21:24     ` Eric Sandeen
2008-02-12 21:44       ` Linda Walsh [this message]
2008-02-12 21:54         ` Eric Sandeen
2008-02-12 21:59     ` David Chinner

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=47B21327.3080502@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sandeen@sandeen.net \
    /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