[linux-lvm] Having duplicate PV problems, think there's a bug in LVM2 md component detection

[Ron Watkins]

Due to another failing hard drive, I was forced to just use the md0 device 
directly and put it into use.  Once I have the dying drive replaced, I might 
be able to clear the data off again if you want to do a specific set of 
tests, but that would take many hours.  (150+ gigs over Fast Ethernet, not a 
quick process).  So please be sure you need me to do this, if you do.

I am using LVM version 2.01.04 (2005-02-09).  The Library Version is 
1.01.00-ioctl (2005-01-17).  The Driver Version is 4.1.0.  (no date given). 
I don't have any easy way to determine if the Debian maintainer is patching 
this.  Should I be submitting the bug report directly to him/her/them 
instead?

I'm not sure how to strace... I see the strace command. I assume I'd have to 
strace the pvcreate and pvdisplay, meaning I'd need to move my data again 
first.   If you do want me to do this, I can start copying data off late 
tomorrow, and can probably do the actual test on Wednesday.   I'll need the 
exact command line you want used, however, since I don't know anything about 
strace.

<<RON>>

jeeves:~# lvm version
  LVM version:     2.01.04 (2005-02-09)
  Library version: 1.01.00-ioctl (2005-01-17)
  Driver version:  4.1.0


----- Original Message ----- 
From: "Luca Berra" <bluca at comedia.it>
To: "LVM general discussion and development" <linux-lvm at redhat.com>
Sent: Monday, February 28, 2005 4:38 PM
Subject: Re: [linux-lvm] Having duplicate PV problems,think there's a bug in 
LVM2 md component detection


> On Mon, Feb 28, 2005 at 03:39:59PM -0500, Ron Watkins wrote:
>>Yes, I have two PVs with the same UUID.  The problem is that these PVs are 
>>COMPONENTS OF an MD device.  So when pvcreate writes its superblock to 
>>md0, it gets mirrored onto all the components of md0.  Later runs elicit 
>>much complaining because /dev/hda and several /dev/sd devices now have the 
>>'same' UUID.   They're SUPPOSED to, they're components of a RAID.
>>
>>LVM is supposed to detect this situation and not do that, but it doesn't 
>>seem to be working for me.
>>
> i wonder if it is a problem with largefile access ?!?
> which version of lvm2 are you using?
> does debian patch it?
> can you try stracing it an look for seeks, so we can see if it is
> wrapping around somewhere?
>
> L.
>
> -- 
> Luca Berra -- bluca at comedia.it
>        Communication Media & Services S.r.l.
> /"\
> \ /     ASCII RIBBON CAMPAIGN
>  X        AGAINST HTML MAIL
> / \
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>