pCloud doesn't use internal pCloud hash, this is why rclone dedupe takes so much time, because it has to fetch sha1-hashes individually than using the already provided pCloud hash

What is the problem you are having with rclone?

The command

rclone dedupe --dry-run --fast-list --by-hash -vv pcloud:

takes A LOT of time to find anything!! I stopped it after an hour

The reason is that it is getting the sha1-hashes individually. But it doesn't need to do that, because pCloud is able to deliver the folders and files recursively with it's own pCloud hash in just one single request. Here are the docs.

So could you please use the pCloud hash for rclone dedupe? And please also return the pCloud hash, if I list my files via

rclone lsjson pcloud:

Even better would be, if you directly return the JSON, which you receive by pCloud here.

And even better would be, if the pCloud hash would be globally accepted, so that it would be even checked, if I do a sync between two different pCloud accounts. This would reduce all multiple sha1-requests to just one single request.

And if someone asks pCloud, how this hash is made, maybe it would even be possible to compare the pCloud hash to local files in one single request.

What is your rclone version (output from rclone version)

rclone v1.68.1

• os/version: darwin 11.7.10 (64 bit)
• os/kernel: 20.6.0 (x86_64)
• os/type: darwin
• os/arch: amd64
• go/version: go1.23.1
• go/linking: dynamic
• go/tags: cmount

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

Mac OS X 11.7.10 - 64 Bit

Which cloud storage system are you using? (e.g. Google Drive)

pCloud

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

rclone dedupe --dry-run --fast-list --by-hash -vv pcloud:

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

2024/10/15 01:22:36 DEBUG : rclone: Version "v1.68.1" starting with parameters ["rclone" "dedupe" "--dry-run" "--fast-list" "--by-hash" "-vv" "pcloud:"]
2024/10/15 01:22:36 DEBUG : Creating backend with remote "pcloud:"
2024/10/15 01:22:36 DEBUG : Using config file from "/Users/masr/.config/rclone/rclone.conf"
2024/10/15 01:22:36 INFO : pcloud root '': Looking for duplicate sha1 hashes using interactive mode.

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Start with the pCloud folder/listfolder API documentation and the rclone paths exercised by dedupe --by-hash and lsjson. Determine how the pCloud hash is currently exposed and what the existing hash interfaces require; done means the requested pCloud hash behavior is defined and supported without the individual SHA-1 requests described here.