bittorrent 4.0 handling file larger then 4.0 gbyte?
 

Hi!

I am using bittorrent 4.0 in Slackware-current. Is the slackware-current package compiled to be able to handle files larger then 4.0gbyte?

I was downloading a file which states 3.99gbyte on Azureus. But at 92.4% Azureus keep on crashing. So I kick up btdownloadcurses.py. As bittorrent verify my file, it will crash after 2/3 gbyte(not sure, wasn't observing) and the error given was file is too large.

However, I managed to finish downloading the file with Azureus in Mac Os X.

Wondering, whether there is a switch/option during complation time to handle super large files.

the bittorrent package is a noarch package, so there was no
compile, it is just a big script. Open it up and snoop around,
or go to bittorrent homepage and find out. Or perhaps you
downloaded a corrupted copy, check the md5sum with the
original.

-tank

Thanks for the info.

Now you are throwing more light to it.

So the bittorrent scripts are phyton scripts. That means phyton can't handle file larger then 3-4gbyte?

I thought that my partial downloaded copy was corrupted, but I can continue the download in Mac Os X using Azureus. And the file is in perfect condition (finished).

Sigh, I realize that it is nothing to do with file size. I am getting that error now even though the download file is like 700mbyte and 300+mbyte

The exact error I get is
[21:18:41] IO Error [Errno 27] File too large

And my Azureus have been crashing as well. :( Anything wrong with my Slackware?

Just curious, what is the partition filesystem where you downladed the > 4GB file ?

All my filesystem are ext3.

Does it have to do with disc cache? How can I clear the disc cache without rebooting?

Azureus and bittorrent crash at the any downloads, but seeding only is ok.

I am having the exact same issue
 

"IO Error [Errno 27] File too large"

Hello,

I'm having the exact same issue with more than one torrent file.

Now I am currently running ext3 root filesystem, but I am downloading to an ntfs partition via SMB.

After the torrent does the initial file check and begins to download, it gets killed with this error. Its a 3GB file approximately 70% complete.

I am currently using python 2.4.2.

I thought at first the problem lay within Python itself, so I ended up recompiling python for large file support. And I am still getting this error, does the problem actually lie with python?

Was there any resolution you came to for this issue?