linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Adaptec 2405 : hardware or software raid?
Date: Mon, 25 May 2009 17:32:01 +0200	[thread overview]
Message-ID: <20090525173201.25dc3f35@hydro.bl.pg.gda.pl> (raw)

Hi,

I've bought the cheap Adaptec 2405 SAS controller for the sole
purpose of using 15k rpm HDDs. It turns out that to expose the HDDs
to the system I must first launch the computer from enclosed CD and
create some logical volumes. Those logical volumes can mix HDDs in
various raid configurations (1,0,10,5) and expose a single
device, eg. /dev/sda from multiple HDDs.

This is the first time when I see the "logical volumes" option
mandatory. I was planning to access the HDDs directly and create
software raid on them with mdadm.

It is possible, however to create ONE logical volume per ONE physical
disc, and then I can use mdadm on them.

But now, having seen this Adaptec software/tool to generate the
hardware raid configurations (and no way around it) I started to
wonder what approach is better?

What do you recommend:

- make one logical volume per disc and use only software raid?
- use Adaptec 2405 hardware raid entirely?
- or do you know some way around the hardware and access the SAS
  discs directly? (is that approach safe?)

What has better linux support (which kernel version), other
considerations, etc...

thanks in advance for your help
-- 
Janek Kozicki

             reply	other threads:[~2009-05-25 15:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 15:32 Janek Kozicki [this message]
2009-05-25 16:52 ` Adaptec 2405 : hardware or software raid? Andrew Burgess
2009-05-25 17:05   ` Upgrading a software RAID Maxime Boissonneault
2009-05-28 13:38     ` Bill Davidsen
2009-05-28 13:44       ` Maxime Boissonneault
2009-05-28 14:05         ` Bill Davidsen
2009-05-28 14:14     ` Robin Hill
2009-05-28 14:32       ` Maxime Boissonneault
2009-05-28 15:08         ` Robin Hill
2009-05-30 18:11           ` Maxime Boissonneault
2009-05-30 19:03             ` Robin Hill
2009-05-30 20:03               ` Maxime Boissonneault
2009-05-30 20:15                 ` Robin Hill
2009-05-30 22:18                   ` Maxime Boissonneault
2009-05-30 22:52                     ` Maxime Boissonneault
2009-06-02 18:23                     ` Bill Davidsen
2009-06-02 18:32                       ` Thomas Fjellstrom
2009-06-02 19:57                         ` Bill Davidsen
2009-06-02 20:03                           ` Thomas Fjellstrom
2009-06-02 21:13                           ` CoolCold
2009-06-03 16:30                             ` Bill Davidsen
2009-05-29  8:58         ` Keld Jørn Simonsen
2009-05-30 18:32         ` Bill Davidsen
2009-05-30 18:35           ` Maxime Boissonneault
2009-05-30 19:10             ` Robin Hill
2009-05-30 22:39             ` Bill Davidsen
2009-05-31  0:17             ` Keld Jørn Simonsen
2009-05-31  5:21               ` Maxime Boissonneault
2009-06-02 18:33                 ` Bill Davidsen

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=20090525173201.25dc3f35@hydro.bl.pg.gda.pl \
    --to=janek_listy@wp.pl \
    --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).