My setup is the following: I have an encrypted volume (historically it’s CryFS, but could change if needed) that I am syncing to S3 with Rclone. So what I do in my script is:
#Mount entrypted volume
cryfs /mnt/media/encrypted/volume /home/mine/decrypted
#Rclone it to S3
rclone -v sync /home/mine/decrypted amazonS3:
It basically does it’s job, but the problem is it updates not only modified and new files on remote, but also files that I merely accessed on the local volume. I.e. if I open the file read-only and then sync, rclone will say
2017/05/01 02:30:15 INFO : (some file): Copied (replaced existing)
although ll of that file will say
-rw-rw-r-- 1 user group 491520 Apr 12 21:17 (some file)
Apr 12 being before the previous sync.
So the question is - how rclone decides whether to update the file or not and are there any possible hiccups while working with FUSE local volumes? I understand that this problem can be more of CryFS, but at least I’d like to understand the exact cause. Some configs exist maybe that command how rclone diffs files?
Note the change of filesize between the two. So of course Rclone synced it at next run.
Filesize does not change if the same client downloads another file from outside a mounted partition (i.e. /home/user/dir), so has to be something to do with SFTP and FUSE maybe. The workaround for me was to switch to SCP instead - which works fine.
In any case, thanks for your advice - got me digging