What is the problem you are having with rclone?
Mega doesn't support checksum or modtime as of now, so the only way to check is size.
I'm syncing a file in which only few bytes change and size remains same. Is there a way to force upload file with mega, even if same size?
I don't want to go the route of deleting the file first and then uploading it, because it has it's own risks. The --ignore-size command also doesn't seem to work for my case and does nothing for mega.
Run the command 'rclone version' and share the full output of the command.
rclone v1.60.1
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-1022-oracle (aarch64)
- os/type: linux
- os/arch: arm64
- go/version: go1.19.3
- go/linking: static
- go/tags: none
Which cloud storage system are you using? (eg Google Drive)
Mega
The command you were trying to run (eg rclone copy /tmp remote:tmp)
# rclone copy $HOME/bw/data/bitwarden/data.json mega_mini: -P --ignore-size -vvv
2022/12/11 02:04:29 DEBUG : rclone: Version "v1.60.1" starting with parameters ["rclone" "copy" "/root/bw/data/bitwarden/data.json" "mega_mini:" "-P" "--ignore-size" "-vvv"]
2022/12/11 02:04:29 DEBUG : Creating backend with remote "/root/bw/data/bitwarden/data.json"
2022/12/11 02:04:29 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2022/12/11 02:04:29 DEBUG : fs cache: adding new entry for parent of "/root/bw/data/bitwarden/data.json", "/root/bw/data/bitwarden"
2022/12/11 02:04:29 DEBUG : Creating backend with remote "mega_mini:"
2022-12-11 02:04:31 DEBUG : data.json: Sizes identical
2022-12-11 02:04:31 DEBUG : data.json: Unchanged skipping
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Checks: 1 / 1, 100%
Elapsed time: 2.6s
2022/12/11 02:04:31 INFO :
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Checks: 1 / 1, 100%
Elapsed time: 2.6s
2022/12/11 02:04:31 DEBUG : 8 go routines active```