You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the -c option, a parameter should be added that calculates CRC/MD5 hash in case of differences in mtime, and the file is only moved if there is a difference.
The situation is not clear, but identical files are being synchronized from a NAS server - I assume because there has been a change in the mtime value.
And i see this in google cloud console web interface:
This situation is not constant, but there are files that have been uploaded multiple times, even though it is the same file being synchronized upwards.
Expected
Adding a new parameter that performs a content hash/crc check when the size is the same, but the mtime value is different.
The text was updated successfully, but these errors were encountered:
kamarton
changed the title
gsutil rsync -c alternative for if mtime is changed, then check hash
gsutil rsync -c alternative for if mtime is changed, then check hash (repeated file upload issue.)
Feb 22, 2023
Similar to the
-c
option, a parameter should be added that calculates CRC/MD5 hash in case of differences inmtime
, and the file is only moved if there is a difference.The situation is not clear, but identical files are being synchronized from a NAS server - I assume because there has been a change in the
mtime
value.I currently use this:
gsutil -m rsync -r -d "/sourcedir" gs://destination-bucket/
And i see this in google cloud console web interface:
This situation is not constant, but there are files that have been uploaded multiple times, even though it is the same file being synchronized upwards.
Expected
Adding a new parameter that performs a content hash/crc check when the size is the same, but the mtime value is different.
The text was updated successfully, but these errors were encountered: