From: Tejun Heo <teheo@suse.de>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: Neil Brown <neilb@suse.de>,
linux-raid list <linux-raid@vger.kernel.org>,
list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: nonzero mismatch_cnt with no earlier error
Date: Mon, 05 Mar 2007 13:00:47 +0900 [thread overview]
Message-ID: <45EB95EF.9030702@suse.de> (raw)
In-Reply-To: <45E297E5.50303@eyal.emu.id.au>
Eyal Lebedinsky wrote:
> I CC'ed linux-ide to see if they think the reported error was really innocent:
>
> Question: does this error report suggest that a disk could be corrupted?
>
> This SATA disk is part of an md raid and no error was reported by md.
>
> [937567.332751] ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4190002 action 0x2
> [937567.354094] ata3.00: cmd b0/d5:01:09:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in
> [937567.354096] res 51/04:83:45:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Command 0xb0 is SMART. The device failed some subcommand of SMART, so,
no, it isn't related to data integrity, but your link is reporting
recovered data transmission error and PHY ready status changed and some
other conditions making libata EH mark the failure as ATA bus error.
Care to post full dmesg?
--
tejun
next prev parent reply other threads:[~2007-03-05 4:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 0:23 nonzero mismatch_cnt with no earlier error Eyal Lebedinsky
2007-02-24 0:30 ` Justin Piszcz
2007-02-24 0:59 ` Eyal Lebedinsky
2007-02-26 4:36 ` Neil Brown
2007-02-26 5:46 ` Jeff Breidenbach
2007-02-26 8:18 ` Eyal Lebedinsky
2007-03-05 4:00 ` Tejun Heo [this message]
2007-02-24 6:58 ` Eyal Lebedinsky
2007-02-24 9:14 ` Justin Piszcz
2007-02-24 9:37 ` Justin Piszcz
2007-02-24 9:48 ` Jason Rainforest
2007-02-24 9:50 ` Justin Piszcz
2007-02-24 9:59 ` Jason Rainforest
2007-02-24 10:01 ` Justin Piszcz
2007-02-24 11:09 ` Michael Tokarev
2007-02-24 11:12 ` Justin Piszcz
2007-02-25 20:02 ` Bill Davidsen
2007-02-25 18:33 ` Frank van Maarseveen
2007-02-25 19:58 ` Christian Pernegger
2007-02-25 21:07 ` Justin Piszcz
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=45EB95EF.9030702@suse.de \
--to=teheo@suse.de \
--cc=eyal@eyal.emu.id.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).