From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from agk.surrey.redhat.com (agk.surrey.redhat.com [172.16.10.74]) by pobox.surrey.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k9QKR28U006823 for ; Thu, 26 Oct 2006 21:27:02 +0100 Received: from agk by agk.surrey.redhat.com with local (Exim 4.34) id 1GdBoc-0001uD-No for linux-lvm@redhat.com; Thu, 26 Oct 2006 21:27:02 +0100 Date: Thu, 26 Oct 2006 21:27:02 +0100 From: Alasdair G Kergon Subject: Re: [linux-lvm] Mirror resync direction Message-ID: <20061026202702.GF1319@agk.surrey.redhat.com> References: <20061026211738.008da405@nim.leo> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20061026211738.008da405@nim.leo> 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" Content-Transfer-Encoding: 7bit To: LVM general discussion and development On Thu, Oct 26, 2006 at 09:17:38PM +0100, Paul LeoNerd Evans wrote: > testing (2.02.06-3). I use it to set up a VG containing two > Is this a bug in the LVM2 tools, or the dm-mirror target, or what? Is it > perhaps a limitation of --corelog; in which case, how can I protect > against that? Firstly, this is work in progress, so you should be using newer tools. Secondly, with newer tools you should follow a different procedure: use vgreduce --removemissing (carefully) to remove the lost device, add the replacement disk to the VG in the normal way, then use lvconvert to turn the LV back into a mirror. Alasdair -- agk@redhat.com