linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Fairbairn" <steve@fairbairn-family.com>
To: linux-raid@vger.kernel.org
Subject: Any inexpensive hardware recommendations for PCI interface cards?
Date: Fri, 8 Feb 2008 11:21:01 -0000	[thread overview]
Message-ID: <11ae01c86a44$aff357a0$0603a8c0@meanmachine> (raw)


Hi All,

I currently have a couple of IT8212 PCI ATA RAID (1, 0 ot 1+0) cards
which Linux RAID doesn't seem to like too well.  Initially I tried
creating an array out of 4 disks on the 4 primaries over the 2 cards.
Although this seemed to work, the access performance was impossibly low
and I never actually got to the point of leaving it for a week to build
the array.

Since then, I have striped 2 of the drives (just primaries again and
known to be good drives) on a single card using the cards own striping
capability.  This striped drive, I've that added to my RAID 5 array as a
500GB single disk.

The grow into this disk worked fine as did the resize2fs.  As soon as I
tried to copy data onto the array, the system marked the  disk as
faulty.  Now currently I'm running a degraded array anyway as I'm
waiting for the replacement of the drive that failed with bad sectors
when I initially started the grow. So I had to use assemble --force to
get the md device back online.  I've not mounted it since. (I know it's
wise not to use the drive while it's degraded, but if I can get the data
off of a 320GB HD, then I can stripe that with another disk on the other
ITE card, and add in a spare to the array).

Can anyone see any issues with what I'm trying to do?
Are there any known issues with IT8212 cards (They worked as straight
disks on linux fine)?
Is anyone using an array with disks on PCI interface cards?
Is there an issue with mixing motherboard interfaces and PCI card based
ones?
Does anyone recommend any inexpensive (probably SATA-II) PCI interface
cards?

The motherboard has run out of sensible interfaces (I'm not using both
primary and secondary in an array on IDE), but I'd still like the
capacity to grow my array further.

Thanks again for the help.

Steve.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.21/1265 - Release Date:
07/02/2008 11:17
 


             reply	other threads:[~2008-02-08 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 11:21 Steve Fairbairn [this message]
2008-02-08 11:47 ` Any inexpensive hardware recommendations for PCI interface cards? Tim Southerwood
2008-02-08 12:56 ` Bill Davidsen
2008-02-08 13:54   ` Justin Piszcz
2008-02-08 19:01     ` Iustin Pop
2008-02-08 19:24       ` Justin Piszcz
2008-02-08 19:38         ` Iustin Pop
2008-02-08 19:40           ` Justin Piszcz
2008-02-08 21:27             ` Jeff Breidenbach

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='11ae01c86a44$aff357a0$0603a8c0@meanmachine' \
    --to=steve@fairbairn-family.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;
as well as URLs for NNTP newsgroup(s).