I going try this steps:
- power off the VM's
- delete the snapshots.

Thanks.


2016-05-13 17:45 GMT-03:00 Greg Padgett <gpadgett@redhat.com>:
On 05/13/2016 02:42 PM, Marcelo Leandro wrote:
Hello Greg,
     You can help me?

Thanks.

Hi Marcelo,

I see in your engine log that one of the images can't be found when a merge is attempted:

  VDSErrorException: Failed to MergeVDS, error = Drive image file could
  not be found, code = 13

There were some recent fixes to Live Merge that help is progress beyond this particular error, see [1] for details on that.  The fix is in 3.6.6.

It might be helpful to check the vdsm log to see what happened on the host when the first merge on that snapshot was attempted.  It should be in the Host04 log around time 2016-05-11 19:33:43.

Thanks,
Greg

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1327140



2016-05-11 19:56 GMT-03:00 Marcelo Leandro <marceloltmm@gmail.com
<mailto:marceloltmm@gmail.com>>:


    hello,

    i have problem other vm now:
    the vm contain two disk, only a09bfb5d-3922-406d-b4e0-daafad96ffec
    mark illegal in snapshot tab.

    information database:
      imagestatus |           storage_pool_id            |
      storage_domain_id           |            image_group_id            |
                  im
    age_guid              |               parentid
    -------------+--------------------------------------+--------------------------------------+--------------------------------------+----------------
    ----------------------+--------------------------------------
                1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
    0dc658da-feed-498b-bfd2-3950f7198e11 |
    e94d711c-b50b-43bd-a67c-cb4643808d9d | b9478a6c-28c5-4
    03b-a889-226d16d399a5 | 00000000-0000-0000-0000-000000000000
                1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
    6e5cce71-3438-4045-9d54-607123e0557e |
    05aab51a-8342-4d1f-88c4-6d733da5959a | 023110fa-7d24-4
    6ec-ada8-d617d7c2adaf | a09bfb5d-3922-406d-b4e0-daafad96ffec
                4 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
    6e5cce71-3438-4045-9d54-607123e0557e |
    05aab51a-8342-4d1f-88c4-6d733da5959a | a09bfb5d-3922-4
    06d-b4e0-daafad96ffec | 00000000-0000-0000-0000-000000000000

    erro msg :
    Failed to delete snapshot 'Backup the VM' for VM 'vm-name.


    vm-disk-info.py output:

    Disk e94d711c-b50b-43bd-a67c-cb4643808d9d
    (sd:0dc658da-feed-498b-bfd2-3950f7198e11)
    Volumes:
             b9478a6c-28c5-403b-a889-226d16d399a5
         Disk 05aab51a-8342-4d1f-88c4-6d733da5959a
    (sd:6e5cce71-3438-4045-9d54-607123e0557e)
    Warning: volume 023110fa-7d24-46ec-ada8-d617d7c2adaf is in chain but
    illegal
         Volumes:
             a09bfb5d-3922-406d-b4e0-daafad96ffec

    engine.log :

    https://www.dropbox.com/s/yfsaexpzdz3ngm1/engine.rar?dl=0

    Thanks.


    2016-05-11 18:39 GMT-03:00 Greg Padgett <gpadgett@redhat.com
    <mailto:gpadgett@redhat.com>>:


        On 05/11/2016 09:49 AM, Marcelo Leandro wrote:

            hello,
            i have problem for delete one snapshot.
            i see the  error:
            Due to partial snapshot removal, Snapshot 'Backup the VM' of
            VM 'vmname'
            now contains only the following disks: 'vmdiskname'.


            Failed to delete snapshot 'Backup the VM' for VM 'vmname'.


        Hi Marcelo,

        Can you try to remove the snapshot again and attach the engine log
        if it fails?

        Thanks,
        Greg

            information in db :
               imagestatus |           storage_pool_id            |
               storage_domain_id           |            image_group_id
                     |
                       im
            age_guid              |               parentid
            -------------+--------------------------------------+--------------------------------------+--------------------------------------+----------------
            ----------------------+--------------------------------------
                         1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
            6e5cce71-3438-4045-9d54-607123e0557e |
            bfb1e6b5-7a06-41e4-b8b4-2e237ed0c7ab | 1bb7bd08-5ee8-4
            a3b-8978-c15e15d1c5e4 | 6008671c-2f9d-48de-94f3-cc7d6273de31
                         4 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
            6e5cce71-3438-4045-9d54-607123e0557e |
            bfb1e6b5-7a06-41e4-b8b4-2e237ed0c7ab | 6008671c-2f9d-4
            8de-94f3-cc7d6273de31 | 00000000-0000-0000-0000-000000000000


            output the script vm-disk-info.py


               Disk bfb1e6b5-7a06-41e4-b8b4-2e237ed0c7ab
            (sd:6e5cce71-3438-4045-9d54-607123e0557e)
            Warning: volume 1bb7bd08-5ee8-4a3b-8978-c15e15d1c5e4 is in
            chain but illegal
                  Volumes:
                      6008671c-2f9d-48de-94f3-cc7d6273de31
                      1bb7bd08-5ee8-4a3b-8978-c15e15d1c5e4


            output the  command md5sum :
            volume :   1bb7bd08-5ee8-4a3b-8978-c15e15d1c5e4
            4c05c8258ed5746da6ac2cdb80c8974e
            1bb7bd08-5ee8-4a3b-8978-c15e15d1c5e4

            ec74d4d8189a5ea24720349868ff7ab7
            1bb7bd08-5ee8-4a3b-8978-c15e15d1c5e4

            the volume change

            output the command md5sum :
            volume: 6008671c-2f9d-48de-94f3-cc7d6273de31

            86daf229ad0b65fb8be3a3de6b0ee840
            6008671c-2f9d-48de-94f3-cc7d6273de31

            86daf229ad0b65fb8be3a3de6b0ee840
            6008671c-2f9d-48de-94f3-cc7d6273de31

            the volume not change

            Thanks.


            _______________________________________________
            Users mailing list
            Users@ovirt.org <mailto:Users@ovirt.org>
            http://lists.ovirt.org/mailman/listinfo/users