samba - Sep 2000 - bug in smbmount and smbclient with 8bit filenames

On Fri, Sep 01, 2000 at 11:57:28PM +0200, Urban Widmark
wrote:
> On Thu, 24 Aug 2000, Jason Haar wrote:
> 
> [Hmm, has no one answered this yet?]
Nope :-(
> > It appears that files on our NT servers that have 8bit chars in the
> > filenames are causing "No such file or directory" errors
when listed via
> > either smbmount'ed partitions or smbclient.
> 
> For smbfs (smbmount) could you send kernel logs from this? (dmesg output)
> Either to me and/or to the right mailinglist.
OK, there are none. This mount works fine - no smb_request/etc messages.
It's just that it spits the dummy when faced with 8bit filenames.

Please note that this affects smbclient 2.0 AND TNG too - it's not just a
Linux smbmount problem...

BTW, these "8bit filenames" aren't some strange character set,
they are just
filenames with 8bit characters in them (i.e. luser error during "Save
As" :-)
> 
> I think the problem is that when you list these files ls is doing both
> readdir() and stat(). For some reason the name it gets from readdir
isn't
> understood in the stat call.
> 
> Does '/bin/ls --color=never /some_path' work better?
> 
BING! :-) Spot on. That command shows the filenames and no error. "ls
-l" or
find, or rsync all show it as an error as follows:

[jhaar@crom]$ /bin/ls --color=never 
?LOGO 11.98  ?LOGO SHEET  Handheldw?screens.eps
InterOpLogo30%.eps          


compare with:

[jhaar@crom]$ /bin/ls -la
ls: Handheldw?screens.eps: No such file or directory
ls: LOGO 11.98: No such file or directory
ls: LOGO SHEET: No such file or directory
total 70                                                           
drwxrwxr-x    1 jhaar    jhaar         512 Aug 17 01:38 .
drwxrwxr-x    1 jhaar    jhaar         512 Sep  4 12:22 ..
-rwxrwxr-x    1 jhaar    jhaar       70922 Jan 18  1999 InterOpLogo30%.eps  




-- 
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417

On Mon, 4 Sep 2000, Jason Haar wrote:
> OK, there are none. This mount works fine - no smb_request/etc messages.
> It's just that it spits the dummy when faced with 8bit filenames.
> 
> Please note that this affects smbclient 2.0 AND TNG too - it's not just
a
> Linux smbmount problem...
smbclient is someone elses headache.

Please note the difference between smbfs and smbmount. This problem is in
smbfs, not in smbmount.
http://www.hojdpunkten.ac.se/054/samba/smbmount/
> BTW, these "8bit filenames" aren't some strange character
set, they are just
> filenames with 8bit characters in them (i.e. luser error during "Save
As" :-)
What exactly do you mean by 8bit characters? unsigned char is a 8bit value
... are you talking about 0x00-0x1f or 0x80-0xff? A "strange"
character
set would be using parts of 0x80-0xff (unless unicode, which it is on
NTFS but not on FAT).

Could you find the binary value of these characters? Or tell me how to
create a file with a non-working name.

> [jhaar@crom]$ /bin/ls -la
> ls: Handheldw?screens.eps: No such file or directory
               ^
That character has a real value. which? smbfs fails here when it tries to
find more info about the file, using the filename.


(This problem wouldn't appear if smbfs was a little more clever and used
 the fileinfo it reads at once, most likely a great speedup for ls. Or if 
 it was even more clever and spoke unicode with the NT.)

/Urban