@olivierlambert restarted the master, nothing happened

@olivierlambert
not yet, restarting will force coalesce?

@olivierlambert
no, there is no coalesce errors in SMlog.

the only error in log is "SMGC: [23240] * * * * * SR 3a5b6e28-15e0-a173-d61e-cf98335bc2b9: ERROR
Feb 19 12:34:39 SMGC: [2234] gc: EXCEPTION <class 'XenAPI.Failure'>, ['XENAPI_PLUGIN_FAILURE', 'multi', 'CommandException', 'Input/output error']"

@olivierlambert
We dont have pro support
Our version is 8.2

I was looking into the forum for a solution, but i dont find it...

A few days ago, our SR here in the company filled up completely, causing a problem executing the scheduled backups jobs in our routine. We find out the problem and add some space in out storage to run the jobs again, but we are getting a "Job canceled to protect the VDI chain". Also there is a list of VDI to coalesce that only goes up and now is in 160. Some VMs are getting backuped, but the majority are getting that job canceled to protect VDI chain error.

Searching for the logs, i cant find any coalesce running in the XCP. I read that when rescan the SR the XCP does the coalesce automatically, but i cant find the process running out.

What can i do to run all the backup jobs sucessfully again? We have to stop all backup jobs and wait the coalesce to run? How can we track this?

Thanks in advance