#68 closed defect (fixed)
sequence 0xA9 0x20 characters in file's/folder's names on samba's shares
| Reported by: | digi | Owned by: | Silvan Scherrer |
|---|---|---|---|
| Priority: | critical | Milestone: | Samba Server for eCS (OS/2) 1.1.0 |
| Component: | Samba Server | Version: | 3.0.31 |
| Keywords: | Cc: |
Description
Users can't open/create files and folders with sequence of two symbols 0xE9 0x20 in names. Also, not impossible to create folders/files with names "*е" (е = 0xE5)
(codes of characters in windows-1251 charset)
for ex.: N:\my-samba-share>ver > "123й 567.txt"
will create file with name "123" - ?!
N:\my-samba-share>ver > "123й567.txt"
will create file with name "123й567.txt" - Ok
Attachments (4)
Change History (13)
comment:1 by , 17 years ago
| Milestone: | Samba Server for eCS (OS/2) 1.1 → Samba Server for eCS (OS/2) 1.0.2 |
|---|
by , 17 years ago
| Attachment: | smb-log_level10.zip added |
|---|
comment:2 by , 17 years ago
digi - please recreate the logs with debug level 10 and http://smedley.info/smbd-ticket68.zip this has some additional debug information to try and work out where the problem stems from.
by , 17 years ago
| Attachment: | smb-log2_level10.zip added |
|---|
by , 17 years ago
| Attachment: | smb-log3_level10_smbd-ticket68_winclient.zip added |
|---|
comment:3 by , 17 years ago
http://smedley.info/smbd.zip is updated again to try and confirm where the problem comes from
comment:4 by , 17 years ago
Samba's & libc logs with build from last smbd.zip archive: ftp://digi.os2.snc.ru/in/smb-log4_level10-libc_log.zip
comment:5 by , 16 years ago
| Version: | → 3.0.31 |
|---|
comment:6 by , 16 years ago
comment:8 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fix for 3.0 http://svn.netlabs.org/samba/changeset/337
Fix for 3.3 http://svn.netlabs.org/samba/changeset/339
Fix for 3.2 http://svn.netlabs.org/samba/changeset/341
Note: Samba should be set to either use IBM-850 or UTF-8 as unix and display charset manually, even if the system is running on a different codepage. Codepage IBM-437 is still defective.
Also see http://svn.netlabs.org/samba/changeset/307
and http://svn.netlabs.org/samba/changeset/308
which are problematic in this respect on the server but absolutely necessary for the client.
comment:9 by , 16 years ago
The following script tests whether codepage translation works on a given share (copy it it on to the share and run it from there):
/* Character translation test */
'@del TEST_*_*'
chunks = 128 /* a single char if chunks = 128 */
success = 0
mismatch= 0
writeerr= 0
verbose = 0
do bl = 0 to chunks-1
call charout, '.'
bs = 128/chunks
if bs <> 1 then filename = "TEST_"||bl||"_"
do I = 128+bs*bl to 128+bs*(bl+1)-1
if bs = 1 then filename = "TEST_"||I||"_"
filename = filename||d2c(I)
end
if Verbose then call charout , filename' '
wok = lineout(filename, 'TESTFILE')
cok = stream(filename,'c','close')
if wok = 0 then do /* successfully written */
if Verbose then say ''
ok = SysFileTree(left(filename,lastpos("_",filename))||"*", file., "FO")
if Verbose then call charout , filespec("N",file.1)
if filespec("N",file.1) = filename then do
if Verbose then say " No error!"
success = success + 1
ok = SysFileDelete(file.1)
end
else do
if \Verbose then call charout , filename' '
say " Char mismatch!"
mismatch = mismatch + 1
end
end
else do
if \Verbose then call charout , filename' '
say 'Write failure, "'wok'"'
writeerr = writeerr + 1
end
end
say 'Successful chars 'success
say 'Mismatched chars 'mismatch
say 'Unwriteable chars 'writeerr

samba's log: writing files named "1-123й 456" and "2-123е" from windows client