From: Roman Mamedov <rm@romanrm.net>
To: Another Sillyname <anothersname@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mixed controllers on JBOD Raid 6?
Date: Thu, 2 Jul 2015 00:14:40 +0500 [thread overview]
Message-ID: <20150702001440.2d391587@natsu> (raw)
In-Reply-To: <CAOS+5GFJQ10z-VV=06ncxh+wb=ycq9HrHJfJD++y8z8qGnoOrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
On Wed, 1 Jul 2015 19:27:11 +0100
Another Sillyname <anothersname@googlemail.com> wrote:
> I'm looking at an Asus Maximus Vii Gene motherboard which has 8 SATA
> controller connectors.....6 Intel and 2 other (can't remember at the
> moment).
>
> Are there any projected issues or concerns about making a 8 Drive
> RAID6 array where I'm using mixed controllers?
Mixing controllers in general -- no issue whatsoever, that's the beauty of the
(Linux) software RAID.
In cases like yours, there could be a minor performance hit if the additional
2-port controller gets fed only a single-lane of PCI-E 1.0. If so, this will
cap the total throughput of both ports combined to less than 250 MB/sec.
However on the motherboard that you specified that controller is ASMedia
ASM1061 which supports PCI-E 1x 2.0. And if the chipset really provides a 2.0
port to it (not an expert in Intel chipsets, check the datasheets), then the
cap would be 500 MB/sec, which should be more than enough for two regular
spinning hard drives.
In any case, typically with RAID6 setups like these getting the highest
possible sequential read/write performance isn't on top of the priorities
list, so the above may not even be a concern for you.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-07-01 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 18:27 Mixed controllers on JBOD Raid 6? Another Sillyname
2015-07-01 19:06 ` Roger Heflin
2015-07-01 19:14 ` Roman Mamedov [this message]
2015-07-02 19:41 ` John Stoffel
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=20150702001440.2d391587@natsu \
--to=rm@romanrm.net \
--cc=anothersname@googlemail.com \
--cc=linux-raid@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