Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide option to use checksum (e.g. MD5) to compare and validate source and remote files #5

Open
WayneSherman opened this issue Jul 27, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@WayneSherman
Copy link

rclonesync-V2 uses rclone lsl to cache file metadata to speed up compare operations. The lsl output does not include checksums, so there isn't a way to confirm the local and remote files are are binary match of each other.

Using "rclone remote:path lsjson --hash" to cache file metadata provides hashes (if available) which can be used for comparison operations and to validate uploads and downloads to confirm that local and remote files are binary matches.

Making use of the hashes will provide higher confidence of file integrity, and caching them can speed up the compare operation. At present, rclone sync --checksum can take a long time since it has to compute local hashes on every run.

See also:
RClone should support a cache of checksums for local files to avoid redundant work
Cache MD5s
rclone md5sum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants