Thank you for the support, hoping to help improve the resiliance of the
implementation.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt
Thanks Diego, I was able to reproduce it manually, shouldn't be too
difficult to fix
On Wed, Aug 31, 2022 at 5:37 PM Diego Ercolani wrote:
>
> This is the bug report I filled:
> https://bugzilla.redhat.com/show_bug.cgi?id=2123008
> ___
> Users mailing
This is the bug report I filled:
https://bugzilla.redhat.com/show_bug.cgi?id=2123008
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code
There is only one daemon.log per directory.
Here it is the archive for the daemon.log
https://cloud.ssis.sm/index.php/s/y6XxgH7CcrL5AC3
I will create the bug report referring this thread.
Thank you
___
Users mailing list -- users@ovirt.org
To
Thanks Diego, I checked one of the failures and I see:
2022-08-26 13:00:16,067Z ERROR
[org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-6
) [51fb711e-0fbc-4590-8ff0-638a041b13a5] Failed to extend proxy
I add also that I upgraded the engine on 2022-08-22 so I have the last "stable"
since then:
[root@ovirt-engine dbutils]# rpm -qi ovirt-engine-4.5.2.4-1.el8.noarch
Name: ovirt-engine
Version : 4.5.2.4
Release : 1.el8
Architecture: noarch
Install Date: Mon Aug 22 08:17:41 2022
One process that I killed was:
[root@ovirt-node4 ~]# ps axuww | grep qemu-nbd
vdsm 588156 0.0 0.0 308192 39840 ?Ssl Aug26 0:12
/usr/bin/qemu-nbd --socket
/run/vdsm/nbd/c7653559-508b-4e4a-a591-32dec3e5a29d.sock --persistent --shared=8
--export-name= --cache=none --aio=native
Do you have the logs (engine.log, vdsm.log) for this?
qemu-nbd holding the lock might mean the transfer was not finalized
properly and the nbd server was left open which should not happen...
On Wed, Aug 31, 2022 at 1:57 PM Diego Ercolani wrote:
>
> Thanks Arik,
> we have tried your solution but
Thanks Arik,
we have tried your solution but with no successful results.
we have gather also other infor and combined in this solution:
we have deleted on DB the row on vm_backups and vm_disk_map related to the
hanged backup.
The we have tried to delete shapshot locked , after the row db
On Mon, Aug 29, 2022 at 2:20 PM Diego Ercolani
wrote:
> Thank you for your support,
> I'm councious about the difficulty to keep everything in-line. I currently
> try to find the correct workload to make backup (using CBR) of VMs.
> I tryied both vprotect (with current tecnology preview) and
Thank you for your support,
I'm councious about the difficulty to keep everything in-line. I currently try
to find the correct workload to make backup (using CBR) of VMs.
I tryied both vprotect (with current tecnology preview) and Veeam (community
using RHV plugin) And I'm currently experiencing
On Fri, Aug 26, 2022 at 6:25 PM Diego Ercolani
wrote:
> Hello I saw there are other thread asking how to delete disk snapshots
> from backup operation.
> We definitively need a tool to kill pending backup operations and locked
> snapshots.
I Think this is very frustrating ovirt is a good piece
12 matches
Mail list logo
