linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: Roman Mamedov <rm@romanrm.ru>, Steven Haigh <netwiz@crc.id.au>,
	linux-raid@vger.kernel.org
Subject: Re: Recommended pci-e 1x SATA cards.
Date: Sun, 17 Apr 2011 13:36:52 -0500	[thread overview]
Message-ID: <4DAB3344.2090502@hardwarefreak.com> (raw)
In-Reply-To: <4DAA7E46.6040309@fnarfbargle.com>

Brad Campbell put forth on 4/17/2011 12:44 AM:

> Hells bells, there is even a case that Roman pointed to where the
> precise controller you recommend as being of suitable quality
> demonstrates the exact fault we are talking about, and you try to blame
> the copy program or the Windows driver.
> 
> There appears to be an insidious flaw in these chips that only manifests
> itself under "perfect storm" conditions, but when it does it silently
> eats your data.

I've been in the hardware game a long time, and all the evidence I'm
seeing WRT this silent data corruption issue points simply to QC, not a
chip design flaw.  If the problem were a chip design flaw, we'd see far
more widespread reporting, as millions of this chip have shipped into
the marketplace.

The fact that the Russian with 5 cards purchased in Dubai could
routinely demonstrate this problem with 2 of 5 identical cards, and
never on the other 3, points directly to a board QC isue.  Again, if the
problem were a design flaw in the IC itself, all 5 cards would have
exhibited the problem.

-- 
Stan

  reply	other threads:[~2011-04-17 18:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 10:31 Recommended pci-e 1x SATA cards Steven Haigh
2011-04-14 10:54 ` Roman Mamedov
2011-04-14 11:05   ` Tapani Tarvainen
2011-04-14 11:25     ` Roman Mamedov
2011-04-14 11:41       ` Tapani Tarvainen
2011-04-14 12:02         ` Roman Mamedov
2011-04-14 11:14   ` Steven Haigh
2011-04-14 19:37   ` Stan Hoeppner
2011-04-15  1:54     ` Brad Campbell
2011-04-15  5:03     ` Roman Mamedov
2011-04-14 12:53 ` Roman Mamedov
2011-04-14 13:16   ` Steven Haigh
2011-04-14 19:55     ` Stan Hoeppner
2011-04-14 23:50       ` Steven Haigh
2011-04-15  4:06         ` Stan Hoeppner
2011-04-15  4:35           ` Steven Haigh
2011-04-15  4:56             ` Stan Hoeppner
2011-04-15  4:58       ` Roman Mamedov
2011-04-15 21:31         ` Stan Hoeppner
2011-04-16  5:15           ` Roman Mamedov
2011-04-16  8:57             ` Brad Campbell
2011-04-16 20:40               ` Stan Hoeppner
2011-04-17  5:44                 ` Brad Campbell
2011-04-17 18:36                   ` Stan Hoeppner [this message]
2011-04-17 18:45                     ` Mikael Abrahamsson
2011-04-17 20:26                       ` Stan Hoeppner
2011-04-17 21:18                         ` Sven Eschenberg
2011-04-17 21:25                     ` Guy Watkins
2011-04-17 23:29                     ` Brad Campbell

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=4DAB3344.2090502@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=netwiz@crc.id.au \
    --cc=rm@romanrm.ru \
    /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).