All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: "Dieter Stüken" <stueken@conterra.de>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Copying LVM from one system to another
Date: Tue, 11 Jul 2006 14:10:18 -0400	[thread overview]
Message-ID: <1152641418.2787.106.camel@localhost.localdomain> (raw)
In-Reply-To: <44B3E470.90404@conterra.de>

yes, you are right for migrating the content from one disk to another
disk.

but in his case, he want to migrate to another system, with same cpu,
ram, disk,...

that is why i think clone is ok.

Ming

On Tue, 2006-07-11 at 19:48 +0200, Dieter Stüken wrote:
> Ming Zhang wrote:
> > if HW is the same, why not use ghost or alike software to do a clone?
> 
> Don't "clone" the LVM PVs if you ever want to connect both disks simultaneously.
> For normal partitions this is fine, as those are identified by the device
> name. So you can easily distinguish /dev/hda1 from /dev/hdc1.
> 
> LVM however identifies the different VG/LV/PV by its content, regardless of
> where the disks are connected. If you connect your LVM disk to a different
> cable or controller, don't worry, it will be found automatically. If two disks,
> however, look exactly the same, LVM gets confused. 
> 
> Instead you should connect both disk:
> 
> arrange booting from <newdisk>,
> lvm from <olddisk> should still work, even if connected differently.
> 
> pvcreate <new disk>
> vgextend <new disk>
> pvmove <olddisk>
> vgreduce <olddisk>
> 
> to migrate all LVM content to the new disk.
> 
> Dieter.

      parent reply	other threads:[~2006-07-11 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 14:01 [linux-lvm] Copying LVM from one system to another Shaun Mccullagh
2006-07-10 17:18 ` Ming Zhang
2006-07-11 17:48   ` Dieter Stüken
2006-07-11 18:03     ` Shaun Mccullagh
2006-07-11 19:12       ` Dieter Stüken
2006-07-11 19:50         ` Shaun Mccullagh
2006-07-11 18:10     ` Ming Zhang [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=1152641418.2787.106.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=linux-lvm@redhat.com \
    --cc=stueken@conterra.de \
    /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.