Error overwriting existing files on SAMBA share

[Neil Waldhauer]

I have SAMBA server 3.3.16-eCS 1.1.4-804 running. When I use the new client 2.2.0 beta4, I can copy files only as long as the target does not already exist. Here is an example where the r drive is a share on the server as seen by a client computer running 2.2.0 beta 4:

[r:\temp]dir *.txt

Volume in drive R is EVFS Directory of R:\temp\*.txt

2-07-14 16:52 5,624 124 foo.txt 2-07-14 16:52 5,624 0 pci_dump.txt

11,248 bytes in 2 files and 0 dirs 65,534 bytes allocated

1,616,200,556,544 bytes (1,505GB) free

[r:\temp]copy foo.txt foo2.txt R:\temp\foo.txt => R:\temp\foo2.txt

1 file copied

[r:\temp]copy foo.txt foo2.txt R:\temp\foo.txt => R:\temp\foo2.txt The segment is in use by another process. "R:\temp\foo2.txt"

0 files copied

[r:\temp]

I see the same problem with SAMBA client 2.1.5 GA.

[Silvan Scherrer]

did you try this operation with 4OS2? If yes could you also try normal cmd?

[Neil Waldhauer]

Yes, the operation was in 4OS2. I tried again in cmd, and it works normally. Any idea what is happening?

[Silvan Scherrer]

I tend to say it's a 4OS2 bug. Somehow like the file is not closed.

I don't think we can do anything here and I close this bug. If you are able to prove it's not a 4OS2 bug, please feel free to reopen this one.