Bug 10473 - Conversion error: Illegal multibyte sequence(%96vning_02)"
Summary: Conversion error: Illegal multibyte sequence(%96vning_02)"
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.1.4
Hardware: All Windows 7
: P5 normal (vote)
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-27 07:24 UTC by John Hixson (mail undeliverable)
Modified: 2014-03-01 00:24 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Hixson (mail undeliverable) 2014-02-27 07:24:57 UTC 
"After upgrading to Freenas 9.1.1 and 9.1.1.1 the following error message shows up on the consosle :
"Conversion error: Illegal multibyte sequence(%96vning_02)" and many others.

It looks like there is some problem with Swedish character, "%96vning_02" for example should be "övning_02".

FreeNAS-9.2.1.1-RELEASE-x64 (0da7233) SMB3
Windows 7 64 bit

See attached screen dumps, error on console, ls in shell and missing names on files in Windows Explorer."

Please see 

https://bugs.freenas.org/issues/4281

After looking around google for a bit, I came across:

https://lists.samba.org/archive/samba/2013-September/175571.html

I looked at the code that was referenced and it is indeed "fixed", however, this problem continues.
Comment 1 Jeremy Allison 2014-02-27 22:54:08 UTC 
What is the filename character encoding as stored on the disk ?

It should be in utf8.

Jeremy.
Comment 2 John Hixson (mail undeliverable) 2014-03-01 00:24:03 UTC 
(In reply to comment #1)
> What is the filename character encoding as stored on the disk ?
> 
> It should be in utf8.

So it appears this was a configuration issue. I'm sorry for the noise ;-)

The person in question with the problem changed their character set to 
CP850 and things behaved correctly.

> 
> Jeremy.