From: Gerry Reno <greno@verizon.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Move an array/volgroup to another machine.
Date: Thu, 16 Apr 2009 12:49:52 -0400 [thread overview]
Message-ID: <49E761B0.5020506@verizon.net> (raw)
In-Reply-To: <49E75FB5.2050700@brunson.com>
Eric Brunson wrote:
> On 04/16/2009 10:33 AM, Gerry Reno wrote:
>> Eric Brunson wrote:
>>> On 04/16/2009 10:12 AM, Eric Brunson wrote:
>>>> On 04/16/2009 10:07 AM, Gerry Reno wrote:
>>>>> We built a replacement server (x86_64) for an older server (x86).
>>>>> Now we want to move a RAID-5 array intact from the older machine
>>>>> over to the new machine. We know the UUID of the array and of all
>>>>> the PV and VG on the array. So what commands should we perform
>>>>> after plugging in all the array drives to the new server to bring
>>>>> up the array and lvm on the new machine?
>>>>
>>>> "vgscan" and "vgchange -a VGNAME" I believe.
>>>
>>>
>>> Sorry, doing three things at once: vgchange -a y VGNAME
>>>
>>>
>>>>
>>>> Make sure your VG name doesn't conflict with any already in the
>>>> machine.
>>>>
>> Will vgchange activate the raid array?
>
>
> Is it an md (software) RAID or a hardware RAID device?
>
> If the former, then I'm not sure. I'll have to defer to someone with
> more md experience.
> If the latter, then it depends of if you have the correct drivers and
> hardware detection.
>
>
>>
>> The new server just has a couple raid-1 arrays on it right now. But
>> we need the raid-5 to be activated because there is a volgroup that
>> uses the raid-5 device as it's PV.
>>
It's an 'md' software raid device. I think we can probably just try to
assemble the array using the UUID. Maybe something like:
mdadm -vv -A /dev/md4 --uuid=UUID
Regards,
Gerry
next prev parent reply other threads:[~2009-04-16 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 16:07 [linux-lvm] Move an array/volgroup to another machine Gerry Reno
2009-04-16 16:12 ` Eric Brunson
2009-04-16 16:13 ` Eric Brunson
2009-04-16 16:33 ` Gerry Reno
2009-04-16 16:41 ` Eric Brunson
2009-04-16 16:49 ` Gerry Reno [this message]
2009-04-17 8:42 ` Luca Berra
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=49E761B0.5020506@verizon.net \
--to=greno@verizon.net \
--cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.