if Transmission tries to download a file too large for the filesystem, warn the user and stop the torrent

[charles]

Overseen at ​http://forums.somethingawful.com/showthread.php?threadid=3261709&pagenumber=2

My personal "transmission blows" story is the time Transmission spent 1.5gb of bandwidth repeatedly downloading the 4097th 1MB piece of an ISO, and silently failing to write it to disk. Confused, I loaded up uTorrent in WINE, it gave up after the first try with a fairly descriptive error message, allowing me realize that downloading >4GB files to a FAT32 partition wasn't going to work out.

I don't think it's so fair to expect a mac torrent program to have an error message relating to fat32 individual file size limits. Not even OS X itself gives a meaningful error message when you try to copy a file too large to a fat32 volume.

It says "Can not copy a file size of this size to this volume" or something of that naute. That seems pretty meaningful.

It was in Ubuntu, though that's irrelevant. The important part is that it failed to write to the disk, and didn't say anything at all. It treated it like a hash failure for the piece, and just kept trying over and over. uTorrent didn't tell me the file was too big either; but it did tell me that it couldn't write to the disk.

[charles]

Ah, looks like what the user suggested is what we now do.

We set the error message to "Error: File too large ($filename)" and then stop the torrent. Even better, since we have a high priority on the first and last pieces, downloading the last piece lets the user shortly after they started downloading the torrent.

[charles]

screenshot of a torrent that stopped and gave "file too large" error

[charles]

I don't know what version the OP in the somethingawful form was using, but it's fixed in the latest version...