[PVE-User] Extending Logical Volume on host, but not in the guest

[Germain Maurice]

Obviously, i stopped the VM before doing the lvextend and started it after.

Actually, i found where was the problem, i have a 5 nodes cluster my VM 
is on node 2
and i did the lvextend on node 1.
I played with "lvchange --refresh /dev/SAS/vm-300-disk-1" on node 2 and 
the "blockdev --getsize64 /dev/SAS/vm-300-disk-1" returned the new size.
So i expect lvextend does a "lvchange --refresh" right after the extending.

The problem is that other PVE nodes don't take account about this 
extending, maybe after a migration "lvchange --refresh" is done, i don't 
tried it yet.

Thanks everybody for your quick answers.

Le 03/03/11 19:30, Gilles Mocellin a écrit :
> Le Thursday 03 March 2011 18:56:28 Germain Maurice, vous avez écrit :
>> Le 03/03/11 18:52, Germain Maurice a écrit :
> [...]
>
>>> I'm testing the ability to extend partitions inside VMs, so i did a :
>>> # lvextend -L+5g /dev/SAS/vm-300-disk-1
>>> # lvdisplay -C
>>>
>>>    vm-300-disk-1 SAS -wi-ao 15.00G
>>>    vm-101-disk-1 SATA  -wi-a- 32.00G
>>>
>>> When i'm testing this extending in the VM, i still have /dev/vdb with
>>> 10GB...
>>>
>>> Is it possible to do that ?
>>> What command i forgot to execute ??
>>>
>>> Thank you
> You must stop and start the VM (not just restart). KVM does not see the
> resized block device.
>
>> With Proxmox 1.7 natürlich ;)
> I wasn't aware of it, I have to try that !
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


-- 
Germain Maurice
Administrateur Système/Réseau
Tel : +33.(0)1.42.43.54.33

http://www.linkfluence.net