From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_check segfault / xfs_repair I/O error
Date: Mon, 16 Apr 2012 05:18:53 -0500 [thread overview]
Message-ID: <4F8BF20D.9080205@hardwarefreak.com> (raw)
In-Reply-To: <20120415223106.GU6734@dastard>
On 4/15/2012 5:31 PM, Dave Chinner wrote:
> On Sun, Apr 15, 2012 at 11:15:09PM +1000, Drew Wareham wrote:
>> cciss 0000:04:00.0: cciss: c ffff810037e00000 has CHECK CONDITION sense
>> key = 0x3
>
> This is clearly a raid array error....
https://bugzilla.redhat.com/show_bug.cgi?id=722780
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/DL180-G5-showing-hard-drive-error-messages/td-p/4771517
http://h30499.www3.hp.com/t5/General/i-o-error-linux-DL380G5/td-p/4772829
Not sure if these are relevant Drew but I'm posting them just in case.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-16 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 13:15 xfs_check segfault / xfs_repair I/O error Drew Wareham
2012-04-15 19:47 ` Stan Hoeppner
2012-04-15 22:31 ` Dave Chinner
2012-04-16 10:18 ` Stan Hoeppner [this message]
2012-04-20 4:11 ` Drew Wareham
2012-04-20 15:06 ` Eric Sandeen
2012-04-20 15:46 ` Drew Wareham
2012-04-20 17:01 ` Eric Sandeen
2012-04-21 0:57 ` Drew Wareham
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=4F8BF20D.9080205@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.