From: Emmanuel Florac <eflorac@intellique.com>
To: Shawn Usry <shawn@dolphinlogic.com>
Cc: xfs@oss.sgi.com
Subject: Re: Interesting possible XFS crash condition
Date: Wed, 20 Oct 2010 11:54:46 +0200 [thread overview]
Message-ID: <20101020115446.5d606b44@harpe.intellique.com> (raw)
In-Reply-To: <4CBE887F.6020506@dolphinlogic.com>
Le Wed, 20 Oct 2010 01:13:19 -0500
Shawn Usry <shawn@dolphinlogic.com> écrivait:
> The latter statement and observations lead me to believe that perhaps
> this was simply a yucky controller that was failing under heavy
> I/O.
I've set up quite a lot of those RAID cards (about 100) and there is a
significant failure rate on these (much higher than the newer 9650). I
had both cases of bad controller RAM and CPU overheating several times.
Try unmounting the filesystem and start a RAID verify:
tw_cli /cX/uY start verify
This will generate high IO. Check dmesg for controller errors. Try
remounting after a couple of hours of verification. If the controller
is fried, it most probably fail, but shouldn't crash the system.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-10-20 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 6:13 Interesting possible XFS crash condition Shawn Usry
2010-10-20 8:12 ` Michael Monnerie
2010-10-20 19:01 ` Shawn Usry
2010-10-20 21:27 ` Emmanuel Florac
2010-10-21 4:45 ` Shawn Usry
2010-10-21 6:06 ` Dave Chinner
2010-10-20 9:54 ` Emmanuel Florac [this message]
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=20101020115446.5d606b44@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=shawn@dolphinlogic.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