[ovirt-users] Moving thin provisioned disks question

Fred Rolland frolland at redhat.com
Wed Jun 28 06:48:05 UTC 2017


Hi,

The qemu operation progress is parsed [1] and is printed on debug level in
Vdsm log [2].
In the UI, a progress indication of the operation is available on the disks
status for the "Move Disk" operation.
Currently only for this operation.

Regards,

Fred


[1]
https://github.com/oVirt/vdsm/blob/917905d85abb1a24d8beea09f012b81ed594b349/lib/vdsm/qemuimg.py#L280
[2]
https://github.com/oVirt/vdsm/blob/917905d85abb1a24d8beea09f012b81ed594b349/lib/vdsm/qemuimg.py#L332

On Tue, Jun 27, 2017 at 6:50 PM, Gianluca Cecchi <gianluca.cecchi at gmail.com>
wrote:

> On Tue, Jun 27, 2017 at 3:09 PM, InterNetX - Juergen Gotteswinter <
> jg at internetx.com> wrote:
>
>>
>> >     >
>> >     > Suppose I have one 500Gb thin provisioned disk
>> >     > Why can I indirectly see that the actual size is 300Gb only in
>> Snapshots
>> >     > tab --> Disks of its VM ?
>> >
>> >     if you are using live storage migration, ovirt creates a qcow/lvm
>> >     snapshot of the vm block device. but for whatever reason, it does
>> NOT
>> >     remove the snapshot after the migration has finished. you have to
>> remove
>> >     it yourself, otherwise disk usage will grow more and more.
>> >
>> >
>> > I believe you are referring to the "Auto-generated" snapshot created
>> > during live storage migration. This behavior is reported
>> > in https://bugzilla.redhat.com/1317434 and fixed since 4.0.0.
>>
>> yep, thats what i meant. i just wasnt aware of the fact that this isnt
>> the case anymore for 4.x and above. sorry for confusion
>>
>>
> I confirm that the snapshot of the VM, named "Auto-generated for Live
> Storage Migration" has been removed after the disk moving completion.
> Also, for a preallocated disk the "qemu-img convert" has format options
> raw/raw:
>
> [root at ov300 ~]# ps -ef|grep qemu-img
> 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
>
>
> for a thin provisioned disk instead it is of the form qcow2/qcow2
> [root at ov300 ~]# ps -ef|grep qemu-img
> 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
>
>
> BTW: the "-p" option should give
>
>        -p  display progress bar (compare, convert and rebase commands
> only).  If the -p option is not used for a
>            command that supports it, the progress is reported when the
> process receives a "SIGUSR1" signal.
>
> 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?
>
> Thanks,
> Gianluca
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170628/04b5b71b/attachment.html>


More information about the Users mailing list