logical volumes can not be resized or created on a pvresized volumegroup Reproducible: Always Steps to Reproduce: 1. step, create a vg, with an underlaying block device (f.e. 5gb), and create a vg and lv on it # pvcreate /dev/xvdc # vgcreate testvg /dev/xvdc # lvcreate -l 100%FREE -n testlv testvg 2. step, grow the underlaying block device, and grow the pv,vg,lv vm, has been taken down to resize the underlaying blockdevice, and has been rebooted afterwards (block device has been resized +5gb) # pvresize /dev/xvdc # vgdisplay --- Volume group --- VG Name testvg System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 10,00 GB PE Size 4,00 MB Total PE 2561 Alloc PE / Size 1282 / 5,01 GB Free PE / Size 1279 / 5,00 GB VG UUID uLGrx6-6JAR-17N6-m9MC-hZD0-RLk5-igUhQE as you can see we do have physical extends and disk space free now, so we should be able to resize the lv now # lvresize -L +1G /dev/testvg/testlv Extending logical volume testlv to 6,01 GB Insufficient free space: 256 extents needed, but only 0 available Actual Results: neither lvresize or lvcreate will work after block device growth and pvresize operation performed on it, to extend existing volumes or create new ones virtual machine running on citrix xenserver with sys-kernel/xen-sources-2.6.18-r12 # uname -a Linux mysql01 2.6.18-xen-r12 #2 Wed Nov 18 10:52:19 Local time zone must be set--see zic manu i686 Intel(R) Xeon(R) CPU E5520 @ 2.27GHz GenuineIntel GNU/Linux i've been trying that now on gentoo and on centos so far, all unter citrix xenserver, the centos machine does even have a kernel that comes with xenserver and is officially supported by citrix i'll give parralels a try tomorrow
If you shutdown the vg and start it up again, does the resize work? 1. What allocation policy are you using? 2. Can you create a new LV after the PV resize? 3. Can you please include the output of: # vgdisplay -v vgtest
darn, it has been a layer 8 problem, has been quite late yesterday, should have filed the bug report after a couple hours of sleep, sry for your time spend on this # vgdisplay -v testvg after doing the test again, vgdisplay -v testvg showed me this --- Physical volumes --- PV Name /dev/xvdc PV UUID Y4jMRm-zLhC-UCm3-GdiL-msHC-kKj9-YEEb4E PV Status NOT allocatable Total PE / Free PE 2561 / 1023 and that has been the problem PV STATUS NOT ALLOCATABLE after a # pvchange -x y /dev/xvdc everything worked again sry