From: Brad Campbell <brad@wasp.net.au>
To: Robin Bowes <robin-lists@robinbowes.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>, linux-raid@vger.kernel.org
Subject: Re: Moving controllers
Date: Tue, 23 Mar 2004 15:20:43 +0400 [thread overview]
Message-ID: <40601D8B.6050906@wasp.net.au> (raw)
In-Reply-To: <39776.194.60.85.4.1080037377.squirrel@194.60.85.4>
Robin Bowes wrote:
>>why not just experiment and find out? put two disks on a single channel,
>>make the raid, power down, move the slave to another channel, and see if
>>the raid assembles.
>
>
> One word: time; I was hoping someone could tell me if it would work to
> save me messing around. Of course, if I plan to do this I will perform
> some sort of test first.
>
The answer is yes it will work fine.
I had 5 200gb WD disks set as autodetect raid-5
My internal VIA IDE interfaces were hda/b/c/d
My external CMD680 IDE interfaces were hde/f/g/h
I had raid disks on c/d/e/f/g.
I created the raid and ran it for months, then I shuffled the disks and master/slave jumpers.
No problems.
I then purchased a couple of Highpoint 1540 SATA cards and a bundle of addonics SATA-> IDE adaptors.
Using the in-kernel hpt ata driver, no problem.
I then moved across to a pair of Promise SATA150-TX4 cards with the libata driver, no problem.
So as you can see, these disks have been "everywhere man" and I never had a problem with the kernel
or appropriate tools picking them up in any order.
Brad
prev parent reply other threads:[~2004-03-23 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 14:25 Moving controllers Robin Bowes
[not found] ` <Pine.LNX.4.44.0403221748490.13036-100000@coffee.psychology.mcmaster.ca>
[not found] ` <Pine.LNX.4.44.0403221748490.13036-100000@coffee.psychology.mcmaster.c a>
2004-03-23 10:22 ` Robin Bowes
2004-03-23 11:20 ` Brad Campbell [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=40601D8B.6050906@wasp.net.au \
--to=brad@wasp.net.au \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-raid@vger.kernel.org \
--cc=robin-lists@robinbowes.com \
/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).