From: Roman Mamedov <rm@romanrm.ru>
To: stan@hardwarefreak.com
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 04:06:40 +0600 [thread overview]
Message-ID: <20120820040640.5b4f77ac@natsu> (raw)
In-Reply-To: <50315F39.2030404@hardwarefreak.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
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."
http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/185065.html
> Roman has a beef with SiI. It's unfounded and unsubstantiated
"I've had problems with XFS and EXT4 over the md device driver that turned out
to be a bug in the Silicon Image 3132 chipset. It quietly corrupts data."
-- https://bbs.archlinux.org/viewtopic.php?id=115128
"...Sil3132 2-port SATA-card which couldn't handle heavy load on both ports.
Single port was fine, so preclear did not reveal any problems. I have one
working and one non-working coming from the same supplier and looking almost
exactly the same so it would be impossible to know before hand which card
make/model might cause problems. In this case random read errors were produced
for the two attached disks."
-- http://lime-technology.com/forum/index.php?topic=21052.0
"This might be the Sil3132 itself that's creating the problem. It's somewhat
notorious for corrupting data under high IO pressure. It's trivially easy to
trigger if you're using both ports at the same time, but I've seen similar
data corruption with just one port under active use."
-- http://arstechnica.com/civis/viewtopic.php?f=11&t=37779&start=1880
"There are confirmed problems within certain models of their SATA controllers
which cause silent data corruption and other issues, affecting Linux, FreeBSD,
and Windows. ... I'm not even willing to trust later revisions like the 3124;
not catching data corruption during QA/testing is simply unacceptable
regardless of what "class" of product it is. I would be very surprised to
hear someone advocate use of Silicon Image controllers after reading the
above."
-- http://comments.gmane.org/gmane.os.freebsd.devel.hardware/6624
Etc, etc, etc. And here on this list:
http://comments.gmane.org/gmane.linux.raid/30629
> Believe who you wish.
Can fully agree with this. :)
--
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 --]
next prev parent reply other threads:[~2012-08-19 22:06 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 [this message]
2012-08-20 5:17 ` Stan Hoeppner
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=20120820040640.5b4f77ac@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=stan@hardwarefreak.com \
/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).