linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: matt <listy@fastmail.fm>
Cc: linux-raid@vger.kernel.org
Subject: Re: OT: silent data corruption reading from hard drives
Date: Wed, 1 Aug 2012 19:03:18 +0600	[thread overview]
Message-ID: <20120801190318.05d2431e@natsu> (raw)
In-Reply-To: <50191ADE.10809@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Wed, 01 Aug 2012 08:02:38 -0400
matt <listy@fastmail.fm> wrote:

> Quick intro: Last year I was having problems with an md array
> continuously having a mismatch_cnt in the tens of thousands,
> inexplicably.  After a week or two of hardware swapping and such, I
> narrowed it down to bad reads of the hard drive block devices.  I used
> scripts that would repetitively do something like this on all my drives:
>       dd if=/dev/sdk1 bs=1024 count=50000000 |md5sum -b
> Some devices would intermittently get different results.  I ended up
> resolving (?) it by replacing the cheapo (Syba) SATA controller cards
> with other cheapo (Rosewill) ones.  I've been fine for about a year
> since then.

Syba was mentioned in a bad context last time we discussed this here, somewhere
down the thread: http://comments.gmane.org/gmane.linux.raid/33346
I don't remember if you have participated in that discussion, if not, have an
entertaining read. Is your new Rosewill card also Silicon Image based?

> Is silent data corruption like this simply to be expected when using cheap
> commodity hardware?

I'd say no. There are known good and known bad hardware, where both good and
bad is most easily measured by the amount (or lack of) problem reports you hear
or can find. One method to do that is asking a searching engine about "<chip
name> data corruption".

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-08-01 13:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 12:02 OT: silent data corruption reading from hard drives matt
2012-08-01 13:03 ` Roman Mamedov [this message]
2012-08-02  0:56 ` Stan Hoeppner
2012-08-02  1:07   ` Roberto Spadim
2012-08-02  1:14     ` Roberto Spadim
2012-08-02  1:27   ` Adam Goryachev
2012-08-02  1:35     ` Roberto Spadim
2012-08-02  3:23     ` Stan Hoeppner
2012-08-02 13:02     ` Drew
2012-08-02  3:19   ` Roman Mamedov
2012-08-02  7:51     ` Stan Hoeppner
2012-08-02  8:06       ` Roman Mamedov
2012-08-02  9:29         ` Stan Hoeppner
2012-08-02 12:26         ` Iustin Pop
2012-08-02 16:59         ` listy
2012-08-02 17:04           ` Roberto Spadim
2012-08-02 17:13             ` Jeff Johnson
2012-08-02 17:19               ` Roman Mamedov
2012-08-02 17:25                 ` Roberto Spadim
2012-08-02 17:22               ` Roberto Spadim
     [not found]           ` <501AB9D8.1030404@turmel.org>
2012-08-02 18:32             ` listy
2012-08-03 13:36               ` Phil Turmel
2012-08-15 21:55                 ` Peter Grandi
2012-08-16  7:30                   ` Oliver Schinagl
     [not found]                     ` <CABYL=TqU6qvDK-CuFak42iVNj0v4OcvALXOnr=6XLM4HyXfGkw@mail.gmail.com>
2012-08-16 14:33                       ` Roberto Spadim

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=20120801190318.05d2431e@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=listy@fastmail.fm \
    /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).