From: Kyle Liddell <kyle@foobox.homelinux.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Upgrading to Raid
Date: Thu, 01 Sep 2005 00:29:44 -0500 [thread overview]
Message-ID: <1125552584.9109.15.camel@athlon> (raw)
In-Reply-To: <20050901034637.38BC91B8BB@localhost.comcast.net>
On Wed, 2005-08-31 at 21:46 -0600, scotthathcock@comcast.net wrote:
> Is there a good Howto on migrating from a non Raid disk to Raid? I
> recall seeing one but can't find it now.
If you're really lazy (like me), you can convert your current running
system over to RAID without messing with reinstalling from backups
(although you probably should make the backups, hopefully you won't have
to use them). Assuming you're doing RAID1, get your partitions and such
set up on your new drive. Then set up the raid array (the howto on
tldp.org is helpful, although be sure to use the newer mdadm setup even
though the docs are a little thinner in the howto) on your new drive,
marking the other drive in the array as bad/down. Copy say, /dev/hdxy
to /dev/mdx, and then edit the proper config files so that when you
reboot you'll be using the raid array. Once you're in it, change the
other drive in the array from bad to the old drive, and it'll rebuild
the array on the fly. It's pretty neat.
(If you do that method though, read the docs very carefully to make sure
you're doing it right. It's been a while since I've done it so I may
have gotten something backwards or some such.)
I wouldn't worry about any performance hits: A few months ago I
converted an old P2 450mhz system to RAID 1+0 and noticed no performance
hits, and even went to raid1 + lvm and again no problems. I've since
added an additional CPU to that box, but hard drives are just so much
slower than your CPU that it'd take a lot of work to create a slowdown.
Also, if there's any chance you'll want to maybe resize your partitions,
or especially, add more drives to the system, I would very strongly
suggest looking into LVM (Linux Volume Manager). It plays well with
raid (instead of raid1+0 I'm doing the equivalent with raid1+lvm, but no
worries about adding more disks) and lets you alter "partitions" on the
fly. If you want to add more storage, just buy a pair of drives, raid1
them, then just append it to the end of your volume, and run your
favorite on the fly partition resizer and enjoy.
By the way, a $15 promise ATA100 two channel IDE PCI card + a pair of
$80 120gb seagate HDDs is quite a nice deal. I've got two of the
Promise IDE cards in my server, and they seem to be pretty good PATA
cards if you're into that sort of thing.
Kyle
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-01 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 3:46 [gentoo-amd64] Upgrading to Raid scotthathcock
2005-09-01 3:59 ` Nuitari
2005-09-01 4:18 ` Chris S
2005-09-01 4:34 ` Chris S
2005-09-01 14:54 ` Billy Holmes
2005-09-01 5:29 ` Kyle Liddell [this message]
2005-09-01 5:36 ` Francisco Perez
2005-09-02 10:02 ` Joshua Hoblitt
2005-09-02 13:22 ` Matt Randolph
2005-09-02 19:56 ` Joshua Hoblitt
2005-09-03 9:54 ` Florian D.
2005-09-03 20:45 ` Homer Parker
2005-09-04 17:16 ` Florian D.
2005-09-03 0:04 ` Florian D.
2005-09-03 1:24 ` Francisco Perez
2005-09-03 3:18 ` Nuitari
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=1125552584.9109.15.camel@athlon \
--to=kyle@foobox.homelinux.net \
--cc=gentoo-amd64@lists.gentoo.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