Very Computer

by **Sony Anto** » Mon, 10 Feb 2003 17:56:44

I transferred a huge file in bin mode, using vsftpd in RH 8.0 Linux (
vsftpd-1.1.0-1 ). The file I transferred ( from windows XP ) was
actually 5304155010 bytes long in both windows and linux.
But vsftpd reported 1009187714 bytes
--------------------------------
ftp> mput *.mpg
mput Sample.mpg? y
200 PORT command successful. Consider using PASV.
150 Go ahead make my day^W^W^Wsend me the data.
226 File receive OK.
ftp: 1009187714 bytes sent in 571.89Seconds 1764.65Kbytes/sec.
--------------------------------

As far as I know ftp does not define a standard for compression.

The only possibility I can think of was that this is a bug in wsftpd.
Did I go wrong somewhere. ( Is there really a compression as a part of
ftp protocol - so that windows client and linux wsftpd are aware of it
)

--sony

by **Sam Trenhol** » Tue, 11 Feb 2003 06:03:39

>I transferred a huge file in bin mode, using vsftpd in RH 8.0 Linux (
>vsftpd-1.1.0-1 ). The file I transferred ( from windows XP ) was
>actually 5304155010 bytes long in both windows and linux.
>But vsftpd reported 1009187714 bytes

Linux on x86 machines use 32-bit ints; 5304155010 - 2^32 is 1009187714

Chris should probably patch vsftpd to use a long long for reported
file sizes.

- Sam

--
My email address may be obtained at http://www.samiam.org/ssi/mailme.shtml

by **Sony Anton** » Tue, 11 Feb 2003 10:39:16

>>I transferred a huge file in bin mode, using vsftpd in RH 8.0 Linux (
>>vsftpd-1.1.0-1 ). The file I transferred ( from windows XP ) was
>>actually 5304155010 bytes long in both windows and linux.
>>But vsftpd reported 1009187714 bytes

> Linux on x86 machines use 32-bit ints; 5304155010 - 2^32 is 1009187714

For those who didn t understand what Sam is telling here.
4Gb is all a 32 bit unsigned int can represent ( 2^32 = 4 GB )
after this the counter just rolled over starting with 0 again and reaching
1009187714
Thanks Sam yes this should be fixed. But then I wonder if the 32 bit types
are used elsewhere.
Also what needs to be done inorder to overcome the inherent 32 bit offset
used for operations like seek().
In fact I forgot if linux - like is the case with Solaris - needs some
special compile time switches, in order to enable a program to operate on
files larger than 4 GB.
--sony

Quote:
> Chris should probably patch vsftpd to use a long long for reported
> file sizes.

> - Sam

Very Computer

vsftp bug ??

vsftp bug ??

vsftp bug ??

vsftp bug ??