Bug 5156 - JPEG copy error from XP x64 client
Summary: JPEG copy error from XP x64 client
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.10
Hardware: Other Mac OS X
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2007-12-21 05:58 UTC by David
Modified: 2008-01-16 05:07 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description David 2007-12-21 05:58:56 UTC
When trying to copy a directory of image files from a Samba share (running on OS X 10.4.11) using a Windows Xp Professional x64 client and the windows explorer GUI the folder is copied, but the contents are not.

I have noticed that if I remove the jpegs from the directory then the contents are copied down as expected. So for example If I have 2 jpeg files and 2 targa files in a directory then try to copy the directory then only the directory is copied, if I remove the two jpegs then the targa files are copied down too.

I have repeated this process with several different images formats and it only seems to occur when jpegs exist in the directory.

I have tested with many different jpegs so I know that the jpegs are not corrupt.

One strange thing is that if I copy the files using DOS and XCOPY then it copies  the directory contents as well and then I can use explorer to copy the files as expected.

Also if I enter the directory with the jpegs then explorer sometimes creates thumbnails of the jpegs and creates it's thumbs.db file and then I can copy folder and it's contents as well. Other times the thumbnails do not get created and explorer crashes.

Another thing I have noticed is that if explorer successfully creates the thumbnails then I cannot delete the jpegs files using either Finder or Explorer, I get an error reporting that the file is in use. The only way to remove it is to switch to root and delete it using the command line on OS X.

I hope this bug report is helpful.

Comment 1 Volker Lendecke 2008-01-16 04:55:10 UTC
Please try with 3.0.28, 3.0.10 is very old.

Comment 2 David 2008-01-16 05:04:10 UTC
(In reply to comment #1)
> Please try with 3.0.28, 3.0.10 is very old.
> Volker

I don't really have the power to do that as it is automatically updated via the Apple Software Update.
Comment 3 Volker Lendecke 2008-01-16 05:07:41 UTC
Well, then please contact your Apple support.