koen84

On 1 server i've got better peering now (needed an extra restart though), but on the other it's still the same less than 5 peers.

Took 8h, then started to catch up. Catch up was combined with snapshot resume + aborting (which slows the chain sync a lot). Meanwhile it's back at compacting and not...

@guagualvcha any ideas ? The node keeps doing this "stopping chain sync for doing database compacting", preventing it from catch the chainhead.

And it's back with this idiocy. I'm ranging 90-95% disk used, which means 589G at 92% (you can run a fast node in that amount of storage still). While another...

@j75689 please take a look at this issue w.r.t. your call for feedback of syncing problems. Even if i sync at 40-55 blocks per minute (compared to chainspeed of 20bpm)...

Also, current disk usage is : * 85% (2.2 TiB free) * 71% (3.8 TiB free) * 88% (1.3 TiB free) So seems unlikely a factor, especially seeing all 3...

I'm actually at a point where my archive nodes compacting litterally endlessly (as in weeks).

Maybe it's a config difference, but my archive nodes don't have a separate ancient folder. Total size is currently 4.0 TiB (meaning a 4TB drive wouldn't cut it by approx...

@DefiDebauchery i went to check back, maybe i missed it before amidst the massive amount of output in the chaindata, but there's indeed an ancient folder : 107 GiB on...

RAID10 NVMe with 4x 4TB NVMe and it definitely grows like crazy. I started at 0.9TiB something 2-3 months ago. I don't know if the ancient blocks can be tweaked...