--ignore-case-sync - strange behavior?

hi, i just found out that pCloud has case sensitive folders name, I would like to disable it

now if I use "--ignore-case-sync" flag with

rclone copy --ignore-case-sync "my hd folder" pCloud: ....

I have this strange behavior
if I have a pcloud folder called "test" (all lowercase) with 2 files, test1.txt and test2.txt and I copy two updated test1.txt and text2.txt from an hd folder called "TEST" (all in uppercase) everything works fine
but if insert a new file called test3.txt in "TEST" hd folder and copy again this folder to pCloud, now, on pCloud I have 2 folders
folder "test" with test1.txt and test2.txt
folder "TEST" with test3.txt

all new files are copied into "TEST" folder

is this normal behavior? how can I disable "case sensitive" entirely? thank you and sorry for my poor englis

What is your rclone version (output from rclone version)

last beta

Which OS you are using and how many bits (eg Windows 7, 64 bit)

windows 10 64bit

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


Can you share a log with debug of what you are running?

Hmm... My first thought is that this isn't going to work. --ignore-case-sync is for telling rclone that it made a mistake and actually the source or destination is case insensitive.

If the destination is actually case sensitive then you'll see problems like you've got where rclone tries to create a new directory called TEST and succeeds - what should have happened is that the "test" directory on pcloud should have been returned.

You are syncing from Windows, so you'll be using a case insensitive sync, so I would have thought that the problem will happen without the --case-insensitive flag? Can you try that?

yes, from windows, and whitout "--ignore-case-sync" on pCloud "TEST" is always created, in every case. it's not a big problem at the end. thank you

2020/09/07 15:15:09 DEBUG : rclone: Version "v1.52.3-339-gb6d3cad7-beta" starting with parameters ["rclone" "copy" "-vv" "--log-file=mylogfile.txt" "--ignore-case-sync" "--ask-password=false" "C:\\users\\main\\desktop\\test" "b4fmod:"]
2020/09/07 15:15:09 DEBUG : Using RCLONE_CONFIG_PASS password.
2020/09/07 15:15:09 DEBUG : Using config file from "C:\\Program Files (x86)\\PureBasic\\Sorgenti\\bfp4fmod\\B4FmodTools\\TEST\\rclone.conf"
2020/09/07 15:15:09 DEBUG : fs cache: renaming cache item "C:\\users\\main\\desktop\\test" to be canonical "//?/C:/users/main/desktop/test"
2020/09/07 15:15:10 DEBUG : TEST/test01.txt: Modification times differ by -4m13.721506s: 2020-09-07 15:14:55.721506 +0200 CEST, 2020-09-07 13:10:42 +0000 +0000
2020/09/07 15:15:10 DEBUG : TEST/test02.txt: Modification times differ by -4m12.2189479s: 2020-09-07 15:15:01.2189479 +0200 CEST, 2020-09-07 13:10:49 +0000 +0000
2020/09/07 15:15:10 DEBUG : pcloud root '': Waiting for checks to finish
2020/09/07 15:15:10 DEBUG : pcloud root '': Waiting for transfers to finish
2020/09/07 15:15:11 INFO  : TEST/test01.txt: Copied (replaced existing)
2020/09/07 15:15:11 INFO  : TEST/test02.txt: Copied (replaced existing)
2020/09/07 15:15:11 INFO  : TEST/test03.txt: Copied (new)
2020/09/07 15:15:11 INFO  : 
Transferred:   	        84 / 84 Bytes, 100%, 80 Bytes/s, ETA 0s
Checks:                 2 / 2, 100%
Transferred:            3 / 3, 100%
Elapsed time:         2.0s

2020/09/07 15:15:11 DEBUG : 5 go routines active

No worries! I can't think of a sensible work-around at the moment.

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