Rclone does not backup file containing `ô` character

Suspected Bug
1

What is the problem you are having with rclone?

rclone does not backup folder content if folder name contains ô character. I had to replace ô by o to fix the problem.

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

rclone v1.65.1
- os/version: darwin 12.7.1 (64 bit)
- os/kernel: 21.6.0 (x86_64)
- os/type: darwin
- os/arch: amd64
- go/version: go1.21.5
- go/linking: dynamic
- go/tags: cmount

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

SFTP/SSH

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

rclone -Lv --log-file=/tmp/rclone.log --filter-from /usr/local/etc/rclone/filter_mbp.txt sync ~ Safe:/MBP/ \
           --backup-dir Safe:/OLD/MBP/$date

The rclone config contents with secrets removed.

[Safe]
type = crypt
remote = Hurd:/home/lota/RESCUE
filename_encryption = standard
password = …
password2 = …
directory_name_encryption = true

[Snel]
type = sftp
host = [IP Address]
user = lota
port = 5000
key_use_agent = true
md5sum_command = md5sum
sha1sum_command = sha1sum
shell_type = unix

[mini]
type = sftp
host = mini.local
user = hfa
port = 22
key_use_agent = true
md5sum_command = md5sum
sha1sum_command = sha1sum
shell_type = unix

A log from the command with the -vv flag

Although, Contrôle mini shows up in the log, it is simply not copied to the server.

Log available at this bin.

2

This is strange and I can not reproduce it:

$ rclone version
rclone v1.65.1
- os/version: darwin 14.2.1 (64 bit)
- os/kernel: 23.2.0 (x86_64)
- os/type: darwin
- os/arch: amd64
- go/version: go1.21.5
- go/linking: dynamic
- go/tags: cmount

$ tree
.
├── Contrôle mini
│   └── file.txt
└── test
    └── file2.txt

$ rclone sync . crypt:test

$ rclone ls crypt:test
        0 test/file2.txt
        0 Contrôle mini/file.txt
3

I forgot to mention rclone is executed on macOS Monterey…

4

Yes I can see but it should not make any difference. Could you try simple test like mine? With limited content?

5

I just did the same test as yours and it works fine. Dunno what's the probem with my other folder yet.

6

I just created another folder named Trôle under ~/Thinker/ and the issue persists.

It appears that folders bearing ô characters are just ignored, on my end, obviously.
No issue with filename bearing ô character.

7

How you check if it exist on remote? rclone ls?

All works for me...

$ tree
.
├── Contrôle mini
│   ├── Trôle
│   │   └── file3.txt
│   └── file.txt
└── test
    └── file2.txt

$ rclone sync . crypt:test

$ rclone ls crypt:test
        0 test/file2.txt
        0 Contrôle mini/file.txt
        0 Contrôle mini/Trôle/file3.txt
8

Ah!

No… I was browsing the content using macOS Finder…

rclonem='rclone mount --daemon Safe: /usr/local/mnt/rclone > /dev/null 2>&1'

Indeed, when I input rclone lsd Safe:MBP/Test I can see the folder. Apparently, it is well synced. It's just that it is not visible via the rclone mount command.

9

OK. Perfect. This is can of warm - rclone mount on macOS

I have tried rclone mount right now and it is exactly an issue. NFC/NFD saga.

Maybe rclone nfsmount will work better but it is still buggy:

10

Other workaround I used was to convert all names to specific normalization before transferring data to cloud.

$ brew install convmv

# Convert all files in a directory from NFD to NFC:
$ convmv -r -f utf8 -t utf8 --nfc --notest .

# Convert all files in a directory from NFC to NFD:
$ convmv -r -f utf8 -t utf8 --nfd --notest .

What worked for me was to convert all to NFC and use fuse-t with:

rclone mount crypt: ~/Temp/mount -o modules=iconv,from_code=UTF-8,to_code=UTF-8

Here my post re fuse-t - macOS rclone mount - new FUSE-T released - old issues fixed.

Then I can see everything in mount:

Screenshot 2024-01-12 at 10.30.29
Screenshot 2024-01-12 at 10.30.29486×528 36.3 KB

But my advice is not to use rclone mount on macOS... or do not use any characters not from basic ASCII set:) Hopefully it will change in the future - but nowadays it is not reliable at all with characters handling.

Please note that it is not just rclone problem. It is mess created by Apple which has nasty consequences:

1 Like
11

@ncw - have you had any chance to follow up on:

As you can see in this thread it is real problem for people using mount on macOS. Especially when they are not from UK/US:)

I have briefly tested rclone nfsmount and NFC/NFD problem is there the same as with rclone mount

12

Thanks for your time spent in investigating again this issue. It was surely informative for me. I should be more cautious when using accented characters next time.

13

There is no really 100% working solution today.... for mount on macOS

If you use my workaround and see everything in mount it does not mean that you can open all files using Finder... but you can using terminal... But different files..

TOTAL mess.

14

In fact, no need cause I'm slowly migrating my entire environment to Linux… Leaving macOS for good!

15

hahaha. Yes on Linux there is no such issue at all.

But there are still other macOS users:)

16

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