@olivierlambert looks like XO got a bad cache with that storage.

on same physical storage i have 2 shares connected to pool. All vm is usualy at 1st.
So i moved broken VDI to 2nd, made few backups, everything works fine. Then moved VDI back to 1st, got this error again.

Any options how to fix that without migrating all VMs and removing this storage?

@Danp was a something here before, but now it empty.
i'll wait few more days to be sure is it still broken or not.

@Tristis-Oris orchestra log. 14 VMs, 2 failed. 2022-05-20T11_00_00.005Z - backup NG.txt

@Danp delta backups. some once 24hours, other 8hours.

@olivierlambert updated to commit 30874.
after that all broken backup was fixed without moving vdi.
but after 1-2 iterations same error again, on same VMs.

manual backup works always? (as i see), scheduled fail from time to time.

@olivierlambert from sources.
Xen Orchestra, commit 25183
xo-server 5.93.0
xo-web 5.96.0

Greetings.
last few days receive this errors. Works fine for a months before.

• have 3 pool, but errors only at 1 of them.
• all pools at same network, backup at same 2 storages.
• it begins at 3-4 VMs, but today 2 more backup broken too. One of VM just created, so almost have no backup chain.
• after moving disk to another storage backup chain fixed.

weird that it happens only at 1 pool. It have no any errors with a link to storage or network. Empty space is enough too.

is it possible if link down between XO and pool during backup? this pool located in another place. this is the only difference.

found nothing at SMlog, only at XO syslog.

UUID: e8e86755-8e74-e078-8c43-955a7d521df4
    Start time: Thursday, May 19th 2022, 6:04:29 am
    End time: Thursday, May 19th 2022, 6:04:36 am
    Duration: a few seconds
    Reason: (unhealthy VDI chain) Job canceled to protect the VDI chain

2022-05-18T21:12:15.067Z xo:backups:mergeWorker FATAL ENOENT: no such file or directory, rename '/mnt/vc-2600-1/xo-vm-b>
 error: [Error: ENOENT: no such file or directory, rename '/mnt/vc-2600-1/xo-vm-backups/.queue/clean-vm/_20220518T211039Z-p7h0kr8o71d' -> '/mnt/vc-2600-1/xo-vm-backups/.queue/clean-vm/__20220518T211039Z-p7h0kr8o71d'] {
 errno: -2,
 code: 'ENOENT',
 syscall: 'rename',
 path: '/mnt/vc-2600-1/xo-vm-backups/.queue/clean-vm/_20220518T211039Z-p7h0kr8o71d',
 dest: '/mnt/vc-2600-1/xo-vm-backups/.queue/clean-vm/__20220518T211039Z-p7h0kr8o71d'

2022-05-18T10:00:54.337Z xo:backups:DeltaBackupWriter WARN checkBaseVdis {
  error: [Error: ENOENT: no such file or directory, scandir '/mnt/vc-2600-1/xo-vm-backups/06ff383c-6c59-7293-98f5-9ed62745e567/vdis/9f3f2ced-14b7-4857-8a07-e7fb1acce485/260dac24-cad6-4362-ab9f-0a872e1c08f2'] {
    errno: -2,
    code: 'ENOENT',
    syscall: 'scandir',
    path: '/mnt/vc-2600-1/xo-vm-backups/06ff383c-6c59-7293-98f5-9ed62745e567/vdis/9f3f2ced-14b7-4857-8a07-e7fb1acce485/260dac24-cad6-4362-ab9f-0a872e1c08f2'

@shinuza got it, thanks. sad of course(

"ansible needs a stable unique id to identify hosts"
not realy, with manual host lists awx download new every time and remove old\chenged info.
same for netbox integration.

for most of task just enough tags like linux, db, etc.

is it any way to translate uuid to names at inventory?

@shinuza it's a password.

with long one with symbols xo-cli can't register.
changed to simple, it works now.

tried "" or '' in playbook, it didnt work.