@henri9813 Can you share your logs (/var/log/SMlog + xensource.log) somewhere? I wonder if this error is triggered by a sm attach call.
Team - Storage
Posts
-
RE: Unable to add new node to pool using XOSTOR
-
RE: Backup fail whereas xostor cluster is "healthy"
@henri9813 Hi! Just to confirm, can you share the exception in the SMlog file of the master host? We are aware of an exception in the same style, and it is a side effect of another exception caused in the _snapshot function of LinstorSR. We have already planned to correct it in a new version of the sm, it's been a while that it's there but not critical. Thanks!
-
RE: Unable to add new node to pool using XOSTOR
@olivierlambert In 8.2 yes, linstor sm version is separated, it's not the case in 8.3 anymore.
-
RE: SR Garbage Collection running permanently
@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.
-
RE: SR Garbage Collection running permanently
@Razor_648 Hi,
The log you showed only mean that it couldn't compare two VDI together using their CBT.
It sometimes happen that a CBT chain become disconnected.Disabling leaf-coalesce mean it won't run on leaf, VHD chain will always be 2 depths deep.
You migrated 200 VMs, every disks of those VMs had snapshot made that then need to be coalesced, it can take a while.
Your backup then also do a snapshot each time while running that need to be coalesced.There are GC in both version of XCP-ng 8.2 and 8.3.
The GC is run independently of auto-scan, if you really want to disable it you can do it temporarily using/opt/xensource/sm/cleanup.py -x -u <SR UUID>
it will stop the GC until you press enter. I guess you could run it in a tmux to make it stop until next reboot. But it would be better to find the problem or if there really is no problem let the GC work until it's finished.
It's a bit weird to need 15 minutes to take a snapshot, it would point to a problem though.
Do you have any other error than the CBT one in your SMlog? -
RE: Possible to reconnect SR automatically?
@manilx No, nothing more to do, once installed this package remains present as long as you do not upgrade to a new major version of XCP-ng. But no issues regarding updates.
-
RE: SR Garbage Collection running permanently
@Razor_648 Do you have any exceptions in your /var/log/SMlog files?
-
RE: Possible to reconnect SR automatically?
@dwhitehead42 You can install the plug-late-sr RPM from our repo.
Then follow this documentation: https://github.com/xcp-ng-rpms/plug-late-sr/tree/master/SOURCES