@olivierlambert it has happened again

"XXXXX-nfs-02 (FAST all Flash Storage ZFS/NFS): failed to unpause tapdisk","Failed to unpause tapdisk for VDI ab867371-7a74-4a9f-88a9-9fb89e7dd3de, VMs using this tapdisk have lost access to the corresponding disk(s)","XXXXX XXXX-xcp Pool","Oct 23, 2025 8:18 PM",""

VM for this VDI had been running on host XXX-xcp-03 but there were attachments on the vdi from host XXX-xcp-07 .

we did not manually move this VM but it has moved.

I really think this problem is getting caused by load balancer moving things around while delta backups are running.

can we look into having XOA LB plugin NOT move VM's getting touched by the XOA backup processes?

@DustinB thats not the point of the post.

the point of the post is on HTTP connection has timed out, the TASK never actually times out on the proxy.

I am aware it says space issues on the SR and its unfortunate that error is in the screen shot but its a distraction, not the actual problem.

XOA 5.110.1
XOA Proxy involved is version 0.29.30

we have a backup task that is refusing to time out. the only way i can get this to end is by restarting the proxy

this has been an issue sense the new backup process was introduced.

timeout for the task is set to 8 hours but XOA and the XOA proxy seem to not care what this value is.. it just sits there and is keeping the VDI's locked.

dont get hyper focused on this next screen shot, it has nothing todo with the actual issue, just showing that even though the process is timed out but running.. the VID's are still locked by the host

Thanks

I have, what is hopefully a final update to this issue(s).

we upgraded to xoa version .99 a few weeks ago and the problem has now gone away. we suspect that some changes were made for timeouts in xoa that have resolved this , and a few other related problems.