Hello, I have problems creating a LV on top of SW RAID-5 volume. I have Fedora Core 1/AMD64, and LVM2 utils 2.00.08-5 RPM from the latest Fedora Core beta (1.90, I think). My kernel is 2.6.4. The problem is that 1) Metadata version 2 does not work at all, and 2) If I use version 1, I cannot create LV once the VG is created - "lvm lvcreate" tries to write metadata to /dev/sda4 (one of the parts of my SW RAID-5 volume) instead of the /dev/md5 itself. Details are attached. Thanks for any help. -Yenya ad 1) # lvm pvcreate /dev/md5 Physical volume "/dev/md5" successfully created # lvm vgcreate -s 64M data_vg /dev/md5 Volume group "data_vg" successfully created # lvm lvcreate -l 4534 -n test_lv data_vg Volume group "data_vg" doesn't exist # lvm vgs # ad 2) # lvm pvcreate -M1 /dev/md5 Physical volume "/dev/md5" successfully created # lvm vgcreate -M1 -s 64M data_vg /dev/md5 Volume group "data_vg" successfully created # lvm vgdisplay --- Volume group --- VG Name data_vg System ID hostname.domain.cz1080572966 Format lvm1 VG Access read/write VG Status resizable MAX LV 255 Cur LV 0 Open LV 0 Max PV 255 Cur PV 1 Act PV 1 VG Size 283.38 GB PE Size 64.00 MB Total PE 4534 Alloc PE / Size 0 / 0 Free PE / Size 4534 / 283.38 GB VG UUID cqall8-M9B6-BUJM-uAs6-Ykn3-WSCc-pW6bXm # lvm lvcreate -l 4534 -n test_lv data_vg device-mapper ioctl cmd 9 failed: Invalid argument Couldn't load device 'data_vg-test_lv'. Failed to activate new LV. # dmesg|tail -2 device-mapper: dm-linear: Device lookup failed device-mapper: error adding target to table # lvm lvremove /dev/data_vg/test_lv Do you really want to remove active logical volume "test_lv"? [y/n]: y Logical volume "test_lv" successfully removed # lvm lvcreate -l 4534 -n test_lv data_vg -v -v global/locking_type not found in config: defaulting to 1 global/locking_dir not found in config: defaulting to /var/lock/lvm File-based locking enabled. Locking /var/lock/lvm/V_data_vg WB Finding volume group "data_vg" /dev/sda: No label detected [...] /dev/sda4: lvm1 label detected /dev/md5: lvm1 label detected Duplicate PV wqQ2AyMMX3z1or14EvqOwLEL3RKaldUf on /dev/sda4 - using md /dev/md5 /dev/sdb: No label detected /dev/sdb1: No label detected [...] Found /dev/sda4 in VG data_vg Creating logical volume test_lv Archiving volume group "data_vg" metadata. Failed to read PV data from /dev/loop0 /dev/sda does not have a valid LVM1 PV identifier /dev/md0 does not have a valid LVM1 PV identifier [...] Found /dev/sda4 in VG data_vg Duplicate PV wqQ2AyMMX3z1or14EvqOwLEL3RKaldUf on /dev/sda4 - using md /dev/md5 Found /dev/md5 in VG data_vg Duplicate PV wqQ2AyMMX3z1or14EvqOwLEL3RKaldUf - using md /dev/md5 [...] format1: Unknown metadata version 18881 found on /dev/sdd4 Successfully wrote data to /dev/sda4 Creating volume group backup "/etc/lvm/backup/data_vg" Finding volume group for uuid ll8M9B6BUJMuAs6Ykn3WSCcpW6bXm00000000000000000000000000000000 Found /dev/sda4 in VG data_vg Found volume group "data_vg" activation/missing_stripe_filler not found in config: defaulting to /dev/ioerror activation/mirror_region_size not found in config: defaulting to 512 Locking memory Loading data_vg-test_lv device-mapper ioctl cmd 9 failed: Invalid argument Couldn't load device 'data_vg-test_lv'. Unlocking memory Failed to activate new LV. Unlocking /var/lock/lvm/V_data_vg -- | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | | GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E | | http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ | Any compiler or language that likes to hide things like memory allocations behind your back just isn't a good choice for a kernel. --Linus Torvalds _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/