I'm trying to sync local files to B2. I'm able to run sync successfully, but after one hour (+/- 5 min; I measured), new files on the remote are gone, and ones that were deleted are restored. I checked this by running lsl before sync, immediately after sync, and one hour later, and then doing a 3-way diff of them.
I'm up-to-date on my bill, so my only theories are rclone not finalizing sync uploads correctly, using a cache for the second lsl (and the files never actually got uploaded), or B2 is actually losing them. I also verified that my filenames+paths aren't too long.
Run the command 'rclone version' and share the full output of the command.
- os/version: Microsoft Windows 10 Pro 2009 (64 bit)
- os/kernel: 10.0.19043.1526 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.17.2
- go/linking: dynamic
- go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone sync and rclone lsl is not a daemon, does not run in the background, does not cache anything.
so if after rclone sync had successfully uploaded the files, and then, the newly sync files are gone.
i would focus on the b2 website, looking at a log file.
after the rclone sync, what objects go missing.
--- source files that did not exist in the dest, so first time copied?
--- source files that are different from existing dest, so source overwrites the dest?
if versioning enabled, have to look at that, what did b2 do with the existing dest file?
this should be easy to replicate.
in a local directory on local,
--- modify a file that already exists in the dest, can just change the modtime timestamp.
--- create a new file in the same dir
using that same dir as the source, rclone sync -vv. -vv will output rclone debug info.
post the full debug log, really need to see a debug log.
Well this is embarrassing. I think I figured it out. I realized I have another machine syncing an old version of the data periodically. I'm still confirming, but rclone and B2 are fine, I just forgot about an old cronjob.