Can I use filename_encoding to work around case insensitive remotes such as OneDrive?

[brianjmurrell]

What is the problem you are having with rclone?

OneDrive is case insensitive, so case-collisions aside, restoring from a backup to OneDrive would lose all of the case sensitivity of my local (Linux ext4) filenames.

Will something like filename_encoding = base32768 in my OneDrive configuration resolve this issue?

If so, how can I rename the files in an existing copy on OneDrive without having to re-upload the whole local filesystem?

I have read Convert Filename Encoding but I am not using any crypt options in my config, so not sure how that maps.

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

rclone 1.60.1
- os/version: fedora 38 (64 bit)
- os/kernel: 6.3.4-201.fc38.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.3
- go/linking: dynamic
- 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)

rclone sync $source onedrive:/Backups/$dest \
       --local-case-sensitive     \
       --links                    \
       --delete-excluded          \
       --exclude-from excludes    \
       --progress

The rclone config contents with secrets removed.

[onedrive]
type = onedrive
token = [redacted]
drive_id = [redacted]
drive_type = business

[kapitainsky]

@brianjmurrell

OneDrive is case insensitive, so case-collisions aside, restoring from a backup to OneDrive would lose all of the case sensitivity of my local (Linux ext4) filenames.

No as it is case preserving so case-collisions aside everything will work.

@brianjmurrell

Will something like filename_encoding = base32768 in my OneDrive configuration resolve this issue?

It is crypt option only

[brianjmurrell]

But if I add crypt to my configuration, I will eliminate the case-collisions?

Does it make sense for the situations of case-collisions for rclone to be able to encode filenames even when not encrypting?

[kapitainsky]

@brianjmurrell

But if I add crypt to my configuration, I will eliminate the case-collisions?

It should - the best is to test.

@brianjmurrell

Does it make sense for the situations of case-collisions for rclone to be able to encode filenames even when not encrypting?

It is possible today - use crypt and set no-data-encryption = true

[kapitainsky]

Please note that base32768 is case sensitive though...

crypt base32768 file names encoding on case insensitive remotes (e.g. OneDrive) is not 100% safe

It is maybe theoretical as chances of collision for encrypted names is extremely low but if you want to be 100% safe use base32.