Custom Query (8096 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (289 - 291 of 8096)

Ticket Resolution Summary Owner Reporter
#4167 worksforme 552 Quota error handling William
Description

PC: Windows XP Pro SP3 with 2GiB RAM and 3GHz Intel P4 Client: FileZilla 3.2.0 Server: ProFTPD 1.3.1

Hi guys,

some of the servers I connect to allow me to resume partially uploaded files. When there is also a file system quota set (and maxed out) for the connecting user I've noticed an issue with FileZilla where it will loop several hundred times (inconsistent number) in an attempt to force an upload of the file.

When there are hundreds of files in the queue and each file causes four to five hundred failed upload attempts it will be hammering the server to no end for hours. It would seem more logical to cancel all uploads for a user@server/dir with an error message when there is no more quota left (i.e. the server returns a 552 error). Full is full.

I will attach full debug logs but here is a summery: 2009-01-15 17:35:14 1484 1 Status: Starting upload of C:\ISO\Debian\debian-testing-i386-businesscard.iso 2009-01-15 17:35:14 1484 1 Command: STOR debian-testing-i386-businesscard.iso 2009-01-15 17:35:14 1484 1 Response: 552 Transfer aborted. Disk quota exceeded 2009-01-15 17:35:14 1484 1 Command: APPE debian-testing-i386-businesscard.iso 2009-01-15 17:35:15 1484 1 Response: 552 Transfer aborted. Disk quota exceeded 2009-01-15 17:35:15 1484 1 Command: APPE debian-testing-i386-businesscard.iso 2009-01-15 17:35:15 1484 1 Response: 552 Transfer aborted. Disk quota exceeded etc. etc...

When the server disables upload resuming the client will try a normal upload then only a few APPE (resulting in error 451) and then disconnect.

With ProFTPD's HiddenStores enabled (and APPE automatically disabled) the server will upload an incoming file with a temporary file name. If the transfer is interrupted with the 552 error the client will try the same upload again. Because the temporary name already exists the server returns a 550 error and FileZilla stops trying immediately.

It would also be nice to be able to set a retry limit for any kind of action and not just the connection retry limit.

Cheers, and thanks for an otherwise great FTP client!

#9527 rejected 552 disk full arror cecp110
Description

I am getting a 552 disk full error. Is this server wide or is there something I need to do? Who can resolve this? Filezilla or someone on my end? I need to know who I should be contacting to resolve this. thanks

#5367 fixed 7-hour error on timestamp for all sent files John O'Leary
Description

Two parties have verified that text files sent via FileZilla 3.3.2.1 show a new "last modified date" that is seven hours ago. Yet, others looking at the same files on the remote server using SQL Tools 1.5 see the correct timestamp.

I am using Windows XP Pro SP3, and the files are being transferred to any of several servers. In the Site Manager, we have the timezone offsets set to zero (in fact, the seven-hour error is in the wrong direction for this to be the difference between PDT and GMT.)

Here's the kicker: if you drag the affected file back from the remote server, it keeps the same wrong timestamp!

Love the product, just trying to help make it better...

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.