"result too large" repeating errors --

[Jordan]

Could someone experiencing this problem please check their logs and see if they have the same "write failed for ..." error messages that Chinstrap was reporting? Chinstrap was helping me track this down, but happily for him / unhappily for me, the problem disappeared for him...

[abc]

Yep, I have the same error: checksum failed, then write failed for, result too large. Download resumes for a few minutes when I restart it, then it crashes again. Closing mail seems to lessen the frequency of crashes.

[Jordan]

abc, were you trying to download all the files in the torrent, or just some of them?

[veldt]

The problem might be an underlying HFS+ bug that transmission triggers but utorrent does not. I haven't checked yet, but maybe transmission has too many files open for writing for HFS+ to handle; closing other apps seems to have helped in some cases -- maybe their open-files load was making things worse.

Happens with torrents with lots of small files; big torrents can of course have many more files.

HFS+ filesystem corruption definitely causes "Result too large" errors, but it might not be the cause here. This is based in part on the following URL about that error message; although not about transmission, it might have some useful information:

http://old.nabble.com/Re:-Result-too-la ... 20560.html

.. in part it mentions having lots of threads active.

Pausing and restarting seems to help. Naturally all open files in a torrent will be closed when it's paused, and they might not all be opened right away when it's restarted.

I haven't checked the source or used "lsof" yet; this is mostly speculation.

In this topic, all transmission versions were 2.12 and up. In the earlier, related topic

viewtopic.php?f=2&t=10870

, the 2 users with the problem who tried versions earlier than 2.12 definitely had corrupted hard-drives. So the trigger for this error may be something new in 2.12. (I know, that doesn't exactly pinpoint it

This is just a guess. If transmission buffers up incoming data and only opens and writes files once in a while, then sorry, I'm way off.

[amazondoc]

Hello all --

I haven't checked this thread in a long time. Interesting to see how it has developed!

I have continued to get this error occasionally, but not often, and almost always on large downloads (at least a coupla gbs, I think). Unfortunately, I haven't paid enough attention to the details to have further useful info to add.

I have been downloading the torrents to two external Firewire drives, as well as to my internal hard drive. Unfortunately, I haven't noticed whether the errors occur only when downloading to one of those specific drives, or whether it occurs on all of them.

I do usually have Apple Mail running, but again I have never correlated whether it is always running when the errors occur.

I just updated to Transmission 2.20 . If I receive any more of these errors on the new version, I'll post it here!

[amazondoc]

Yup, I'll try to do that. However, for some reason the incidence of these errors has dropped dramatically since December, when I started this thread. Unfortunately, like the other details, I haven't been paying enough attention to know *when* they became more rare. It may simply be that I'm not downloading as many big torrents as I was, or it may be something more signiicant like the new hard drive I got several weeks ago or the fact that I'm now running OS 10.6.6 instead of 10.6.5 . Adding to that confusion, I've just updated to 2.20 . I'm hoping that I never see the error again, but I'll try to get better info if I do!

[timta2]

This is still an issue (w/10.7 Lion and Transmission 2.33) so I'm giving it a bump. Jordan wanted to know if there were any messages in "the log" about "write failed". Is that the Transmssion log or Mac OS X's Console Log?

I just had this happen 3 times on a 14GB torrent containing 4,075 files.

The Transmission log reads...

write failed for "file.zip": Result too large
Result too large (/Users/-My user folder-/file.zip)
Pausing

And that was repeated 3 times for the 3 separate files that caused Transmission to pause three times with the "Results Too Large Error". I don't see any Transmission related errors in the Console log. I would be willing to provide any assistance I can to get this addressed and/or resolved. I really hate to use uTorrent but it seems to have no problems with the same torrents

[Horseylicious]

Just happened for me for the first time running 2.33 on 10.7.1. No error in the Console logs, just this from Transmission's log:

2011-09-18 20:40:29 +0000 inout.c:132 [Error] xxx: write failed for "xxx": Result too large
2011-09-18 20:40:29 +0000 torrent.c:487 [Error] xxx: Result too large (xxx)

[shazinaz]

I have gotten some good information here.

[Jordan]

Here's an earlier thread about "result too large": viewtopic.php?f=2&t=10870

[Horseylicious]

Here's an earlier thread about "result too large": viewtopic.php?f=2&t=10870

That's all well and good, except there's nothing wrong with my hard disk: all disk repair and fsck checks come up just fine.
And yet every time I try to download a very large file, I get this error.

[Horseylicious]

Horseylicious: What is the percentage of the drive you are downloading to that is available and how much free space does this translate to? What is the size of the torrent you are trying to download? Would you mind trying the latest nightly build and then if you get the error, search in Console.app for Transmission errors and also T's Message Log . Please copy and paste the full error(s) and let us know T's version and revision (r) number as well.

Hi x190. The errors have come running 2.33 (12565). I get no messages in Console.app - just the log from Transmission, exactly as reported above. The files were around 35GB, downloaded to a 1TB drive with 350GB available. I did verify local data when they were done and they checked out fine.
I would try running a newer build of Transmission except most of my trackers won't allow betas. Also, I don't download huge files very often, which means for me the error is very rare.

[Horseylicious]

How did I miss that?
Just checked: Macupdate still has 2.40b3 up, as does the Transmission homepage…

[Horseylicious]

Still having freezes (the app is unresponsive for a full 15 minutes) trying to download very large files running 2.42, but no "result too large" errors this time from Transmission's Message Log.
See my post here: viewtopic.php?f=4&t=12066

[lhawkins]

I've also got these errors on various torrents with Transmission from versions 2.1 up to 2.4.2. These errors always seem to happen when the torrent I download is very large AND composed of many small files. I've downloaded 30GB torrents with a few files in them with no issues, however the current file I'm having trouble with is only around 3.5GB but is composed of around 3000 files. The hard drive it's currently downloading to is a FW 800 connected 6TB RAID 5 array (OWC Mercury Elite AL Pro Qx2) although as a test, I "Moved the data file" to my internal SATA drive which made no difference.

Usually, when this happens I just click the resume button every few minutes until the torrent is done and since it doesn't happen often (as I don't download large torrents with many small files often) it's not that big a problem for me, however I'm pretty sure it's a problem with Transmission as Azureus and uTorrent don't have the same problem with the exact same torrent.