Makes sense.
The notices I am getting look like this:
DEBUG : sftp://redacted@redacted.your-storagebox.de:23/dir: Running remote command: md5 -r /home/dir/81easprsgccat7rjn5ilo0qecg/at4trdqob9rqvfne8v4eulge4g
Or
DEBUG : 81easprsgccat7rjn5ilo0qecg/at4trdqob9rqvfne8v4eulge4g: Parsed hash: b2bc1c4d2431235495596ced2b9a12d0
Almost as if one part does not get decrypted
Another
DEBUG : 81easprsgccat7rjn5ilo0qecg/at4trdqob9rqvfne8v4eulge4g: Parsed hash: b2bc1c4d2431235495596ced2b9a12d0
that output looks good to me.
Ok, maybe I am not fully used to it. Was just not sure if it should look like this.
If it looks good this way then it is all good.
I guess at a 2nd look it makes sense just got thrown by “DEBUG”
Thank you
when rclone uploads a source file to S3, rclone calculates the md5 and saves the hash as metadata.
when rclone runs rclone check on a S3 remote, rclone reads the metadata, does not need to download the file.
whereas when the remote is sftp,
there is no pre-calculated hash, so rclone runs a shell command md5
Makes sense. Thank you for explaining!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.