Restore problem: why diff restored size in default disk and 2nd disk?

[Robin Chen]

Hi Team,

I'm new to Proxmox/Linux, here's the problem, for a backup:

if restore it to default disk, seems the restored size is dynamic( size the guest OS acutal used, say 11G for a new installed Windows);
if restore it to a 2nd disk(tried both ZFS or LLV), the restored size is just fixed size, say 128G as defined during new installation.

As a result, if I restore all my 8 backups to the default disk(256G), everything is fine. While if restoring to my 2nd disk(also 256G), it can hold maybe just 2 VMs(fixed size 128G + 64G, almost reach the 256G and full).

Please see detailed in attached screenshot

Why? Thanks in advance.

 

[Stoiko Ivanov]

What's the definition of both storages ? (local-lvm vs samsung-256g-2018jun) - please post the contents of /etc/pve/storage.cfg

 

[Robin Chen]

Thanks for your reply.

Here's the storage.cfg

root@proxmox:~# cat /etc/pve/storage.cfg
dir: local
    path /var/lib/vz
    content backup,iso,vztmpl
    maxfiles 1
    shared 0

lvmthin: local-lvm
    thinpool data
    vgname pve
    content images,rootdir

dir: seagate-2048g-2017dec
    path /seagate-2048g-2017dec
    content vztmpl,backup,iso
    maxfiles 100
    shared 0

lvm: samsung-256g-2018jun
    vgname samsung-256g-2018jun
    content rootdir,images
    shared 0

also part of 'fdisk -l' if my description is not clear:

Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 80A1D23E-30A1-4EBC-9831-D64E93B239A4

Device      Start       End   Sectors   Size Type
/dev/sda1    2048      4095      2048     1M BIOS boot
/dev/sda2    4096    528383    524288   256M EFI System
/dev/sda3  528384 488397134 487868751 232.6G Linux LVM

...

Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6E704CDA-1311-704D-8FC0-85C6F05E30C2

Device     Start       End   Sectors   Size Type
/dev/sdb1   2048 488397134 488395087 232.9G Linux filesystem

Storage local & local-lvm is generated by Proxmox Installation on my default disk(dev/sda).
Now samsung-256g-2018jun(dev/sdb) is LVM, while as mentioned, I also tried ZFS previously, same problem(big restored size).

 

[Stoiko Ivanov]

Your local-lvm is a lvm thin pool, wheras samsung-256g-2018jun is a regular lvm (a.k.a lvm thick). With a thin pool you can overprovision (give VMs more space than is available on the storage), with the associated risks.
For ZFS you need to mark the storage as sparse (in the GUI it's called thin provision).

Take a look at our documentation:
https://pve.proxmox.com/wiki/Storage
https://pve.proxmox.com/wiki/Storage:_LVM_Thin

 

[Robin Chen]

Excellent, so the key is thin provision! The problem is solved, thank you!

 

[guletz]

Excellent, so the key is thin provision! The problem is solved, thank you!

Hi,

If you solve your problem, then be kindly and edit the subject of this post and wrote ... SOLVED, so others can use this solution without a new post.

Thx.