online lvm expansion

[orion]

ok so heres the setup, i have a bladecenter with 4 blades connected with FC to a nas server. I have an lvm shared with the cluster for vm disk storage. Everything is working as expected except i ran out of space(figures). So i expanded the fc target on the san that worked fine, expanded the lvm on the nodes that worked fine everything is looking like it is suppose to except dmsetup that shows the old size and i get errors attempting to create a disk size bigger than the old share size.

Ideas?

Proxmox 3.023

--- Physical volume ---
PV Name /dev/mapper/250726f784d6f7820
VG Name sanpool
PV Size 781.25 GiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 199999
Free PE 84287
Allocated PE 115712
PV UUID BwVCwy-wQ2B-svn5-vCG8-nH9V-RXqh-TOwcvO


--- Volume group ---
VG Name sanpool
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 97
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 17
Open LV 15
Max PV 0
Cur PV 1
Act PV 1
VG Size 781.25 GiB
PE Size 4.00 MiB
Total PE 199999
Alloc PE / Size 115712 / 452.00 GiB
Free PE / Size 84287 / 329.25 GiB
VG UUID 8fdhLc-2Okz-7rX1-zp1V-lIYe-QsNd-LR5ipu

250726f784d6f7820 dm-3 SCST_FIO,ProxMoxsize=500G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=active
`- 3:0:1:0 sde 8:64 active undef running

 

[reflex]

You mean vgextend fails?

 

[orion]

No lvcreate on vm creation fails, and thru running around the system looking at settings i found that dm-3 is the only thing that shows up incorrect. When i do a lvcreate at a smaller size within the original spacing it completes successfully.