"result too large" repeating errors --

[amazondoc]

Hello all --

I found a recent thread on this topic, but it appears to be locked -- and there did not appear to be a definitive solution for the problem in that thread -- so I'm posting my own experience with the errors here.

Mac OS 10.6.5, Transmission 2.12 --

I am getting this error repeatedly, but only on my very largest torrents (over 8 GB each). If I hit "resume selected right away" the download will resume, but the error is likely to appear again. One of the three large torrents that have had this problem has now successfully completed download after multiple error messages. The other two are still in progress. Many smaller torrents have completed without incident.

What is causing this problem? What can I do about it?

[amazondoc]

Thanks -- but, as I mentioned in my first post, I already read that thread. Although it offers several possible solutions, if you'll read it closely you'll see that none of the solutions really worked. The "thank you" at the end was for teaching someone how to clone a drive, not for how to solve this problem.

If anyone does have suggestions on solving this issue, please let me know. Thanks!

[amazondoc]

Perhaps you missed fsck_hfs -ry a bit before that?

Nope. Perhaps you missed bluntegg's response to the fsck suggestion?

[amazondoc]

Nooooooooo, this part of the response:

Thanks thisseeker, I tried this twice as written out above. Still happening, although less often. ....Oh well, it's giving me the error every 30-60 mins now as opposed to every 2 mins before.

In my case, there's nothing wrong with my HD. The files are being stored on an external hard drive, which has been tested perfectly normal. Call me silly, but I don't really feel like messing around on the command line when it isn't gonna solve my problem anyway.

If anyone does have any useful suggestions that are likely to actually solve this problem, please let me know. Thanks!

Edited to add --

btw, the second large torrent has now finished downloading, finally. The third one is still in progress. It appears that the main consequence of this repeated error message is a prolonged download time, since I have to restart (not start over, just "resume selected right away") the download every time it occurs. So it's annoying, but not fatal.

Edited again to add further --

After receiving several more of these "result too large" errors, the final large torrent finally finished downloading over night. I'm still hoping that someone will have a good solution, but it's now obvious that the downloads can be completed successfully even when the error occurs many times.

[scooterbaga]

I'm having the same problem. I'm using Transmission 2.13, on 10.6.5. I'm saving my downloads to an external drive. The external drive is a drobo. (Although it shouldn't matter, just thought I mention that...) The drive checks out fine in Disk Utility.

[dirty]

I've been having the same problem for a while now. I'm also downloading to an external USB drive, running 10.6.5. All the torrents which exhibit this behavior are between 500-900 MB and contain about 1100-2500 files each. After a few minutes, each will report the "Result too large" error and I'm forced to manually restart it.

My external drive reports no errors from Disk Utility.

[timta2]

I too have been having this problem for a while. My disks are fine (according to Disk Utility, Disk Warrior, etc). It seems to only happen to me with torrents from PureTnA. Usually torrents with a high number of small files. It's probably just coincidence that they are all from that site though since it's the only site I download from that has such torrents. The same torrents resumed while using Utorrent (I know, yuck) complete just fine and seed until completion, so it's definitely something related to Transmission.

[Alan Mercury]

I'm also receiving this error on Transmission 2.13 and Mac OS X 10.6.5 on torrents with many small files.

[Litehouse59]

This problem is still not fixed. U/L is fine, but D/L is a reload every five minutes on files over 4 or 5 gb. The only change has been the update so i have to think it's the source of the issue. I like Transmission, but this will drive people crazy and to other options. Any progress? Tx!

[purecharger]

I began having this error with large torrents, and found that these messages were appearing in /var/log/system.log at the same time as the torrent download paused with that error:

Code: Select all

Dec 30 07:19:45 ryan-mbp Mail[4177]: EWSServerVersion: 8.2.254.1
Dec 30 07:19:52 ryan-mbp mdworker[4167]: socket(PF_ROUTE) failed: Operation not permitted
Dec 30 07:19:52 ryan-mbp sandboxd[4186]: mdworker(4167) deny system-socket
Dec 30 07:19:53 ryan-mbp sandboxd[4186]: mdworker(4167) deny network-outbound /private/var/run/mDNSResponder
Dec 30 07:19:53: --- last message repeated 2 times ---
Dec 30 07:19:53 ryan-mbp mdworker[4167]: socket(PF_ROUTE) failed: Operation not permitted
Dec 30 07:19:53 ryan-mbp sandboxd[4186]: mdworker(4167) deny system-socket
Dec 30 07:19:53 ryan-mbp sandboxd[4186]: mdworker(4167) deny network-outbound /private/var/run/mDNSResponder
Dec 30 07:19:53: --- last message repeated 2 times ---
Dec 30 07:19:53 ryan-mbp mdworker[4167]: socket(PF_ROUTE) failed: Operation not permitted
Dec 30 07:19:53 ryan-mbp sandboxd[4186]: mdworker(4167) deny system-socket

A quick bit of googling showed that these are Apple Mail related errors, and sure enough, after I quit Apple Mail none of my torrents get the "Result too large" error anymore.

Are you guys running Apple Mail when you get this error?

[Litehouse59]

Wow - yes I am. Trying with it off now. Wonder if there's a fix if this is the problem...

Unfortunately, that changed nothing - 10 mins later I got another error message. This seems to be a common and frustrating problem, wonder why it's not been addressed via update?

[Alan Mercury]

I wasn't running Apple Mail when these problems occurred, but I did have Google Notifier running.

[dirty]

In my case, this machine is just running Terminal, Transmission and Safari. Nothing else.

[lakrigg]

There are lots of issues with Apple atm,
12/16/10 01:15:53 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
12/16/10 01:15:54 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
12/16/10 01:15:55 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
Seams to kill shares
12/16/10 01:09:56 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public', from '//admin@xxxxxxxx/Public', dead

Apache issues also, just all round network conflicts it appears.
These will no doubt be the cause of the transmission probs that have been posted with 'invalid arguement' / write issues also.

They give the BSD backend a bad name

[timta2]

Um, isnt't "mdworker" related to Spotlight? And isn't "mDNSResponder" related to Bonjour? I don't see how those errors are related to Apple Mail anyway.