So we are copying raw volume to raw volume and this cannot succeed if the device is smaller than the image.
We need the original volume metadata, and the vdsm logs showing the copy image from the original volume to the export domain.
Fixing the virtual size in the .meta file manually will work, but you should check that the size match the virtual size in engine database.
Nir Here's the original volume metadata
EOF DOMAIN=58990f55-cd1d-4c2d-9ef2-2adc92881629 VOLTYPE=LEAF CTIME=1453118815 FORMAT=RAW IMAGE=9eb60288-27b6-4fb1-aef1-4246455d588e DISKTYPE=2 PUUID=00000000-0000-0000-0000-000000000000 LEGALITY=LEGAL MTIME=0 POOL_UUID= SIZE=67108864 TYPE=PREALLOCATED DESCRIPTION={"DiskAlias":"Elementary_Jenkins","DiskDescription":"Mount me as /elementary/jenkins"} EOF And here's the LV LV Path /dev/58990f55-cd1d-4c2d-9ef2-2adc92881629/ddf8b402-514c-4a3c-9683-26810a7c41c0 LV Name ddf8b402-514c-4a3c-9683-26810a7c41c0 VG Name 58990f55-cd1d-4c2d-9ef2-2adc92881629 LV UUID Fs6Ot4-eVfh-oFv3-VALB-85Bt-OJnq-LLU3zS LV Write Access read/write LV Creation host, time moe.mgmt.elementary.se, 2016-01-18 12:06:48 +0000 LV Status NOT available LV Size 35.25 GiB Current LE 282 Segments 2 Allocation inherit Read ahead sectors auto And this is from within the vm Disk /dev/vdc: 35.3 GiB, 37849399296 bytes, 73924608 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 So everyone besides that meta value seem to have understood the disk magically somehow have grown beyond it's maximum size. Same goes from the web-ui where the actual size says 35G while the size stays at 32G. That disk is created inside oVirt, and I can not explain how it could have grown beyond 32G Rgds, Jonas