From mboxrd@z Thu Jan 1 00:00:00 1970 From: malahal@us.ibm.com Subject: Re: DM-RAID1 data corruption Date: Tue, 26 May 2009 18:33:28 -0700 Message-ID: <20090527013328.GA18627@us.ibm.com> References: <20090415031210.GA11881@us.ibm.com> <49E645DA.4010204@redhat.com> <20090416024959.GB19876@us.ibm.com> <49E7B029.20906@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com Cc: agk@redhat.com List-Id: dm-devel.ids Mikulas, does RedHat have a bugzilla bug opened for this problem? Mikulas Patocka [mpatocka@redhat.com] wrote: > MD-RAID1 solves this problem by having counters in superblocks on both > legs. If some leg dies, the counter on the other devices is increased. If > the dead disk comes online again, it is found that it has old counter and > cannot be trusted. > > Would it be possible to extend a logical volume when converting it to a > raid1 and use the last area of the volume as a superblock? Interesting idea. Any more thoughts on this front?