At the use of the pvcreate command just after raid creation. All disks (total 3 /dev/hda1, /dev/hdc1 and /dev/hdd1) which compose the raid 5 got automaticaly the pv ID, normaly just the raid (/dev/md4) should have the ID.This is the same on all the 3 disks. For this raison hard drive hda1 is confused with hdc1 and hdd1. I got 2 others soft-raid with LVM2 over them without any problems. Like this, the physical volume is useless and can domage data if joined to an existed volume group. Reproducible: Always Steps to Reproduce: 1.mkraid /dev/md4 -R #build du raid 2.pvcreate /dev/md/4 3.pvscan Actual Results: #pvcreate No physical volume label read from /dev/md4 Physical volume "/dev/md4" successfully created #pvscan Found duplicate PV 9ozddegarqOS2QGfHbXafDb3noxW7unk: using /dev/hdd1 not /dev/hda1 Found duplicate PV 9ozddegarqOS2QGfHbXafDb3noxW7unk: using /dev/hdd1 not /dev/hda1 PV /dev/md5 VG yipi lvm2 [132.63 GB / 0 free] PV /dev/md3 VG prot-scsi lvm2 [12.68 GB / 0 free] PV /dev/hda1 lvm2 [114.54 GB] Total: 3 [114.54 GB] / in use: 2 [0 ] / in no VG: 1 [114.54 GB] Expected Results: #pvscan PV /dev/md5 VG yipi lvm2 [132.63 GB / 0 free] PV /dev/md3 VG prot-scsi lvm2 [12.68 GB / 0 free] PV /dev/md4 lvm2 [114.54 GB] Total: 3 [114.54 GB] / in use: 2 [0 ] / in no VG: 1 [114.54 GB] Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3) ================================================================= System uname: 2.6.3 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.3.13 distcc 2.12.1 i586-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -pipe" CHOST="i586-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://gentoo.mirrors.pair.com/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo ftp://gentoo.mirrors.pair.com/" MAKEOPTS="-j7" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gtk gtk2 imlib java jpeg ldap libg++ libwww lvm mad maildir mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime raid readline samba sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"
Not a kernel bug, throwing it back for proper assignment (whoever manages the pvcreate package)
I don't get the point why this bug is assigned to the cluster herd. Assigning back to bug-wranglers.
I did something like this very recently and it worked just fine for me. Perhaps the latest mdadm and lvm tools have this fixed? Going to close as fixed - reopen if not.
...
