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
Your post seems kind of unrelated and random. Maybe you can clarify what exactly you are trying to say. Are you saying that Apple has so much screwed up in Mac OS X that we should blame Apple for this?
Can we get a developer to chime in with their thoughts about this issue?
That was kinda what I was getting at.
There have been, and still are a crap load of random issues affecting Snow Leopard.
Permission/Samba issues, crapload of read/write issues to HDD & Even worse on USB external drives, issues when dealing with large data. Some people have tried even reloading and getting memory issues. Swapping for a new Hard drive and having the same issues
Some people have reported fix's with 10.6.5 but not very many.
The sheer quantity of these issues is fairly suspect as to why this is happening, something like dodge hardware controllers perhaps that was manufactured during a certain period.
so I was basically saying that apple is the problem & until all the bugs are kinda ironed out , i think it's fairly hard to find a fix.
lakrigg wrote:That was kinda what I was getting at.
There have been, and still are a crap load of random issues affecting Snow Leopard.
Permission/Samba issues, crapload of read/write issues to HDD & Even worse on USB external drives, issues when dealing with large data. Some people have tried even reloading and getting memory issues. Swapping for a new Hard drive and having the same issues
Some people have reported fix's with 10.6.5 but not very many.
The sheer quantity of these issues is fairly suspect as to why this is happening, something like dodge hardware controllers perhaps that was manufactured during a certain period.
so I was basically saying that apple is the problem & until all the bugs are kinda ironed out , i think it's fairly hard to find a fix.
That's terrible advice. Unless the developers can specifically point to an Apple issue, we have to assume this is a Transmission problem. So what are the common elements with everyone who is experiencing this issue? External USB drive? Anything else?
I am also having this error appear repeatedly. It does not seem to occur for small files, but pops up every few minutes on a large torrent. Quitting Apple Mail had no effect on the problem.
I am running OS 10.6.5.
I am saving the torrent files directly to my hard drive (no usb drives)
I am running Transmission 2.13 (11501)
Actually, now I've quit everything but Transmission, Safari, Little Snitch and all the necessary OS processes and ...the error has quit appearing. I had Apple Mail, GroupWise Email, iTunes, iCal and Miro running. Seems like a fair possibility that a conflict is occurring.
i'm having this problem as well, very frustrating. i don't use apple mail. as another stated it seems to be particular to torrents with a large amount of small files...
i'm trying the same torrent i've been having a lot of issues with on utorrent and it's running seamlessly so it must have something to do with the client.
That was kinda what I was getting at.
There have been, and still are a crap load of random issues affecting Snow Leopard.
That's silly. I don't have any of those problems and haven't heard of others having those problems and I personally know quite a few Mac owners. That's like attributing Bob's alcoholism to the fact that there are just so many problems in this world, even though Bob has a lot of problems. LOL.
So what are the common elements with everyone who is experiencing this issue? External USB drive? Anything else?
We are all using Transmission with Mac OS X. Not all of us are using an external USB drive, as I'm using my internal SATA drive.
Filesystem on drive is ___? Torrent size is___?
HFS+ Journaled, of course. Who uses anything else these days? At least in my case overall torrent size doesn't seem to matter. If it contains lots of small files that is when I have problems. If all of those files are compressed (RAR'ed for example) I don't seem to have problems even if the overall torrent size is larger or smaller.
I've been getting the same thing. I watched the logs and noticed that I always get a checksum failure just before the error:
2011-01-14 21:06:55 -0500 peer-mgr.c:1461 [Error] MAME 0.141 EXTRAs: Piece 716, which was just downloaded, failed its checksum test
2011-01-14 21:07:29 -0500 inout.c:159 [Error] MAME 0.141 EXTRAs: write failed for "MAME 0.141 EXTRAs/pcb/couplei.png": Result too large
2011-01-14 21:07:29 -0500 torrent.c:1638 [Info] MAME 0.141 EXTRAs: Pausing
...
2011-01-14 21:08:30 -0500 peer-mgr.c:1461 [Error] MAME 0.141 EXTRAs: Piece 2406, which was just downloaded, failed its checksum test
2011-01-14 21:08:54 -0500 inout.c:159 [Error] MAME 0.141 EXTRAs: write failed for "MAME 0.141 EXTRAs/cabinets/mt_gaxe.png": Result too large
2011-01-14 21:08:54 -0500 torrent.c:1638 [Info] MAME 0.141 EXTRAs: Pausing
I'm trying to download a large file (3.37GB) and get the same error: "Error: Result too large"
I've read thru this tread on and see lots of others reporting the problem, but I don't see any, unless I missed it, suggestions, workarounds or fixes. I too am using 10.6.5 and had Apple Mail running while Transmission was downloading. Firefox was open too along with Dragthing, Quickeys and preview. But I have 8 GB of RAM. My Transmission downloads to a folder on my main internal HD, which has plenty of room available: 648GB.
Has anyone updated to OSX 10.6.6 and seen any improvement? Think I'll try that.
Has anyone concluded whether this problem is an Apple or Transmission issue?
Has anyone tried another Bittorent app to rule out Transmission?
I upgraded to OS 10.6.6, turned off all other apps and tried to download the 3.34GB file again and while I got farther than last time, this time I made it to 1.3GB and the TM froze with the error msg: result too large.
I was about to delete the item from my All window in TM, I clicked the pause button, but for grins clicked it again as if to start the download and low and behold the download started and now I'm up to 2.37GB downloaded AND I have Apple Mail, Contacts and Firefox running this time. I'm ranging from 400 to 500kb dlnld speed from just 8 of 12 peers. Can't beat that!
TM says I have around 1 hr remaining, so we'll see if I make it thru this time.
So next time you bet the error, try clicking pause icon to the right of the progress bar and then click it again and see if your download resumes.
Well x190, consider yourself lucky. I have been using TM longer than you and had never seen it until last night either. But if you read this thread, you'll see that there are a few that have been getting this this error.
After clicking the pause on and then off, as I stated previously, TM started the dnld again and completed it!
I am now seeding and have 9 hrs to go. I will be interesting to see if the error happens during seeding, but I tend to doubt it.
For those of you that do get the error, please try clicking the pause icon on and then off and let us know your results, let us know if dlownld starts up again ok.
I next need to check the files and make sure they are ok.
Also having this issue. Downloading to main drive, not external. Running 10.6.6 and latest build of Transmission. Shut down mail, doesn't help. This appears to be new behavior. I've had assorted issues with Transmission during my 2 years use, but this is new. All other issues seem to sort themselves out with updates. Hope this will too. It's annoying to have to keep starting the DL up again periodically.