[PVE-User] Creating VM with thin provisioning (please help me understand it).

[Mark Adams]

REF: "Thin provisioning is set on the storage, it is a checkbox and of
course it has to be a storage type than can be thin provisioned (ie
lvmthin, zfs, ceph etc)."

I have to correct myself on this sorry, it's been a long time since I used
lvmthin.... This checkbox option is only available on zfs storage as I
guess you have the option for both, where as lvmthin should always be thin?

On Thu, 5 Mar 2020 at 16:43, Mark Adams <mark at openvs.co.uk> wrote:

> Thin provisioning is set on the storage, it is a checkbox and of course it
> has to be a storage type than can be thin provisioned (ie lvmthin, zfs,
> ceph etc).
>
> Then every virtual disk that is created on that storage type is thin
> provisioned.
>
> Regards,
> Mark
>
> On Thu, 5 Mar 2020, 16:28 Leandro Roggerone, <leandro at tecnetmza.com.ar>
> wrote:
>
>> Hi guys , here i am trying to get used to pve. (I came from VM ware EXSi).
>> Im used to use "thin provisioning" option in vmware.
>> It allowed me to set maximum drive space allocation but vm will use
>> minimum and dynamically grow as guest OS needs
>> .
>> How should I accomplish same on pve  ?
>> I created a VM and set 200GB at the storage capacity but can not set any
>> flag about thin provisioning.
>> Now , If I list lslbl , it  shows that created VM is taking the 200GB.
>> root at pve:~# lsblk
>> NAME                         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
>> sda                            8:0    0  5.5T  0 disk
>> ├─sda1                         8:1    0 1007K  0 part
>> ├─sda2                         8:2    0  512M  0 part
>> └─sda3                         8:3    0  3.9T  0 part
>>   ├─pve-swap                 253:0    0    8G  0 lvm  [SWAP]
>>   ├─pve-root                 253:1    0  1.2T  0 lvm  /
>>   ├─pve-data_tmeta           253:2    0 15.8G  0 lvm
>>   │ └─pve-data-tpool         253:4    0  1.9T  0 lvm
>>   │   ├─pve-data             253:5    0  1.9T  0 lvm
>>   │   └─pve-vm--100--disk--0 253:6    0  200G  0 lvm
>>   └─pve-data_tdata           253:3    0  1.9T  0 lvm
>>     └─pve-data-tpool         253:4    0  1.9T  0 lvm
>>       ├─pve-data             253:5    0  1.9T  0 lvm
>>       └─pve-vm--100--disk--0 253:6    0  200G  0 lvm
>> sr0                           11:0    1 1024M  0 rom
>>
>>
>> I can see from gui , that is is possible to expand disk.
>> So ... perhaps I should assign a little storage at beginning and then
>> manually expand if needed.
>> Please share your idea about this.
>> I need to begin creating some VMs and work on them , I dont want to create
>> in a wrong way and have to destroy later.
>>
>> <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> Libre
>> de virus. www.avast.com
>> <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>