From: Tejun Heo <teheo@suse.de>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: nonzero mismatch_cnt with no earlier error
Date: Tue, 06 Mar 2007 01:00:51 +0900 [thread overview]
Message-ID: <45EC3EB3.10407@suse.de> (raw)
In-Reply-To: <45EBCC43.9010709@eyal.emu.id.au>
Eyal Lebedinsky wrote:
> It is in the original thread on linux-raid, but here it is for this list.
> This is the full dmesg. There were only MARKs in between.
>
> I run a raid 'check' every Friday (cron). The last one reported some parity errors.
>
> *** last week check start:
> [927080.617744] md: data-check of RAID array md0
> [927080.630783] md: minimum _guaranteed_ speed: 24000 KB/sec/disk.
> [927080.648734] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
> [927080.678103] md: using 128k window, over a total of 312568576 blocks.
> *** last week error:
> [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)
I need full kernel log including the boot messages so that I can tell
which controller/driver is involved here and also the result of 'hdparm
-I /dev/sdX' of your drives would be nice.
BTW, this is SMART read log for page 09 which is SMART self-test log.
The device aborted it. Dunno who issued it or why it got aborted. As I
wrote in the previous mail, EH discovered that SError has accumulated
link level errors and thus treated it as ATA bus error. All
transmissions over SATA are checksummed and link errors supposedly don't
cause data corruption, so, in theory, the above error message should be
irrelevant to your problem.
Ah.. please also post the result of 'smartctl -d ata -a /dev/sdX' for
your drives. That might reveal something.
--
tejun
next prev parent reply other threads:[~2007-03-05 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DF859B.2050108@eyal.emu.id.au>
[not found] ` <Pine.LNX.4.64.0702231929380.31611@p34.internal.lan>
[not found] ` <45DF8DE3.2050903@eyal.emu.id.au>
[not found] ` <17890.25524.465403.130119@notabene.brown>
2007-02-26 8:18 ` nonzero mismatch_cnt with no earlier error Eyal Lebedinsky
2007-03-05 4:00 ` Tejun Heo
2007-03-05 7:52 ` Eyal Lebedinsky
2007-03-05 16:00 ` Tejun Heo [this message]
2007-03-05 22:01 ` Eyal Lebedinsky
2007-03-09 12:36 ` Tejun Heo
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=45EC3EB3.10407@suse.de \
--to=teheo@suse.de \
--cc=eyal@eyal.emu.id.au \
--cc=linux-ide@vger.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 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).