Issue update

Upgraded to latest version of WinSCP and noticed something interesting (while using temp files resume)
After I upload the file it gives me the attached error message

If I click retry it then writes the proper timestamps (!)
I guess you were right, for some reason the server might have gotten the timestamp set command before the temp file been renamed

Ok I have received word from the server providers

They've informed me their OS system File System is proprietary to their company, and as such they have to keep this info for security reasons.

So I guess I'll have to find a workaround to my problem ..

Ok, let us know.

Ok not sure how to find out, using ADrive but they don't specify this anywhere on their site.

I've sent their support a message, hopefully they'll follow up in a week, cheers mate

svartberg wrote:

Doh that actually worked ! :D
Tested with several files, disabling temp file resume thing definitely sorted the issue

So is this a bug ? or will I need to work around it by disabling resume support via temp files some how ?

Looks like a server-side bug to me. Looks like the server does not properly serialize the requests. But that's just a guess. I do not understand, what's going on there. Is there some special file system?

Doh that actually worked ! :D
Tested with several files, disabling temp file resume thing definitely sorted the issue

So is this a bug ? or will I need to work around it by disabling resume support via temp files some how ?

I do not see WinSCP doing anything wrong. It looks like it can be server-side issue.

Anyway, just as a wild guess, can you try to turn off Automatic Resume/Transfer to Temporary Filename?
https://winscp.net/eng/docs/resume#automatic

Sure, here it is, cheers !

Thanks. Can you please also post a log for a file that does not have the problem? Also it would be nice if you at least keep the directory listing record for that file intact.

Thanks for the quick reply !

Here's the attached log

Please attach a full log file showing the problem (using the latest beta version of WinSCP). Ideally for a single "Bad" file.

Hi, I'm using this awesome tool for regular large volume backups.

But it doesn't always synchronize timestamps to local properly (the "changed" column date), and instead uses current time.
Trying to upload manually noticed the "bad files" (that don't sync timestamps) will always have this problem, while the "good files" will always sync timestamps properly.
Did not notice anything common for those files, happens despite of file sizes and such.

I rely heavily on timestamps for my backup system, so I gotta sort this out somehow before resuming the backups.

Winscp Version 5.1.5 (build 3261)
Operating System : windows vista 64bit
Transfer Protocol : SFTP (I think server uses sftp-3)
Method : problem occurs both in manual GUI & scripted synchronization
File types : compressed & encrypted (256bit) 7z files