![Pcloud webdav synology](https://knopkazmeya.com/4.png)
![pcloud webdav synology pcloud webdav synology](https://www.apponic.com/storage/images/37/36/510d291763145d80b9ff8b5486637c09.png)
![pcloud webdav synology pcloud webdav synology](https://www.bluescreengenerator.de/user/pages/02.blog/45.synology-nas-in-magentacloud-sichern-mit-webdav/hyperbackup_05.png)
![pcloud webdav synology pcloud webdav synology](https://tkcl.me/wp-content/uploads/2022/09/%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2022-09-11-7.38.04-285x300.jpg)
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
![Pcloud webdav synology](https://knopkazmeya.com/4.png)