public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: alex-lists-linux-kernel@yuriev.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-fakeraid controllers
Date: Tue, 07 Feb 2006 12:08:25 +0000	[thread overview]
Message-ID: <1139314105.18391.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20060207015126.GA12236@s2.yuriev.com>

On Llu, 2006-02-06 at 20:51 -0500, alex-lists-linux-kernel@yuriev.com
wrote:
> 	Does anyone has a list/refence/etc on reasonably modern SCSI
> controllers (at least u160) in a non-fakeraid way i.e. the way that would
> allow linux to boot from a RAID protected disk array when one of the drives
> in the array failed even if the root filesystem is located on the same
> array?

Most raid (soft or otherwise) will usually do it. I don't know any SCSI
hardware which will do it reliably unless you go fibrechannel or SATA
simply because a dead scsi drive can and sometimes does hang the entire
shared bus.

The majority of the time the aacraid based cards will do what you need
(most of the time anyway) and can also do a lot of on the fly recovery
and management. The fusions can do some raid stuff of this nature. Most
of the newer hardware is going SATA however.

Alan


  parent reply	other threads:[~2006-02-07 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  1:51 non-fakeraid controllers alex-lists-linux-kernel
2006-02-07  7:58 ` Helge Hafting
2006-02-07 15:45   ` Phillip Susi
2006-02-07 17:39     ` Wakko Warner
2006-02-07 18:25       ` Phillip Susi
2006-02-07 22:45         ` Wakko Warner
2006-02-07  9:30 ` Christoph Hellwig
2006-02-07 12:08 ` Alan Cox [this message]
2006-02-07 22:57 ` Jesper Juhl

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=1139314105.18391.25.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alex-lists-linux-kernel@yuriev.com \
    --cc=linux-kernel@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