@Byte_Smarter I would try updating XCP first, I'm just not sure the impacts

don't know too if there are differences between migration and restoring a backup to the master/orchestra

@tjkreidl it was around 85% full.

@Byte_Smarter hard to tell whats happening. The Xen version here is 8.2

I read somewhere in other XCP documentation, that the SR has to be at least 30% free to do backup and coalesce jobs properly.

I think that was the problem here, the SR went full and we're unable to run any job. But i had to recreate the old SR to get a success response from Orchestra.

Did you try to migrate the VDI's to another SR?

@lucasljorge

thanks to @nikade and @dthenot for the quick response. I wiped out the "old SR" with coalesce issues after migrating. Seems to be running ok.

@Byte_Smarter

its ok buddy, please don't feel it, i'm following the discussion and trying to figure out whats happening too.
I added another SR and i'm monitoring the status. Still having performance issues (1 SR is SAS) but, the coalesce number seems to be finally decreasing.
Watching out the backup jobs running and keep you all in touch

@olivierlambert said in Issue with SR and coalesce:

It's really hard to tell, have you restarted also all the other pool members?

It resolved after i migrate from the SR to another (or to XCP host local storage). But we have scheduled backup jobs running everyday and i'm noticing the VDI to coalesce number is growing up again on these storages.

@Byte_Smarter said in Issue with SR and coalesce:

This seems to be a Python code error ? Could this be a bug in the GC script ?

I think so

@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