-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback on the use of special caracters in files' name (HFS+ <-> ext4) #6
Comments
Hi Airwan, Can you test transfering your files with rsync -a ? The first rsync run should transfer the files. The second run should do nothing. You should test both directions, ie transfer hfs -> ext4 then ext4 -> hfs Thanks in advance, |
Salut et pardon pour retard, alors voici le bilan. Avec rsync -a aucun souci! Ensuite voici un petit 1. Sur le serveur je créer mon un dossier ñaídossier puis je lance le serveur$ backup [ LEFT DIR CONTENT ] RIGHT DIR CONTENT
ñaídossier/ (mkdir) Todo in /Users/Amelie/Documents: mkdir:1 Applying actions... *2. Puis une 2nd fois!! * MacBook-Pro-de-Amelie:Documents amelie$ backup [ LEFT DIR CONTENT ] RIGHT DIR CONTENT
ñaídossier/ (mkdir) Todo in /Users/Amelie/Documents: mkdir:1 rmdir:1 Applying actions... Voici l'erreur!! J'avoue ne pas comprendre... Je vais essayer d'isoler un peu plus l'erreur. Cordialement, On Mon, Apr 21, 2014 at 12:27 PM, Marc MAURICE [email protected]:
|
Hi Airwan, Can you test it ? see #9 |
I just may have discovered this. In my case did you notice one of these music files has a double-slash in the path like //?
|
Feedback on the use of bsync between a mac with HFS+ filesystem and a NAS with ext4 partition.
When using special caracters as ñ, ó or í, but not á (forinstance), the synchrnization becomes very unstable through ssh. Move change, rmdir and so on, give errors.
On the contrary, between my laptop with Debian and ext4 partition there is no problem.
Thus, I guess there's a problem with caracter encoding between both type of partition (HFS and ext4) and bsync does not manage it.
The text was updated successfully, but these errors were encountered: