From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Storage server, hung tasks and tracebacks
Date: Thu, 03 May 2012 07:50:00 -0500 [thread overview]
Message-ID: <4FA27EF8.6040002@hardwarefreak.com> (raw)
In-Reply-To: <20120502184450.GA2557@nsrc.org>
On 5/2/2012 1:44 PM, Brian Candler wrote:
> I have a really wierd problem with storage. The one thing that I *can* see
> is dmesg output giving messages about hung tasks and XFS call tracebacks, so
> I'm posting here in the hope that someone can help me interpret them - even
> if only to say "this definitely means that your disks are not responding"
> would be very helpful.
...
> Any other suggestions (and of course interpretation of the kernel call
> tracebacks) would be much appreciated.
Which mainboards are these Brian? Make/model?
Make/model/count of all add in cards?
Make/model of PSU?
Make model of chassis?
I'll sleuth around and see what I can find. Could be some obscure
expansion card interaction. Could be undersized PSUs or lack of
backplanes spread evenly across the 12v rails of a multi-rail PSU, etc, etc.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-03 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:44 Storage server, hung tasks and tracebacks Brian Candler
2012-05-03 12:50 ` Stan Hoeppner [this message]
2012-05-03 20:41 ` Brian Candler
2012-05-03 22:19 ` Stan Hoeppner
2012-05-04 16:32 ` Brian Candler
2012-05-04 16:50 ` Stefan Ring
[not found] ` <4FA4C321.2070105@hardwarefreak.com>
2012-05-06 8:47 ` Brian Candler
2012-05-15 14:02 ` Brian Candler
2012-05-20 16:35 ` Brian Candler
2012-05-22 13:14 ` Brian Candler
2012-05-20 23:59 ` Dave Chinner
2012-05-21 9:58 ` Brian Candler
2012-09-09 9:47 ` Brian Candler
2012-05-07 1:53 ` Dave 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=4FA27EF8.6040002@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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 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.