Hello,
FYI, i noticed that using
write cache size = 131072
on a share, leads to corrupted files from some applications. Only one client is
accessing the file.
In particular with coreldraw this can be reproduced.
Setup:
Server: samba 3.0.4-SUSE
Client: Windows XP Pro
[raid1]
comment = 1
On Mon, Jul 12, 2004 at 10:17:57PM +0200, Holger Krull wrote:
Hello,
FYI, i noticed that using
write cache size = 131072
on a share, leads to corrupted files from some applications. Only one
client is accessing the file.
In particular with coreldraw this can be reproduced.
Can you tell me
Can you tell me exactly how you reproduce this ?
Open a file on the write cached share, in this case a coreldraw file (size 24K). Save it with a different name, it only happens if a new file gets created. Sometimes the first save succeds without error. After the first one fails, no later write
On Tue, Jul 13, 2004 at 12:33:44AM +0200, Holger Krull wrote:
Can you tell me exactly how you reproduce this ?
Open a file on the write cached share, in this case a coreldraw file (size
24K). Save it with a different name, it only happens if a new file gets
created. Sometimes the first
Can you reproduce this with a different application than
coreldraw ? One that ships with Windows maybe ?
So far i know none, but i will test.
When you save the new file what happens ? Does the app
abort with an error report ?
No, the app is perfectly happy.
How do you know the file
is corrupt ?
On Thu, Oct 03, 2002 at 12:52:10PM +0200, Rasmus Borup Hansen wrote:
I recently found out that write caching in samba sometimes leads to
file corruption (the setup program for Sophos Antivirus generates
corrupted files when making a central installation on a Samba
share).
This
I recently found out that write caching in samba sometimes leads to
file corruption (the setup program for Sophos Antivirus generates
corrupted files when making a central installation on a Samba
share).
This morning I tracked down the place in the Samba code that leads to
corruption. Here is
On Thu, Oct 03, 2002 at 12:52:10PM +0200, Rasmus Borup Hansen wrote:
I recently found out that write caching in samba sometimes leads to
file corruption (the setup program for Sophos Antivirus generates
corrupted files when making a central installation on a Samba
share).
This morning I
