From: Tejun Heo <htejun@gmail.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: help with PMP failures
Date: Wed, 18 Nov 2009 17:33:23 +0900 [thread overview]
Message-ID: <4B03B153.8050507@gmail.com> (raw)
In-Reply-To: <20091118074145.GA24488@merlins.org>
Hello,
11/18/2009 04:41 PM, Marc MERLIN wrote:
> Didn't know about -a, good call.
> Yep, they do and the times are about consistent with the raid going down
>
> Not sure if the last 5 errors are enough to give a good clue, or not.
>
> If I can't quite figure it out, I'll just pop in a 16 port adaptec sata
> board I recently picked up. It'll take PMP out of the equation if I truly
> have drives returning read / write errors that don't quite seem to show up
> in smart yet.
>
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 84 51 00 46 59 70 44
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 61 08 00 3f 59 70 40 08 13d+19:41:56.500 WRITE FPDMA QUEUED
All the loggedcommands are write but the one which triggered the
failure was read. Error value of 0x84 indicates ICRC and ABORT, so
all the logged commands were failed due to transmission failure from
the host. Hmmm....
--
tejun
next prev parent reply other threads:[~2009-11-18 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091116184242.GA22250@merlins.org>
[not found] ` <20091116184853.GA23126@merlins.org>
[not found] ` <4B0238EC.6060803@kernel.org>
2009-11-17 17:39 ` help with PMP failures Marc MERLIN
2009-11-18 4:03 ` Tejun Heo
2009-11-18 7:41 ` Marc MERLIN
2009-11-18 8:33 ` Tejun Heo [this message]
2009-11-18 18:29 ` Marc MERLIN
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=4B03B153.8050507@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=marc@merlins.org \
--cc=tj@kernel.org \
/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.