Hi,

at least this happens to be a server-problem, so WinSCP as innocent. There was some rsync running in the background grabbing the incomplete file and overwriting the complete one a few moments later with the incomplete version. For some reason the pscp-file and some other testtransfers (without using WinSCP) survived here and I was barking up the wrong tree. ;-)

Sorry for the confusion.

Nik

So the first listing in file panel after the transfer finishes contains correct file size?

Hello,

This was my first guess, too. But this thing happens after the transfer has finished.

On the target system:
This is what it looks like when the transfer has finished.

This is what it looks like a few moments later.

The only thing that happens in these "few moments" is that the costumer refreshes his WinSCP-Window quite often to see what is happening with the file on the Linux machine.
Suddenly the filesize changes and this one-hour-ahead-phenomenon occurs. All other files in the directory remain untouched.

He was using WinSCP 3.6.8 Build 245 and then updated to 3.7.6.
The result is the same. Something happens with the file after being copied to the server, but only if WinSCP is being used for the transfer.

This is really strange. ;-)

Nik

They are probably using text transfer mode.

Hello,

our customers is trying to copy a 14MB file from Windows to Linux using WinSCP. When the transfer is finished the filesize shows correct time and date (when the file has been saved first on the windows machine) and the correct size. Some moments later, the filesize has been reduced to 9-11MB and the time/date has changed. When he uses pscp for the transfer the filesize and date stays the same and nothing changes. (That is why we don't think that this is a server problem, because the pscp-files remain untouched.)

The customer says he's using the "refresh button" to see what is happening.

He also faces this one-hour-ahead-problem but this is a minor problem in this case. ;-)

Any idea?

Thank you in advance...

Nik