<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jun 27, 2017 at 3:09 PM, InterNetX - Juergen Gotteswinter <span dir="ltr"><<a href="mailto:jg@internetx.com" target="_blank">jg@internetx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
> ><br>
> > Suppose I have one 500Gb thin provisioned disk<br>
> > Why can I indirectly see that the actual size is 300Gb only in Snapshots<br>
> > tab --> Disks of its VM ?<br>
><br>
> if you are using live storage migration, ovirt creates a qcow/lvm<br>
> snapshot of the vm block device. but for whatever reason, it does NOT<br>
> remove the snapshot after the migration has finished. you have to remove<br>
> it yourself, otherwise disk usage will grow more and more.<br>
><br>
><br>
> I believe you are referring to the "Auto-generated" snapshot created<br>
> during live storage migration. This behavior is reported<br>
> in <a href="https://bugzilla.redhat.com/1317434" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>1317434</a> and fixed since 4.0.0.<br>
<br>
</span>yep, thats what i meant. i just wasnt aware of the fact that this isnt<br>
the case anymore for 4.x and above. sorry for confusion<br>
<span class="gmail-"><br></span></blockquote><div> </div><div>I confirm that the snapshot of the VM, named "Auto-generated for Live Storage Migration" has been removed after the disk moving completion.</div><div>Also, for a preallocated disk the "qemu-img convert" has format options raw/raw:</div><div><br></div><div><div>[root@ov300 ~]# ps -ef|grep qemu-img</div><div>vdsm 18343 3585 1 12:07 ? 00:00:04 /usr/bin/qemu-img convert -p -t none -T none -f raw /rhev/data-center/mnt/blockSD/5ed04196-87f1-480e-9fee-9dd450a3b53b/images/303287ad-b7ee-40b4-b303-108a5b07c54d/fd408b9c-fdd5-4f72-a73c-332f47868b3c -O raw /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/303287ad-b7ee-40b4-b303-108a5b07c54d/fd408b9c-fdd5-4f72-a73c-332f47868b3c</div><div><br></div><div><br></div><div>for a thin provisioned disk instead it is of the form qcow2/qcow2</div><div>[root@ov300 ~]# ps -ef|grep qemu-img</div><div>vdsm 28545 3585 3 12:49 ? 00:00:01 /usr/bin/qemu-img convert -p -t none -T none -f qcow2 /rhev/data-center/mnt/blockSD/5ed04196-87f1-480e-9fee-9dd450a3b53b/images/9302dca6-285e-49f7-a64c-68c5c95bdf91/0f3f927d-bb42-479f-ba86-cbd7d4c0fb51 -O qcow2 -o compat=1.1 /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/9302dca6-285e-49f7-a64c-68c5c95bdf91/0f3f927d-bb42-479f-ba86-cbd7d4c0fb51</div></div><div><br></div><div><br></div><div>BTW: the "-p" option should give</div><div><br></div><div><div> -p display progress bar (compare, convert and rebase commands only). If the -p option is not used for a</div><div> command that supports it, the progress is reported when the process receives a "SIGUSR1" signal.</div></div><div><br></div><div>Is it of any meaning? I don't see any progress bar/information inside the gui? Is it perhaps in any other file on filesystem?</div><div><br></div><div>Thanks,</div><div>Gianluca</div></div></div></div>