All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Mark Knecht <markknecht@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Inexpensive RAID1 controller for home server?
Date: Mon, 20 Aug 2012 00:17:37 -0500	[thread overview]
Message-ID: <5031C871.8080105@hardwarefreak.com> (raw)
In-Reply-To: <20120820040640.5b4f77ac@natsu>

On 8/19/2012 5:06 PM, Roman Mamedov wrote:
> On Sun, 19 Aug 2012 16:48:41 -0500
> Stan Hoeppner <stan@hardwarefreak.com> wrote:
> 
>> Yeah, you're right.  All Silicon Image ASICs suck.
> 
> "The only generic advice I can give you at this point) is to avoid
> Silicon Image controllers, particularly their SATA controllers.  They
> have a history of causing data corruption on Linux, FreeBSD, and
> Windows, and some have reported other miscellaneous problems with them
> as well."

There is no confirmation of a bug in the 3132 because of all these
issues you quote are board specific.  Known product flaw/failure
statistics dictate there will be thousands of bad cards shipped when the
total chip volume is in the 10s of millions.

So please, stop spreading FUD about SiI chips.  It's fine to have an
opinion and share it.  Just don't back it up with unsubstantiated and
unconfirmed claims.

Simply say what you know to be fact:  Some people have had problems with
some cards containing the SiI 3132.  Don't make the claim that all 3132
chips have a defect when you can't back that statement up with facts.

Thank you.

-- 
Stan


  reply	other threads:[~2012-08-20  5:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 19:18 Inexpensive RAID1 controller for home server? Mark Knecht
2012-08-19  3:20 ` Phil Turmel
2012-08-19  4:09 ` Stan Hoeppner
2012-08-19  9:34   ` Roman Mamedov
2012-08-19 21:48     ` Stan Hoeppner
2012-08-19 22:06       ` Roman Mamedov
2012-08-20  5:17         ` Stan Hoeppner [this message]
2012-08-19 23:59       ` 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=5031C871.8080105@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --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 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.