SR Garbage Collection running permanently

Tristis Oris

@Danp
VDIs was migrated 8.2>8.3. Without snapshots, because of CBT.
Other pools was migrated by same way and have no such issue.

i can't remember anything special, why that could happens.

Danp

@Tristis-Oris There's a fix for the time out during leaf coalesce on XCP-ng 8.3 that should be released soon. You can install it now with the following command --

yum install https://updates.xcp-ng.org/8/8.3/testing/x86_64/Packages/sm-3.2.3-1.15.xcpng8.3.x86_64.rpm https://updates.xcp-ng.org/8/8.3/testing/x86_64/Packages/sm-fairlock-3.2.3-1.15.xcpng8.3.x86_64.rpm

Tristis Oris

@Danp reboot is required?

flakpyro

@Tristis-Oris

I have ran into this numerous times. Its one of the reasons i have not switched to "Purge Snapshot data when using CBT" on all my jobs yet.

I hope the fixes in testing solve the issue, what has been fixing it for me in the meantime is modifying the following:

Edit
/opt/xensource/sm/cleanup.py :
Modify LIVE_LEAF_COALESCE_MAX_SIZE and LIVE_LEAF_COALESCE_TIMEOUT to the following values:

LIVE_LEAF_COALESCE_MAX_SIZE = 1024 * 1024 * 1024 # bytes
LIVE_LEAF_COALESCE_TIMEOUT = 300 # seconds

Danp

@Tristis-Oris Not AFAIK but it wouldn't hurt to be sure that the latest fixes are running.

Tristis Oris

@Danp

install patch, reboot pool.
GC job started during restart and stuck at 0%, so i restart toolstack again.
now nothing is running, bad snapshots not disappeared.

Should i wait longer or?

Danp

@Tristis-Oris Did you install the patch on all of the hosts in the pool? Have you tried rescanning an SR to kick off the GC process?

Tristis Oris

@Danp after some time GC task started automaticaly and running for 1 hour already. Still about 50%.

Tristis Oris

@Tristis-Oris GC done, ~5 items removed, ~20 left.

olivierlambert

Good, so it is working

Tristis Oris

@olivierlambert is it some limit for items removal per run?

olivierlambert

The GC is doing one chain after another. We told XenServer team back in 2016 that it could probably merge multiple chains at once, but they told us it was too risky. So we did not focus on that. Patience is key there. Clearly, we'll do better in the future.

Tristis Oris

@olivierlambert got it. Will see what happens in few days.

olivierlambert

It will accelerate. First merges are the slowest ones, but then it's going faster and faster.