Opened 19 months ago

Closed 19 months ago

Last modified 19 months ago

#11519 closed Bug report (rejected)

Files > 500GB have lock and then won't resume

Reported by: David Owned by:
Priority: high Component: FileZilla Server
Keywords: Cc:
Component version: 0.9.60 beta Operating system type: Windows
Operating system version: Server 2016

Description

When transferring files of large sizes the server appears to lock the file out and then won't allow you to write to it again.

No AV is install on the system and everything is allowed through the firewall. It will resume normally but after a point it stops resuming and gives a "550 Writing to file failed" in the log. Permissions to the file and everything are okay and deleting the file and starting again gets it uploading again but it inevitably fails.

Currently attempting to change block size to see if this helps with the problem. The file in question is almost a terabyte in size.

Attachments (1)

FTPLog.txt (3.0 KB) - added by David 19 months ago.
Copy of relevant portion of server logs

Download all attachments as: .zip

Change History (4)

Changed 19 months ago by David

Attachment: FTPLog.txt added

Copy of relevant portion of server logs

comment:1 Changed 19 months ago by David

This forum thread is an example of another user having the same problem as I am, https://forum.filezilla-project.org/viewtopic.php?t=42655

comment:2 Changed 19 months ago by Tim Kosse

Resolution: rejected
Status: newclosed

Either a sever bug in Windows itself or alternatively there must be a third-party software installed on your machine that is interfering with file operations.

comment:3 Changed 19 months ago by David

There is 2 applications installed on the server, things that might interfere with file operations have been disabled and turned off. This works without a problem with most files but just occurs for larger files.

What sort of evidence do you need me to collect to take me seriously about this? I'm am on the point of setting up a dev environment to try and figure it out myself.

Note: See TracTickets for help on using tickets.