[SOLVED] Error: Result too large repeating

[nveeser]

OS: Max OS X 10.6.5
Transmission: 2.12+ (11425) "dev build"

I have three particular torrents which I cannot seem to keep going.
Each one of them runs for several minutes and then halts with the above error.
I restart the torrent and repeat...
Each one is ~4GB from the same tracker.
I checked the location of the current download drive and the eventual destination (on the same disk) and I have ~80G free,

I am currently running with on one of the three torrents downloading and none uploading to see if that helps

Thoughts:
Error message seems to be hiding what is really going on.
I assume you are getting back something from fopen or the like and conflating it into a "Result too large" message.
If I knew how to use dtrace better I would see if I could trace down result code.

Each also has a large number of small JPG files.
I wonder if the issue arrises when a new file is first seen and the file on disk is created.
I have not had this problem with other torrents of the same size and complexty

[cordell]

I also experience the error message "Error: Result too large" for the first time today.

I just upgraded to Transmission 2.12 (11412) before. I run Mac OS X 10.6.5. A bug?

[Rolcol]

I also experience the error message "Error: Result too large" for the first time today.

I just upgraded to Transmission 2.12 (11412) before. I run Mac OS X 10.6.5. A bug?

How big was the torrent? Were you downloading to an external device? If yes, is there enough space for the full torrent? FAT32 has a single filesize limit of 4GiB. You can have torrents bigger than 4GiB but they cannot have files inside of them that are larger than 4GiB when going onto FAT32.

[nveeser]

FWIW
I am using HFS+
This happened before the switch to 10.6.5
Torrent is round 3GiB and no file in there is above 5MiB

[thisseeker]

Hello to all,

I have had the same error on my Mac OS X 10.6.4 system with Transmission 2.12, the torrent was less than 2GB and the files that kept causing errors were of less than 1MB in size each.

I went to http://download.m0k.org/transmission/files/ and downloaded the Transmission 2.11.dmg and after replacing it on my system the download works just fine now with no errors.

Hope this helps others.

Peace and Well-Being

EDIT:
It turns out I gave out cheer too soon! The torrent just gave the same error on the same torrent, different file... Still weird. I'll try earlier versions and report what works for me.

[bluntegg]

I'm also getting the same error over and over on a torrent that's just under 2GB and mostly jpg files with some png. Transmission 2.12 and OSX 10.6.5. I was also getting this before I updated the previous Transmission version to 2.12.

I booted from the install disk and successfully did a Repair Disk and Hardware Test. The problem is still occuring. Any other ideas?
I should also note that I've never had this problem ever with any torrent until now.

[thisseeker]

Looks like an I/O error. Boot from your install disk and run Disk Utility (Repair Disk). Run Apple Hardware Test as well (install disk - hold down D key while booting).

https://trac.transmissionbt.com/wiki/TorrentsPaused

Firstly I'd like to thank x190 for their suggestion to check the disk itself. That got me started on a good path towards resolving this issue.

I'm also getting the same error over and over on a torrent that's just under 2GB and mostly jpg files with some png. Transmission 2.12 and OSX 10.6.5. I was also getting this before I updated the previous Transmission version to 2.12.

I booted from the install disk and successfully did a Repair Disk and Hardware Test. The problem is still occuring. Any other ideas?
I should also note that I've never had this problem ever with any torrent until now.

@bluntegg: I did the same but went one step further. From the Mac OS X INSTALL disc instead of running Disk Utility, run Terminal. When the terminal window opens type this in and press return/enter:

Code: Select all

umount /dev/disk0s2

Then type in this and press return/enter:

Code: Select all

fsck_hfs -ry /dev/rdisk0s2

The -r is for Rebuilding the Catalog Tree and the -y is to say yes to all prompts.
Wait for a while, it will likely notice some errors in the volume header (like it did on my system) and perform some repairs then checks again and once it is done, you can try the last command again to make sure it fixed the problem. After that, quit Terminal and Quit the Installer to reboot your system. It should be good after that.

PS
If your HFS+ Volume is not on disk0s2, type in:

Code: Select all

mount

to get a list of the volumes on your system and then find the name of your harddrive-volume and use the /dev/disk?s? that matches your volume with the fsck_hfs -ry /dev/rdisk?s? command. replacing the question marks with the appropriate numbers found using the "mount" command.

Peace and Well-Being,
thisseeker

[bluntegg]

Thanks thisseeker, I tried this twice as written out above. Still happening, although less often. No clue what's going on. I know there is something wonky with my HD though as for the last year everything just locks up and crashes about 2-3 times a week. Thought it was HD space, but I cleared out a bunch of stuff and have about 30% free. Oh well, it's giving me the error every 30-60 mins now as opposed to every 2 mins before. Thanks for the advice! Will just need to keep an eye on it.

[thisseeker]

x190 you're giving me cause for fright.. ... I actually got scared at the thought of losing it all, for a moment.. good advice nonetheless! and I would do well to heed it. Thank you kindly!

Peace and Well-Being,
thisseeker

PS
any recommended cloning applications from good experience? kindly appreciated!

[thisseeker]

Thank you!

Occam's razor sits true in this case!

Peace and Well-Being,
thisseeker

[thisseeker]

My Peace I Give Unto You

You're an interesting cat, x190!

Thanks for the link