Nice script. How hard would it be to add support for SHA1? I ask because it would be useful to be able to sync two mirrored data sources (i.e., two hard drives that don’t reside in the same PC where you would typically use ZFS, BTRFS, or RAID) and verify integrity between the sources with something like “rclone check”. If rclone detects a sha1 hash difference between the two data sources (i.e., from bitrot or unintended modification), you can look to your database to determine which file is correct and recover that file to replace the modified file on the other source. To my knowledge, rclone can detect differences/modifications in files based on sha1 but it does not have the knowledge as to which file is correct. The right solution is probably to add SHA512 to rclone, but that’s harder.
https://rclone.org/commands/rclone_check/
Nice script. How hard would it be to add support for SHA1? I ask because it would be useful to be able to sync two mirrored data sources (i.e., two hard drives that don’t reside in the same PC where you would typically use ZFS, BTRFS, or RAID) and verify integrity between the sources with something like “rclone check”. If rclone detects a sha1 hash difference between the two data sources (i.e., from bitrot or unintended modification), you can look to your database to determine which file is correct and recover that file to replace the modified file on the other source. To my knowledge, rclone can detect differences/modifications in files based on sha1 but it does not have the knowledge as to which file is correct. The right solution is probably to add SHA512 to rclone, but that’s harder.
https://rclone.org/commands/rclone_check/