[SOLVED] Invalid or incomplete multibyte or wide character ??
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Invalid or incomplete multibyte or wide character ??
Hi,
I'm trying to backup an ext3-formatted disk to an external USB disk, also formatted in ext3.
rsync repeatedly reports those kind of errors : rsync: recv_generator: failed to stat "<filename>" : Invalid or incomplete multibyte or wide character.
Following Google, this is usually related to NTFS-formatted drives but it is not the case here.
A lead to the solution could be that the folders and files being backuped are mapped through smbd. My smbd.conf file contains the following lines regarding charsets :
#Dos charset = 850
#Unix charset = ISO8859-1
Since those lines are commented out, I believe this defaults to UTF-8.
Rsync is for network use (the 'r' bit), and imposes a cpu loading. I gather you are working locally. There are backup programs, and good old tar, cp -a & friends to make this easy. Why 'split the atom' with rsync when you can do it a better way?
Rsync is for network use (the 'r' bit), and imposes a cpu loading. I gather you are working locally. There are backup programs, and good old tar, cp -a & friends to make this easy. Why 'split the atom' with rsync when you can do it a better way?
From the CPU point of vue, this could probably make sense. Appart from that, the backup "script" wasn't written by myself and I believe that it originally was meant for backing up to a networked drive. But in any case, I believe that rsync is still a good option because of its versatility (local use is documented in the man page) and it's performance with big folders.
cp would imply playing with find and timestamps files, and tar would create archives which doesn't help when you need to get a file back rapidly.
That said, anyone feeling like to discuss this "multibyte character" problem ?
Does the problem appear for all the files you're trying to transfer or only for some of them (strange characters in their name)? Eventually you can try to convert one of these file names from one encoding to another and see if it is correctly parsed by rsync after the treatment. To do that the convmv command may come in handy, e.g.
Does the problem appear for all the files you're trying to transfer or only for some of them (strange characters in their name)?
Only some files with (french) accentuated letters. BUT, as a matter of a fact, I tried to replicate today in order to test the command you suggested and... it seems the problem disappeared...
I don't understand, sorry...
Thanks to everyone who tried to help me on this one...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.