XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)

itservices

Hi @pierrebrunet.

I have deleted the "parentless" VDIs and snapshots.

So the "Unhealthy VDI" page is empty for me.

So everytime I retry with the VM in question it is creating a new (full) backup-chain.

Regards,
Marc

itservices

Quick Update:

Was looking good with commit cf26d.

After the transfer completed the VDI of that particular VM was still in use, according to XO.

So still failure on the job.

Regards,
Marc

itservices

With commit caa17 the transfer did not happen again and fails the with the known message.

Regards,
Marc

pierrebrunet

@itservices
Can you export your logs with xen-bugtool --yestoall please? If you prefer to avoid exporting everything, we especially need /var/log/xensource.log and /var/log/SMlog
@Team-Storage do you have an idea about the source of the issue?

itservices

Hi @pierrebrunet

With commit c74a8 the problem is still present but the transfer was completed again.

Unfortunately my installation does not recognize the "xen-bugtool" command. And both log files are not present.

Is this something that needs enabling after install of XCP-NG?

Unfortunately and unnoticed my syslog-server did not receive any messages from XCP-NG in the last 30 days.

Other inputs work

**Edit:

I have deleted and re-added the syslog-server with port and now logs are being send to Graylog.**

Thanks for your assistance y'all.

Regards,
Marc

pierrebrunet

@itservices Hi, xen-bugtools is in xcp-ng hosts. You can directly get the logs from the hosts if you don't have the command.

itservices

Evening @pierrebrunet

My bad.

I am now on commit b440f and the issue persist.

I have written you a message with the link to the file.

Regards,
Marc

itservices

Just to give an update.

I still am having the issue with current commit 090ce.

Regards,
Marc

simonp

@itservices Hello,

I'm taking this issue from Pierre.

Did you perform a full restart of the XCP-ng host since the issue occured ? Or just restarted the toolstask ?

itservices

Hi @simonp

The host was restarted regularly. After every update I restart the host and consequently all VMs running on it. The XOA VM is also running on that host.

Regards,
Marc