`rclone sync` to a backend neither supporting modification times nor checksums

What is the problem you are having with rclone?

I would like to sync to remote (Sia to be exact) which states the following limitations:

  • Modification times not supported
  • Checksums not supported

Am I right that this does leave me with only a comparison based on file sizes?

Might the following settings (set to 0, -1, unlimited?) be a workaround to get reliable sync?

--cache-info-age Duration How long to cache file structure information (directory listings, file size, times, etc.) (default 6h0m0s)

Run the command 'rclone version' and share the full output of the command.

# rclone version
rclone v1.53.3-DEV
- os/arch: linux/amd64
- go version: go1.15.9

I have to update to 1.59 for SIA, however, so consider the question for latest rclone version.

Which cloud storage system are you using? (eg Google Drive)


Yes, but you could wrap the sia backend in the hasher backend and I think this would fix your problem, provided files didn't get modified directly in the sia repository and were always modified through the hasher backend.

1 Like

Perfect. I did not stumble over the hasher backend. That's even better than I could have imagined.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.