From: Spelic <spelic@shiftmail.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs delaylog hanged up
Date: Wed, 24 Nov 2010 01:58:25 +0100 [thread overview]
Message-ID: <4CEC6331.3080300@shiftmail.org> (raw)
In-Reply-To: <20101123204609.GW22876@dastard>
On 11/23/2010 09:46 PM, Dave Chinner wrote:
> Hmmmm. We get plenty of reports about problems with 3ware RAID
> controllers, many of which are RAID controller problems. Can you
> make sure you are running the latest firmware on the controller?
>
No, sorry, my firmware is: FE9X 4.06.00.004
But when controllers hang, there is usually something in dmesg, and in
my case there wasn't. Then after a while it resets (it has something
like a watchdog in it).
In the past during testing I did have reproducible hangups on high load
with these controllers (seemed like a lost interrupt), but they were
fixed by disabling NCQ.
The controller would reset in those cases, drives caches would reset to
"off", and there were entries in dmesg.
But that issue was definitely fixed by disabling NCQ: I tested many
times with and without NCQ with reproducible results; and after that we
had reliable operation for more than 1 year on that machine.
> I've been unable to reproduce the problem with your test case (been
> running over night) on a 12-disk, 16TB dm RAID0 array, but I'll keep
> trying to reproduce it for a while.
It seems to me that 12 disk raid0 dm is quite different from 16 disk md
raid5 array because you don't have the stripe cache and there are likely
to be fewer in-flight operations, if it was a pool of something which
was drained you might not hit it... But I understand that you had the
raid0 array already up :-D I'll see if I can reproduce this but I can't
guarantee: the machine should go back to production very soon.
If I hit it again, what should I look at?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-24 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 19:27 Xfs delaylog hanged up Spelic
2010-11-22 23:29 ` Dave Chinner
2010-11-23 11:17 ` Spelic
2010-11-23 13:28 ` Spelic
2010-11-23 20:46 ` Dave Chinner
2010-11-23 22:14 ` Stan Hoeppner
2010-11-24 0:20 ` Dave Chinner
2010-11-24 13:12 ` Spelic
2010-11-24 21:50 ` Dave Chinner
2010-11-23 22:48 ` Emmanuel Florac
2010-11-24 0:36 ` Spelic
2010-11-24 1:40 ` Stan Hoeppner
2010-11-24 6:18 ` Michael Monnerie
2010-11-24 7:44 ` Emmanuel Florac
2010-11-24 0:58 ` Spelic [this message]
2010-11-24 5:44 ` Dave Chinner
2010-11-25 23:34 ` Spelic
2010-11-26 4:20 ` Dave Chinner
2010-11-24 22:52 ` Spelic
2010-11-26 22:43 ` Spelic
-- strict thread matches above, loose matches on Subject: below --
2010-11-24 4:03 Richard Scobie
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=4CEC6331.3080300@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox