Opened 10 years ago

Closed 10 years ago

Last modified 5 years ago

#4796 closed Bug report (rejected)

SFTP file size reported incorrectly on files larger than ~3GB

Reported by: dougbb Owned by:
Priority: normal Component: FileZilla Client
Keywords: file size Cc:
Component version: Operating system type: Windows
Operating system version: All

Description

VanDyke VShell SFTP server on Windows
Filezilla 3.2.7.1 - Windows or Mac OS X client

.DMG file size is reported as 1,307,542,414 when it is really 5,602,509,710

SSH Secure File Transfer version 3.2.9 reports size correctly

Attachments (3)

filezilla-redacted.log (4.0 KB) - added by dougbb 10 years ago.
Filezilla Log
ssh-example.JPG (99.8 KB) - added by dougbb 10 years ago.
File Size in SSH Secure File Transfer
winSCP.JPG (102.9 KB) - added by dougbb 10 years ago.
WinSCP reports it correctly as well

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by dougbb

Attachment: filezilla-redacted.log added

Filezilla Log

comment:1 Changed 10 years ago by Tim Kosse

Resolution: rejected
Status: newclosed

2009-09-03 17:47:30 5464 0 Listing: 1307542414 Sep 01, 2009 11:15 Mac OS X 10.6 Install DVD.dmg

Broken server. These listing lines are displayed and interpreted exactly as returned by the server.

You have to either upgrade to a proper server that supports filesizes exceeding the 32bit limit or refrain from using such large files.

Changed 10 years ago by dougbb

Attachment: ssh-example.JPG added

File Size in SSH Secure File Transfer

comment:2 Changed 10 years ago by dougbb

Resolution: rejected
Status: closedreopened

How is this true if another SFTP client reports this correctly?

Changed 10 years ago by dougbb

Attachment: winSCP.JPG added

WinSCP reports it correctly as well

comment:3 Changed 10 years ago by Tim Kosse

Resolution: rejected
Status: reopenedclosed

As always there are multiple ways to do things, that is why it appears to work with some clients. But this doesn't change the fact that the server is broken and needs to be updated.

Note: See TracTickets for help on using tickets.