From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k6BHmuUM021430 for ; Tue, 11 Jul 2006 13:48:56 -0400 Received: from conterra.de (vvv.conterra.de [212.124.44.162]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id k6BHmnsY022729 for ; Tue, 11 Jul 2006 13:48:50 -0400 Message-ID: <44B3E470.90404@conterra.de> Date: Tue, 11 Jul 2006 19:48:32 +0200 From: =?ISO-8859-1?Q?Dieter_St=FCken?= MIME-Version: 1.0 Subject: Re: [linux-lvm] Copying LVM from one system to another References: <32F72C4D4D0EC8458CA5BFD76A6D6C680ACF39D0@gimli.xb.local> <1152551925.8360.52.camel@localhost.localdomain> In-Reply-To: <1152551925.8360.52.camel@localhost.localdomain> Content-Transfer-Encoding: 7bit Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: mingz@ele.uri.edu, LVM general discussion and development 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 , lvm from should still work, even if connected differently. pvcreate vgextend pvmove vgreduce to migrate all LVM content to the new disk. Dieter.