Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#10668 closed Bug report (fixed)

"GET" starts even when transfer will fail for sure

Reported by: MacLAK Owned by:
Priority: normal Component: FileZilla Client
Keywords: GET fail, missing destination Cc:
Component version: 3.14.0 (x64) Operating system type: Windows
Operating system version: Windows 10 build 10240 (x64)

Description

When destination drive is invalid (missing network drive, maybe also when disk is full), a GET operation still start, and even hammer the FTP server (3 failed attempts in a row).

With a full transfer queue, it provokes a high number of failed transfers (0 bytes), and some servers then report an abnormal number of logs per second.

Obviously, FileZilla do NOT check destination's suitability before starting the transfer. It should check if there is enough space on disk and drive's availability.

HOW TO REPRODUCE:

  • Connect to a FTP server with a lot of files.
  • Connect a network drive.
  • Go to this drive in FileZilla.
  • Enqueue a lot of files.
  • Disconnect network drive: FILEZILLA DO NOT SEE THIS OPERATION.
  • Launch queue: everything fail, server is hammered.
  • Same thing may apply with a full disk (don't have stuff to test it however).

Attached files: In attached log, I've disconnected my "T:\" network drive, which is therefore missing in navigation panel BUT still shown in "Local site" bar. See attached picture.

Attachments (2)

FileZilla-Failed_transfer_with_repetitions.log (2.1 KB) - added by MacLAK 4 years ago.
Transfer log, with all the failed attempts (only one file asked)
FileZilla-Local_files_screenshot.png (17.7 KB) - added by MacLAK 4 years ago.
Local site screenshot, with "T:\" drive still active despite that it's not accessible anymore.

Download all attachments as: .zip

Change History (4)

Changed 4 years ago by MacLAK

Transfer log, with all the failed attempts (only one file asked)

Changed 4 years ago by MacLAK

Local site screenshot, with "T:\" drive still active despite that it's not accessible anymore.

comment:1 Changed 4 years ago by Tim Kosse

Resolution: fixed
Status: newclosed

In the next version, FileZilla will no longer retry if opening a local file fails.

comment:2 in reply to:  1 Changed 4 years ago by MacLAK

Replying to codesquid:

In the next version, FileZilla will no longer retry if opening a local file fails.

Nice to see, but problem is that FileZilla should not even TRY ONCE a transfer if local file's opening failed.

Note: See TracTickets for help on using tickets.