[Bug 8471] The file of DBCS file name contains DBCS second byte of x'5C' cause error.
samba-bugs at samba.org
samba-bugs at samba.org
Tue Sep 20 20:00:30 MDT 2011
https://bugzilla.samba.org/show_bug.cgi?id=8471
sakai.takeshi at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|All |x86
OS/Version|All |Windows 7
--- Comment #1 from sakai.takeshi at gmail.com 2011-09-21 02:00:30 UTC ---
Wayne, I performed further investigation this problem, found following;
1) Windows Copy command for the same file completed successfully, to samba
server. samba info is below;
[root at localhost monte]# smbclient -U samba -L localhost
Enter samba's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.11-71.fc15]
Sharename Type Comment
--------- ---- -------
samba Disk share folder of leo server
monchan Disk monchan's smb home
monte Disk
IPC$ IPC IPC Service (Samba Server Version 3.5.11-71.fc15)
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.11-71.fc15]
Server Comment
--------- -------
LEOSVR Samba Server Version 3.5.11-71.fc15
Workgroup Master
--------- -------
WORKGROUP LEOSVR
[root at localhost monte]#
2) From above condition, the problem source may be samba side, if so shall I
submit new bug file to samba ? And close this file ? Any how the bug detected
on rsync side, so I filed to rsync, is this correct ?
3) Originally I dug this bug with my NAS, sold by buffalo corp., I bought it
about 5 years ago, it seems using some linux, not known the kind of linux,
version of linux and the version of samba, the NAS name is
tera-station(TS-TGLB15), with this NAS, even the file copying by windows
command also causes file not found error, where the file is used same with
rsync operation. Then I began the investigation with latest rsync and samba.
I give up for older version correction, though would like to fix on latest
version.
That's all my thought at this moment.
Takeshi Sakai
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the rsync
mailing list