Bug 214411 - broken sockets when doing large file io with samba mounts
Summary: broken sockets when doing large file io with samba mounts
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-07 15:00 UTC by Stephen Adler
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-11-23 20:08:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
samba log file (6.90 KB, text/plain)
2006-11-07 15:00 UTC, Stephen Adler
no flags Details

Description Stephen Adler 2006-11-07 15:00:39 UTC
Description of problem:
When opening a samba mounted directory under windows running under vmware, the
windows directory window searchs all the images in that directory and generates
a little icon of the image in the file. The icon update process is very slow.
Looking at the samba log file, I see a lot of socket errors being reported.


Version-Release number of selected component (if applicable):


How reproducible:
Every time


Steps to Reproduce:
1.Fire up the windows system
2.open the samba mounted directory which contains large jpg files
3.watch it take for ever to populate the icons
  
Actual results:
Very slow icon population, lots of socket errors in samba log file.

Expected results:
Fast icon populat, no socket errors in samaba log file.

Additional info:

Comment 1 Stephen Adler 2006-11-07 15:00:39 UTC
Created attachment 140564 [details]
samba log file

Comment 2 Simo Sorce 2007-03-28 17:25:24 UTC
What Windows version?
What Samba version?
Is the samba server on the same host as the windows vmware image?
If not how are the hosts interconnected? Is the eth card of the windows vmware
image bridged? NATed? Routed?
Are they both emulated or not?



Note You need to log in before you can comment on or make changes to this bug.