Skip to content
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

not compatibility with charset, need kernel module #44

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments
Open

not compatibility with charset, need kernel module #44

GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

-What steps will reproduce the problem?
-1.
(on the virutal nas appliance)
mount windows share with "other" charset using samba
-2.
copy files width chars like æ ø å to sdfs partition

-What is the expected output? 
expected it to steady copy over files

-What do you see instead?
unstable copy where some files makes it to sdfs partition, until
copy hangs,


-Please provide any additional information below.
problem could be there is no support for my charset,

i would like to try to circumvent this problem by mounting the windows share 
with another charset using the "iocharset" parameter

this will give me a error
"Can not access a needed shared library"

i found this
http://lists.samba.org/archive/linux-cifs-client/2009-April/004343.html

i tried using ftp, but same results
extremely slow and unstable copy, and not being able to unmount volume


conclusion(for me), ether i must convert my windows file to utf8
or get the nls_utf8.ko kernel module

issue(for you), please make this utf8 compatible or make charset option or 
include this module so people wont have to





Original issue reported on code.google.com by [email protected] on 8 Nov 2011 at 1:55

@GoogleCodeExporter
Copy link
Author

might be the nls_cp437.ko kernel, i cant say for sure
this surpasses my ability in linux 

Original comment by [email protected] on 8 Nov 2011 at 2:17

@GoogleCodeExporter
Copy link
Author

Hello,

I tested the lastest "virutal nas appliance" and I found the same bug.
I installed the nls_utf8.ko  at the boot, no change.

Original comment by [email protected] on 4 Sep 2012 at 3:52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant