smb.conf: ===== [global] mangling method = hash unix charset = CP932 (or EUC-JP) [home] writeable = yes ===== In addition to BUG#190, I found "mangling method = hash" has another problems to treat multibyte strings. I will show some samples: (*) <A> means a Japanese hiragana character (U+3042). 1. a mangled name does not create against a filename more than 8 bytes: Samba 3.0.0beta1: mangling method = hash, unix charset = EUC-JP -------- 2003/06/26 14:22 7 <A><A><A><A><A><A> -------- Problem1: The length of <A><A><A><A><A><A> is 12byte, but no mangled name is created. In Samba 2.2.x, a mangled name is created. This is because "mangling method = hash" in Samba 3.0.0 checks the number of characters of the string but should check if the byte length of the string is more than 8 bytes or not. Problem2: If we create a file whose name is <A><A><A><A><A><A><A><A><A> ( more than 9 multibyte chars), then smbd fails in convert_string_allocate() and calls smb_panic().
moving to extended character component
Accept bug and reassign to me.
Might be fixed with jeremy's other changes. Pleas retest (see bug 186)
I'm marking this as fixed in hopes that all of the mutibyte character set work that was done for RC2 does resolve the problem. If not, please reopen the bug
originally reported against 3.0.0beta1. CLeaning out non-production release versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
database cleanup