public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: Fabien Salvi <fabien@cri74.org>, linux-scsi@vger.kernel.org
Subject: Re: Migrating RAID array to a different manufacturer controller
Date: Tue, 18 Feb 2003 11:05:19 -0700	[thread overview]
Message-ID: <3E5275DF.3090000@mvista.com> (raw)
In-Reply-To: <3E511791.2060904@cri74.org>

You have to use one driver to read the data from adaptor A and another 
driver to write the data to adaptor B after you have setup the RAID 
arrays on adaptor B to match that of adaptor A.  There is no homogenous 
way to access that data.  Dell had proposed a common superblock format, 
but that pretty much got shot down because it eases the ability of 
customers to switch vendors.

Thanks
-steve

Fabien Salvi wrote:

> Hello,
>
> Here is a question that is maybe a bit off topic.
> Sorry for that...
>
> Is it possible to migrate a RAID array from a manufacter controller to 
> another ?
> Is it depend on the level of RAID ?
> I've already be able to read data from RAID 1 because it's simple 
> mirroring (with Mylex DAC 960 controller).
> But, it may not be the case for all controllers I suppose...
>
> In fact, I have a server or a storage enclosure that use a CMD, 
> ICP-Vortex or Mylex controller and I would like to get data from it.
>
> Maybe it's possible with linux software RAID tools ?
>
> What can differentiate from a controller to another ?
> Maybe the parity block size ?
>
>
> Thanks in advance for your help !
>
> B.R.
>


      parent reply	other threads:[~2003-02-18 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 17:10 Migrating RAID array to a different manufacturer controller Fabien Salvi
2003-02-17 17:24 ` Ryan Weiss
2003-02-18  8:59   ` Fabien Salvi
2003-02-18 18:05 ` Steven Dake [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=3E5275DF.3090000@mvista.com \
    --to=sdake@mvista.com \
    --cc=fabien@cri74.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox