From: Eric Sandeen <sandeen@sandeen.net>
To: Jay Sullivan <jpspgd@rit.edu>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
Date: Wed, 14 Nov 2007 21:26:13 -0600 [thread overview]
Message-ID: <473BBC55.7050804@sandeen.net> (raw)
In-Reply-To: <06CCEA2EB1B80A4A937ED59005FA855101AED622@svits26.main.ad.rit.edu>
Jay Sullivan wrote:
> Of course this had to happen one more time before my scheduled
> maintenance window... Anyways, here's all of the good stuff I
> collected. Can anyone make sense of it? Oh, and I upgraded to xfsprogs
> 2.9.4 last week, so all output you see is with that version.
>
Forgot to ask, are you running w/ 4k stacks?
And/or, do you have stack usage debugging enabled? That's quite a
backtrace you've got there... just a shot in the dark.
-Eric
next prev parent reply other threads:[~2007-11-15 3:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 20:06 xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c Jay Sullivan
2007-11-02 2:14 ` Eric Sandeen
2007-11-02 2:22 ` Jay Sullivan
2007-11-02 2:30 ` Eric Sandeen
2007-11-02 9:07 ` Ralf Gross
2007-11-02 16:10 ` Eric Sandeen
2007-11-02 14:00 ` Jay Sullivan
2007-11-02 14:49 ` Jay Sullivan
2007-11-14 15:05 ` Jay Sullivan
2007-11-15 3:26 ` Eric Sandeen [this message]
2007-11-02 4:37 ` Timothy Shimmin
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 2:08 Jay Sullivan
2007-11-02 5:18 ` David Chinner
[not found] <B3EDBE0F860AF74BAA82EF17A7CDEDC660BE05A3@svits26.main.ad.rit.edu>
2007-12-21 2:01 ` Jay Sullivan
2008-01-03 15:55 ` Jay Sullivan
2008-08-04 16:55 ` Richard Freeman
2009-02-24 13:04 Federico Sevilla III
2009-02-24 22:46 ` Dave Chinner
2009-02-25 10:00 ` Federico Sevilla III
2009-02-25 11:51 ` Michael Monnerie
2009-02-25 18:47 ` Federico Sevilla III
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=473BBC55.7050804@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jpspgd@rit.edu \
--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