From: Maarten Vanraes <maarten@ba.be>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: megaraid_sata vs megasr
Date: Wed, 28 May 2008 18:31:25 +0200 [thread overview]
Message-ID: <200805281831.26066.maarten@ba.be> (raw)
In-Reply-To: <0631C836DBF79F42B5A60C8C8D4E8229010EF1F5@NAMAIL2.ad.lsil.com>
Op Wednesday 28 May 2008 17:44:50 schreef Moore, Eric:
> On Wednesday, May 28, 2008 8:18 AM, Maarten Vanraes wrote:
> > So in effect, you are telling me that we bought fakeraid
> > cards... since this
> > is the "recommended driver"? is the card a hardware raid? or software.
> >
> > We had specifically asked for hardware raid... :-(
>
> I worked on megaraid team some five years ago, now I work on mpt fusion.
> I can't tell you what the recommended megaraid cards, as they have
> changed since then from U320. The mpt fusion cards come with Raid
> levels 0, 1, and 1 enhanced, which is implemented in hardware/firmware.
>
>
> You could try looking here:
> http://www.lsi.com/storage_home/products_home/internal_raid/index.html
i think it's this one:
http://www.lsi.com/storage_home/products_home/internal_raid/megaraid_sas/megaraid_sas_8208elp/index.html
in any case: LSI support site directs me to the megasr driver for my card. But
there is something wrong in either case:
on machine 2: i did an rsync from machine A array 2 to machine B array 2 (SATA
disks of 1T in raid 1): speed is around 20MB/s probably due to load on
machine A, or whatever (machine B has nothing running whatsoever.)
hdparm -tT /dev/sdb shows between 50 and 80MB/s
the moment i do an scp or rsync from something else, the first rsync drops
immediately to around 5MB/s, while the second doesn't do more than 5MB/s
(often one would show around 2MB/s.)
at that time, the iowait (dual quad core) is above 90% ...
Since both identical machines behave in the same matter, i believe there is
something seriously wrong with the megasr driver in the first place, and
tried to get support, but they request me to supply a serial number of the
card. (Both machines are already running in a colocation room).
I had to patch it to work with 2.6.21, i'm wondering if i did anything stupid
in the patch. can you check that maybe? (it's a small patch)
on the other hand, if there is an driver that works well, but just needs a
little work, i'll be happy to test this out.
I'm just not a kernel devel, and don't really know how to solve this.
the problem is just that i want to be helped one way or another.
IF in your opinion the cards are not the best solution and i would have to
upgrade it, i can do that; but i suspect the megasr driver.
am i wrong in my thinking?
Sincerely,
Maarten
prev parent reply other threads:[~2008-05-28 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 8:05 megaraid_sata vs megasr Maarten Vanraes
2008-05-26 17:11 ` Jeff Garzik
2008-05-27 9:55 ` Maarten Vanraes
2008-05-27 20:32 ` Moore, Eric
2008-05-28 14:17 ` Maarten Vanraes
2008-05-28 15:44 ` Moore, Eric
2008-05-28 16:31 ` Maarten Vanraes [this message]
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=200805281831.26066.maarten@ba.be \
--to=maarten@ba.be \
--cc=Eric.Moore@lsi.com \
--cc=jeff@garzik.org \
--cc=linux-scsi@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 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.