Server: filescan retrun "entry will not be accessible due to incompatible encoding"

[abolinhas]

Hi,
I'm using nextcloud11, I move a lot of folders/files from my old cloud to nextcloud, now when I execute the command php occ files:scan --all I get this error
Entry "/admin/files/Informa▒▒o Geografica/Areas_PGF/Caima.dbf" will not be accessible due to incompatible encoding
Entry "/admin/files/3_Eixo/Primeira Interven▒▒o/Sectores entidades.dbf" will not be accessible due to incompatible encoding
Entry "/admin/files/3_Eixo/Primeira Interven▒▒o/LEE.shp" will not be accessible due to incompatible encoding
and more...

How can I fix it?
Best regards

[nickvergessen]

@icewind1991 any idea what users can do?

[abolinhas]

Hi,
Any tips about it?

[icewind1991]

Do these files come from an OSX system?

The "most correct" way would be to upload the files trough the web interface, webdav or sync client which will ensure the encoding of the unicode characters is correct.

Alternatively you can convert the NFD encoded filenames (which OSX uses) to NVC encoded ones (what the rest of the world uses) while copying over the files. (see https://serverfault.com/questions/397420/converting-utf-8-nfd-filenames-to-utf-8-nfc-in-either-rsync-or-afpd for example)

[abolinhas]

No, I just copy from one folder to another on the same linux server.
Eg the command that I use
cp -R /oldcloud/home/folder /nextcloud/home/

[icewind1991]

It's possible that previously a client messed with the encoding then.

Can you try doing the encoding conversion while copying (rsync -a --iconv=utf-8-mac,utf-8 ...)

[MorrisJobke]

No reply: I guess this is solved then.

We are happy to reopen if this hasn't solved the issue for you.

[wendall]

I had the same issue with Russian symbols in folder/file names. @icewind1991 is right, the problem was in NFD encoded filenames.
Just installed convmv and run:
convmv -f utf-8 -t utf-8 -r --notest --nfc <nextcloud-data-folder>
After this a simple reindex helped me to see my data in Nextcloud:
php occ files:scan --all

[ghost]

Just a note to say this fixed the issue for me too. Weird thing is that I have no idea how I got the NFD encoded filenames to start with!