Converting a VMDK produces wrong size phenomenon?

[Nhoague]

Hello!

I used VMWare converter to create a VMDK file of a server I am converting to proxmox raw. The initial server is only 93GB used, but the actual real volume is 931GB.

When I create the VMDK file and copy it to the proxmox host for converting it comes in as 93GB, but when I convert to raw using qemu-img convert the new file "says" it is 931GB but a du -sh . only shows it to actually be 93GB.

This wouldnt normally bug me, but as I am moving this file to our SAN, it is reporting a growth of 931GB, not the actual size of the image.

Is there any way to resize this raw to 250GB prior to moving it to the SAN?

Thanks!

 

[mir]

Read this: http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=1028042

Seems default is to create a zeroed thick image but adding this option '-d thin ' to vmkfstools will do what you want.

zeroedthick

This is the default option for virtual machine disks created and stored on a VMFS datastore.

thin

This is the default option for virtual machine disks stored on an NFS datastore. It allocates and commits space on demand, growing as more virtual disk space is used.

Note: The configured size of thin-provisioned disks is correctly displayed using the ls command. The disk space consumed by disk files on a datastore is determined using the du command.