![]() That’s a band-aid, though, the issue is still there. (But I’m happy, because at least it’s running without errors). 08:11:01.226 TRACE CHUNK_FOSSILIZE The chunk f0f87b5d7404c3c33743dc2630ab15a174a2f63edf5faabe3ceafcd18cb45aab has been marked as a fossilĪnd I don’t quite understand why this would involve so much bandwith either. between 1 and 10 seconds for a single chunk: 08:10:10.630 TRACE CHUNK_FOSSILIZE The chunk 88256ce8cdc36831ef7c9b9ad96b3651c03b596e552bd42a3b2ba3cb5eb2b7be has been marked as a fossil ![]() Not sure if that is a limitation imposed by the pcloud api, but I do wonder why pruning fossilizing chunks takes so long, i.e. According to nethogs rclone is using about 4-500 kB/s bandwith for the prune job. ![]() I’ll try it once my current pruning job is through. Yes, that should do the trick! Sometimes solutions can be so simple
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |