[linux-cifs-client] [PATCH 0/7] [CIFS] RFC: implement ability
to specify remote_nls for legacy servers
Marko Käning
mk362 at mch.osram.de
Mon Jul 28 14:08:04 GMT 2008
Hi Jeff,
> Since this patchset will use unicode as an intermediate translation
> format, you'll probably have the same problem even afterward.
I see.
> What NLS table is your kernel using and how often do you see these
> messages?
Well, I don't know how to tell you which NLS table my kernel is using.
Please tell me, how I can give you this info.
(Calling "find /proc -name *nls*" doesn't give me any hint.)
After letting storeBackup do my server backup onto another linux server
---
client machine:
Linux client 2.6.22.18-0.2-default #1 SMP 2008-06-09 13:53:20 +0200 i686 i686 i386 GNU/Linux
with Samba 3.0.26a
---
remote server:
Linux server 2.6.16.53-0.8-smp #1 SMP Fri Aug 31 13:07:27 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux
with Samba 3.0.22
---
I see for approximately 38000 files in 9000 folders 4435 times these
errors happen:
---
flmpc35:~ # egrep "^Jul 25.*strtoUCS" /var/log/messages | wc
4435 57655 361609
---
And it is always -4 or -28 which returns the error -22.
!!! MORE THAN FOUR THOUSAND ERRORS!!!
I wasn't aware myself up to now that the number of messages is actually
that big. Good that you asked me!
It is strange, but these messages only appear when I shove my backup onto
the server. When I pull the backup files back there are no such messages.
storeBackup is also able to successfully recover its backups from the said
server... Weird!
???????????????
Well, concerning the error messages it would probably very helpful to know
which paths caused the trouble! Perhaps I should run my client with some
debug level switch?
???????????????
More information about the linux-cifs-client
mailing list