@Andrew Hello Andrew,
Thank you for reporting.
It appear that the CBT on FileSR-based SR is not working in addition to data-destroy (the option that allow to remove the VDI content and only keep the CBT).
Can you confirm that you are using a FileSR (ext or nfs)?
Is it possible to disable purge data on the CR job?
@acebmxer Hello,
The error VDI_CBT_ENABLED means that the XAPI doesn't want to move the VDI to not break the CBT chain.
You can disable the CBT on the VDI before migrating the VDI but if you have snapshots with CBT enabled it can be complicated and it might necessitate to remove them before moving the VDI.
We have changes planned to improve the CBT handling in this kind of case.
@andrewperry Hi, we are working on 2 things:
snapshot-of field is garbage.snapshot-of already present on affected pools.@User-cxs Ping @xen-orchestra for additional help regarding this trace.
Concerning LINSTOR, you don't have to manually configure it using yum/systemctl. The controller must never be started like this, please stop it with:
systemctl disable --now linstor-controller
For you info it's started automatically by another service and to mount the DB volume list of the SR. Otherwise, this information is not shared across all hosts.
