From: Eero Volotinen <eero.volotinen@iki.fi>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: mptsas and mptbase sas problems on fujitsu-siemens rx200-s3 rack server
Date: Fri, 22 Aug 2008 17:46:20 +0300 [thread overview]
Message-ID: <48AED13C.7080106@iki.fi> (raw)
In-Reply-To: <1219414589.3339.8.camel@localhost.localdomain>
> The first thing to note is that HBA based hardware RAID is not something
> anyone should enable blindly. The fusion isn't even a dedicated RAID
> card, so its RAID engine is effectively jammed into left over firmware
> space because it was available (HP, for instance, required this
> capability to be removed on some of the HP OEM models).
>
> Even for dedicated hardware RAID, the problem you have is that it
> effectively puts the onboard processor in the direct I/O path. Since
> cards are (reasonably) cheap, these processors don't have the fastest
> busses or highest processing capabilities, and often top out at
> surprisingly low bandwidths, especially for compute intensive
> transactions like RAID-5/RAID-6.
Mainly this internal sas array (2*73GB 10k sas disks) is used for
operating system only. Currently I am running it on raid1
After weekend I can try to run it without hardware acceleration,
it mainly makes installing operating system a bit harder.
So, this looks like that I need to buy working sas raid controller,
if I want to use hardware raid on this machine? Rest of data is on
fibrechannel san and it is working fine.
--
Eero
next prev parent reply other threads:[~2008-08-22 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 11:07 mptsas and mptbase sas problems on fujitsu-siemens rx200-s3 rack server Eero Volotinen
2008-08-22 14:16 ` James Bottomley
2008-08-22 14:46 ` Eero Volotinen [this message]
2008-08-22 14:56 ` Moore, Eric
2008-08-25 8:18 ` Heusmann, Heino
2008-08-25 9:00 ` eerov
2008-08-25 9:10 ` Martin Wilck
2008-08-25 9:41 ` eerov
2008-08-26 13:59 ` (SOLVED) " Eero Volotinen
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=48AED13C.7080106@iki.fi \
--to=eero.volotinen@iki.fi \
--cc=James.Bottomley@HansenPartnership.com \
--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.