Syncing again in the other direction tries to copy files

What is the problem you are having with rclone?

I've synced my local drive to OneDrive for the first time. To double check everything is OK, I did a dry-run sync the other way round (OneDrive to local). The logs show some files would have been copied, and others deleted. What's wrong? There should be something I don't quite understand. I just want to be sure that the two drives contains exactly the same data. See below for commands and their output.

Run the command 'rclone version' and share the full output of the command.

rclone v1.61.1
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.19.0-35-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.4
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

OneDrive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

For the first sync

rclone sync  \
    --progress  \
    --fast-list  \
    --onedrive-chunk-size 65536000  \
    --transfers 20  \
    --checkers 20 \
    --copy-links  \
    --log-level INFO  \
    --log-file rclone_log.txt  \
    /media/oliver/Oliver\ HDD/ROOT/  \
    onedrive:/ROOT/

I don't have the initial output of this command. If I run it again, the log file is:

2023/03/05 12:14:26 INFO  : There was nothing to transfer
2023/03/05 12:14:26 INFO  : 
Transferred:   	          0 B / 0 B, -, 0 B/s, ETA -
Checks:            351657 / 351657, 100%
Elapsed time:     26m57.4s

I thought this output means: "source and destination are the same".

For the dry test sync, I do

rclone sync  \
    --dry-run  \
    --progress  \
    --fast-list  \
    --onedrive-chunk-size 65536000  \
    --transfers 20  \
    --checkers 20 \
    --copy-links  \
    --log-level INFO  \
    --log-file rclone_log.txt  \
    onedrive:/ROOT/  \
    /media/oliver/Oliver\ HDD/ROOT/ 

And the log file is (Information inside [brackets] is written by me):

[there were more than 100.000 lines with contents similar to:]
2023/03/05 13:32:05 NOTICE: [filename deleted for privacy]: Skipped remove directory as --dry-run is set
2023/03/05 13:32:10 NOTICE: [filename deleted for privacy]: Skipped delete as --dry-run is set (size 5.686Ki)
2023/03/05 13:02:50 NOTICE: [filename deleted for privacy]: Skipped copy as --dry-run is set (size 7.604Mi)
2023/03/05 13:32:05 NOTICE: 
Transferred:   	    2.593 GiB / 2.593 GiB, 100%, 14.712 MiB/s, ETA 0s
Checks:            351657 / 351657, 100%
Deleted:            54580 (files), 8420 (dirs)
Transferred:        54580 / 54580, 100%
Elapsed time:     29m23.5s

I thought this output means: "source and destination are NOT the same", so I don't know what to think.

I've manually checked some of the files that the second command would copy. They exist both in source and destination, with same size and mod date.

The rclone config contents with secrets removed.

conf
[onedrive]
type = onedrive
client_id = [REMOVED]
client_secret = [REMOVED]
token = [REMOVED]
drive_id = [REMOVED]
drive_type = personal

can you pick a single file, in source and dest and post the output of rclone lsl

or run rclone check

Hi @asdffdsa , thanks for the quick answer!

I think I found the problem when trying to execute those commands. I have the same files and dirs in local and onedrive, but some of them differ in filename (just by case).

For example, in local I have: "photo.PNG", but in OneDrive its name is "photo.png". Also, some directories with the first letter uppercase has all letters lowercase in OneDrive.

Since OneDrive is case insensitive, sync from local to OneDrive doesn't do anything, but the reverse does.

I just renamed the files in local to match the OneDrive files, so the problem is fixed. The real question is why the filename mismatch. In the case of "photo.PNG", I think OneDrive may normalize all file extensions. But the couple directories that lost the first uppercase letter really bother me...

Anyway, my problem is fixed, thanks!

how about --ignore-case-sync

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.