On Thu, May 9, 2019 at 11:46 AM <francisco.garcia@wbsgo.com> wrote:
Hello Nir,
thanks for your response,
How ever, I already put initial size when I create the disk.

The disk is just the base volume...

I show the values than the disk contains before create:
Disk: {
Name:T_iSCSI_Thin_Disk1_restore,
Id:null,
Interface:VIRTIO_SCSI,
Format:COW,
WipeAfterDelete: false,
Shareable: false,
Sparse: true,
Boot:true,
Active:true,
Sizes:{
  Initial:4294967296,
  Actual:null,
  Total:null,
  Provisioned: 4294967296
  }
}
After I created the disk(WIth initial Size and provisioned Size, previously showed). I create the snapshots, and these snapshot's images are created with an actual size with 1Gb(I don't known how I can put an actual size to these images). So, I think the problem isn't when I create the disk, else it maybe when I create the snapshot-chain.

Every layer in the snapshot chain is another disk, and there you can specify the initial size.

Copying from:
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk_snapshots.py

    # Add the new snapshot:
    snapshot = snapshots_service.add(
        types.Snapshot(
            description=description,
            disk_attachments=[
                types.DiskAttachment(
                    disk=types.Disk(
                        id=disk_id,
                        image_id=image_id

                        # sizes for every snapshot should work here

                    )   
                )   
            ]   
        ),  
    )   
 


I don't have a problems when I upload the first image(with size 2Gb) of disk than is the "base" of snapshot-chain, else I have a problem when I upload a disk Snapshot(other image of snapshot-chain) bigger than 1Gb.

How ever, the same process with NFS storages works correctly.

Because on NFS there is no need to allocate storage, the file system does this for you.
But with block storage you must specify the initial size of the disk.

Nir