What is the problem you are having with rclone?
I would like to clarify what happens when running rclone bisync --resync
, regarding keeping the most up-to-date files.
The offical docs say:
"
When using --resync
, a newer version of a file either on Path1 or Path2 filesystem, will overwrite the file on the other path (only the last version will be kept). Carefully evaluate deltas using --dry-run.
"
ref: Bisync
This makes sense to me, and is what should happen. However, a forum post says:
"
Mostly correct. However, during a --resync run:
Warning: Path1 files may overwrite Path2 versions.
In other words, if a different versions of a file exist on both paths, only the path1 version will survive.
"
ref: Is bisync ready for prime time? - #8 by cjnaz
and in my actual usage, this is what I find actually happens.
Shouldn't it be that the first scenario is what happens : that the most up-to-date file is kept during --resync
(so that whether it is on Path1 or Path2 it is copied to the other path)?
Run the command 'rclone version' and share the full output of the command.
rclone v1.62.2
- os/version: debian bookworm/sid (64 bit)
- os/kernel: 6.2.6-76060206-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.20.2
- go/linking: static
- go/tags: none
Which cloud storage system are you using? (eg Google Drive)
onedrive for business
The command you were trying to run (eg rclone copy /tmp remote:tmp
)
(see above)
The rclone config contents with secrets removed.
?