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
path = /raid1
read only = No
create mask = 0777
directory mask = 0775
write cache size = 131072
map system = Yes
map hidden = Yes
delete readonly = Yes
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 exactly how you reproduce this ? I need to have a simple way to see this in order to track it down. In the meantime I suggest you remove the write cache line - modern UNIXes don't need it, it was mainly added for slow Solaris filesystems. Jeremy.
> 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 succeds. How can i help you further?> you remove the write cache lineDid this of course. Was experimenting.
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 save succeds without error. After the first > one fails, no later write succeds. > How can i help you further?Can you reproduce this with a different application than coreldraw ? One that ships with Windows maybe ? When you save the new file what happens ? Does the app abort with an error report ? How do you know the file is corrupt ? Jeremy.