From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Fri, 10 Apr 2009 21:59:42 +0100 [thread overview]
Message-ID: <20090410205942.GC21242@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <00cc01c9ba1d$3aefecf0$0a00a8c0@vorg>
[-- Attachment #1: Type: text/plain, Size: 1798 bytes --]
On Fri Apr 10, 2009 at 01:45:00PM -0700, Timothy D. Lenz wrote:
> Great, for every bit of nudge forward I end up a step or two back. Not
> I have to figure out this copy stuff. Is there any easy way to do some
> sort of compair after cp/rsync to see if/what was missed? Creating yet
> another botable disk to get the copy over to the array would be a bit
> of a pain. Might be easyer to pull the hda from one computer, stick it
> in another or usb case and copy to a temp storage area. on the other
> computer. Then put the drive back and copy from the temp storage to
> the array over then network. Nether computer has any ftp or web
> servers or a desktop. The older computer with the 3 sata drives does
> have mysql installed because I started to mess with setting up mythtv
> but never finished.
>
The easiest option is to use a bootable CD - there's plenty of linux CDs
around (have a look at http://linuxiso.org - my preferred one is GRML)).
Otherwise, yes, putting the drive into another system and doing the copy
there would work fine.
> As for the other reply, the sata drives each have 3 primary partitions
> all set to type fd and formated with ext3. I was going to try ext4 for
> the main storage of the newer system but I found there is a problem
> with kernels .27 and newer on nforce2 and newer boards. some sort of
> problem with the bios and apci. How do I find out which superblocks
> version is used?
>
Either "mdadm -D" on the array, or "mdadm -E" on one of the partitions
will show you the version.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-04-10 20:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10 9:10 ` KwangErn Liew
2009-04-10 9:55 ` CoolCold
2009-04-10 19:43 ` Timothy D. Lenz
2009-04-10 19:53 ` Robin Hill
2009-04-10 20:45 ` Timothy D. Lenz
2009-04-10 20:59 ` Robin Hill [this message]
2009-04-10 21:26 ` Timothy D. Lenz
2009-04-10 21:51 ` Robin Hill
2009-04-11 5:29 ` Timothy D. Lenz
2009-04-11 14:29 ` CoolCold
2009-04-11 18:47 ` Timothy D. Lenz
2009-04-12 0:53 ` Timothy D. Lenz
2009-04-12 11:11 ` Robin Hill
2009-04-12 19:55 ` Timothy D. Lenz
2009-04-14 9:30 ` Robin Hill
2009-04-17 0:47 ` Timothy D. Lenz
2009-04-17 7:49 ` Robin Hill
2009-04-11 14:36 ` Robin Hill
2009-04-11 15:04 ` jim owens
2009-04-11 15:44 ` Jeff Garzik
2009-04-11 17:40 ` jim owens
2009-04-12 11:11 ` Jeff Garzik
2009-04-12 16:43 ` jim owens
2009-04-12 17:18 ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22 ` Timothy D. Lenz
2009-04-10 19:50 ` Robin Hill
2009-04-11 4:40 ` Jon Lewis
2009-04-11 7:48 ` Jan Ceuleers
2009-04-11 8:50 ` Goswin von Brederlow
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=20090410205942.GC21242@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--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).