[ovirt-users] Snapshot or not?

[Ala Hino]

Hi Tibor,

I am not sure I completely understand the scenario.

You have a VM with two disks and then you create a snapshot including the
two disks?
Before creating the snapshot, did the VM recognize the two disks?

On Mon, Nov 13, 2017 at 10:36 PM, Demeter Tibor <tdemeter at itsmart.hu> wrote:

> Dear Users,
>
> I have a disk of a vm, that is have a snapshot. It is very interesting,
> because there are two other disk of that VM, but there are no snapshots of
> them.
> I found this while I've try to migrate a storage-domain between two
> datacenter.
> Because, I didn't import that vm from the storage domain, I did an another
> similar VM with exactly same sized thin-provisioned disks. I have renamed,
> copied to here my originals.
>
> The VM started successfully, but the disk that contain a snapshot did not
> recognized by the os. I can see the whole disk as raw. (disk id, format in
> ovirt, filenames of images, etc) . I think ovirt don't know that is a
> snapshotted image and use as raw. Is it possible?
> I don't see any snapshot in snapshots. Also I have try to list snapshots
> with qemu-img info and qemu-img snapshot -l , but it does not see any
> snapshots in the image.
>
> Really, I don't know how is possible this.
>
> [root at storage1 8d815282-6957-41c0-bb3e-6c8f4a23a64b]# qemu-img info
> 5974fd33-af4c-4e3b-aadb-bece6054eb6b
> image: 5974fd33-af4c-4e3b-aadb-bece6054eb6b
> file format: qcow2
> virtual size: 13T (13958643712000 bytes)
> disk size: 12T
> cluster_size: 65536
> backing file: ../8d815282-6957-41c0-bb3e-6c8f4a23a64b/723ad5aa-02f6-
> 4067-ac75-0ce0a761627f
> backing file format: raw
> Format specific information:
>     compat: 0.10
>
> [root at storage1 8d815282-6957-41c0-bb3e-6c8f4a23a64b]# qemu-img info
> 723ad5aa-02f6-4067-ac75-0ce0a761627f
> image: 723ad5aa-02f6-4067-ac75-0ce0a761627f
> file format: raw
> virtual size: 2.0T (2147483648000 bytes)
> disk size: 244G
>
> [root at storage1 8d815282-6957-41c0-bb3e-6c8f4a23a64b]# ll
> total 13096987560 <(309)%20698-7560>
> -rw-rw----. 1 36 36 13149448896512 Nov 13 13:42 5974fd33-af4c-4e3b-aadb-
> bece6054eb6b
> -rw-rw----. 1 36 36        1048576 Nov 13 19:34 5974fd33-af4c-4e3b-aadb-
> bece6054eb6b.lease
> -rw-r--r--. 1 36 36            262 Nov 13 19:54 5974fd33-af4c-4e3b-aadb-
> bece6054eb6b.meta
> -rw-rw----. 1 36 36  2147483648000 Jul  8  2016 723ad5aa-02f6-4067-ac75-
> 0ce0a761627f
> -rw-rw----. 1 36 36        1048576 Jul  7  2016 723ad5aa-02f6-4067-ac75-
> 0ce0a761627f.lease
> -rw-r--r--. 1 36 36            335 Nov 13 19:52 723ad5aa-02f6-4067-ac75-
> 0ce0a761627f.meta
>
> qemu-img snapshot -l 5974fd33-af4c-4e3b-aadb-bece6054eb6b
>
> (nothing)
>
> Because it is a very big (13 TB) disk I can't migrate to an another image,
> because I don't have enough free space. So I just would like to use it in
> ovirt like in the past.
>
> I have a very old ovirt (3.5)
>
> How can I use this disk?
>
> Thanks in advance,
>
> Regards,
>
> Tibor
>
>
> _______________________________________________
> 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/20171116/65395804/attachment.html>