From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Intel(R) C600 SAS Controller
Date: Wed, 11 Jun 2014 11:41:32 +0100 [thread overview]
Message-ID: <5398325C.5060804@thegeezer.net> (raw)
In-Reply-To: <539830A8.4090500@xunil.at>
On 06/11/2014 11:34 AM, Stefan G. Weichinger wrote:
> Am 11.06.2014 12:14, schrieb thegeezer:
>
>>> Basically 3 RAID-6 hw-raids over 6 SAS hdds.
>> OK so i'm confused again. RAID6 requires minimum of 4 drives.
>> if you have 3 raid6's then you would need 12 drives (coffee hasn't quite
>> activated in me yet so my maths may not be right)
>> or do you have essentially the first part of each of the six drives be
>> virtual disk 1, the second part of each of the six drives virtual disk 2
>> and the third part be virtual disk 3 -- if this is the case bear in mind
>> that the slowest part of the disk is the end of the disk -- so you are
>> essentially hobbling your virtual disk3 but only a little, instead of
>> being around 150MB/sec it might run at 80.
>
> I'd be happy to see 80 !
>
> Ran atop now while dd-ing stuff to an external disk and got ~1MB/s for
> 2.5GB of data.
>
> (this is even too slow for USB ...)
>
> I am unsure what to post here from atop ... ?
>
>
> To the initial question:
>
> Yes, imagine the six disks "split" or partitioned at the level of the
> hardware raid controller (as you described above).
>
>> you might also like to try a simple test of the following (yes lvs count
>> as block devices)
>> # hdparm -t /dev/sda
>> # hdparm -t /dev/sdb
>> # hdparm -t /dev/sdc
>> # hdparm -t /dev/vg01/winserver_disk0
>> # hdparm -t /dev/vg01/amhold
> everything around 380 MB/s ... only ~350 MB/s for
> /dev/vg01/winserver_disk0 (which still is nice)
OK here is the clue.
if the LVs are also showing such fast speed, then please can you show
your command that you are trying to run that is so slow ?
next prev parent reply other threads:[~2014-06-11 10:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 7:52 [gentoo-user] Intel(R) C600 SAS Controller Stefan G. Weichinger
2014-05-24 19:24 ` Stefan G. Weichinger
2014-05-26 17:47 ` Stefan G. Weichinger
2014-05-26 19:57 ` Stefan G. Weichinger
2014-05-27 13:03 ` Stefan G. Weichinger
2014-06-10 19:57 ` Stefan G. Weichinger
2014-06-10 20:02 ` Stefan G. Weichinger
2014-06-10 22:27 ` Stefan G. Weichinger
2014-06-11 8:47 ` Stefan G. Weichinger
2014-06-11 9:19 ` thegeezer
2014-06-11 9:34 ` Stefan G. Weichinger
2014-06-11 10:14 ` thegeezer
2014-06-11 10:27 ` thegeezer
2014-06-11 10:34 ` Stefan G. Weichinger
2014-06-11 10:41 ` thegeezer [this message]
2014-06-11 10:49 ` Stefan G. Weichinger
2014-06-11 11:01 ` thegeezer
2014-06-11 11:20 ` Stefan G. Weichinger
2014-06-11 11:18 ` thegeezer
2014-06-11 11:21 ` Stefan G. Weichinger
2014-06-11 11:52 ` thegeezer
2014-06-11 12:41 ` Stefan G. Weichinger
2014-06-11 13:32 ` thegeezer
2014-06-11 13:44 ` Stefan G. Weichinger
2014-06-11 14:15 ` Stefan G. Weichinger
2014-06-11 14:18 ` thegeezer
2014-06-11 14:38 ` Stefan G. Weichinger
2014-06-11 18:57 ` Stefan G. Weichinger
2014-06-11 20:17 ` thegeezer
2014-06-12 8:15 ` Stefan G. Weichinger
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=5398325C.5060804@thegeezer.net \
--to=thegeezer@thegeezer.net \
--cc=gentoo-user@lists.gentoo.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