Bug 1200 - Exporting from Windows in dBASE format
Summary: Exporting from Windows in dBASE format
Status: CLOSED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.2
Hardware: All All
: P2 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-20 19:20 UTC by mkjellman
Modified: 2005-08-24 10:18 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mkjellman 2004-03-20 19:20:01 UTC 
If you are exporting from any windows program into dBASE format it results in a delayed write error if 
the exported file is greater than 15 MB. If the file is bigger, Windows will fail to export the file and 
display a "Delayed Write Error". This only happens if the resulting exported file size is supposed to be 
over 15 MB. Exporting to a local drive and then copying it to the same Samba share results in a fine 
copy on the share.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2004-03-22 05:48:18 UTC 
please set 'oplocks = no' in the service containing the 
dbase file (as per the documentation) and report back.
Comment 2 mkjellman 2004-03-22 07:20:35 UTC 
Oplocks does not help the situation. Even if I turn off all file locking it still gives the error message.
Comment 3 Gerald (Jerry) Carter (dead mail address) 2004-03-22 08:33:45 UTC 
Have you tested this against a NT file server ?  Just curious.
Comment 4 mkjellman 2004-03-22 09:15:22 UTC 
Yes, If i export out to a Windows Share it is all set. Also when we used to have Jaguar server which 
included Samba 2.x exporting is fine. This problem has only cropped up since 3.0 which is included in 
Panther. (3.0.2) I have been on the phone with Microsoft trying to find out if it was on there end and 
after 4 hours they concluded that it must be a Samba problem. Apple said that they were just going to 
file a report to you because they could not figure it out. I was hopping that going straight to the source 
would be the best bet. Thanks!
Comment 5 mkjellman 2004-04-10 07:03:35 UTC 
jerry, any new ideas? sorry to nag you but people are starting to get angry with
me because of the workaround. thanks!
Comment 6 Gerald (Jerry) Carter (dead mail address) 2005-02-11 07:19:05 UTC 
please test against 3.0.11.  Reopen if necessary.  Sorry for 
not being more responsive.  Lots of bug reoprts.
Comment 7 Gerald (Jerry) Carter (dead mail address) 2005-08-24 10:18:54 UTC 
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.