Closed cela96 closed 2 years ago
The os error 2 translates to ENOENT: Error: No such entry / entity, so fclones can't find the given file. If you can "ls" the file normally then this is probably caused by fclones running .to_string_lossy()
to deal with invalid Unicode filenames. This call converts the 8-bit à
to �
. Working with raw 8-bit sequences everywhere would be possible but is rather tedious.
Here the filename is probably encoded with ISO 8859-1 or -15, try converting it and others to proper Unicode, then it should work.
After fclones scanned and correctly identified the duplicate files I tried to run the command
fclones link <dupes.txt
on a folder mounted with samba on ubuntu 20.04-wsl and I got this error on files with very long names.I received same error with
fclones move duplicatefolder/ <dupes.txt
The base filesystem is ZFS on TrueNAS-12.0-U8
Could the problem be that the path is too long? Could it be related to the character
à
that is not recognized correctly? Could it be an ubuntu and samba problem?Grazie Francesco
P.S. I ran this command in a cloned test dataset to avoid data loss of any kind so I'm not worried about any lost data.