Barely seeding - prefetch failed for : Unknown error: 0

[petter]

For quite some time now I've barely been seeding anything. Lots a client connecting and instantly disconnects, get green and and when I looked in the logs under debug I see lots of lines like this:

Code: Select all

inout.c:152 [Debug] the.torrent.x264.mkv: prefetch failed for "the.torrent.x264.mkv": Unknown error: 0

I'm seeding with VPN through an Airport Extreme, correct VPN port, green port light in Transmission, files on a locally mounted AFP volume.
And I'm running the latest Transmission 2.12

Am I the cause for those errors or is that a downloader problem?
Can I disregard them?

[jose]

I have the exact same problem with the same error. It's been going on for some time now. I switched to Vuze and had better results for one day and then that too produced the same problem. Ports are forwarded properly, green light on transmission, etc. but will only seed to 1-2 peers at max, usually zero. Called ISP and no problems there. This never used to happen. Very troubling and my ratio is shot. Any help would be much appreciated.

[petter]

How is your network setup?
Straight through a router to the internet or do you use any other service as well?

[Fhuber]

What is happening with this problem, is it a configuration problem or a compatability problem. I have the same thing happening and my DL rate is very small, and my internet is significantly slowed by running torrents with this message

port is open (green light)
global 200 per transfer 60
bandwidth DL 1000, UL 80
tested speedtest.net 3.2mb/s and, 0.12 mb/s
not in turtle mode


I am currently DL from 3 of 40 peers at between 0-10 kb/s
while uploading 10 - 50 kb/s

Any body know what is up with this

[Rolcol]

Just curious, are you guys downloading to external HDDs formatted as FAT32? I've seen that debug message but only when downloading onto my hard drive.

[jose]

Just curious, are you guys downloading to external HDDs formatted as FAT32? I've seen that debug message but only when downloading onto my hard drive.

actually YES, that was the case, but I tried downloaded to the local drive and still have the same problem with the upload speeds. So even if this solves the Prefetch error, the other problem remains.

Download rate will max out no problem, upload is the problem.

I've tried all sorts of network settings. At first, transmission worked for months without having ports forwarded. Then it stopped and I got a Red light. Then I did some research and forwarded the ports. Worked for a day or two and then the same problem, although with a Green light. You can literally see the peers trying to connect and getting dropped. Simple Connection to a DSL router, shared by a Macbook (sometimes over WiFi, sometimes not) and MacMini.

It would seem like a connectivity issue but I've exhausted all the options I can. Only problem is ratio.

[Jordan]

"Prefetch failed" should probably be removed as an error message. Prefetching is a hint to the OS to improve disk IO, but even if that hint fails it's not the end of the world. So unless there's a bug where that error message is causing the torrent to be stopped, I don't think that's the problem...

[Jordan]

Download rate will max out no problem, upload is the problem.

It would seem like a connectivity issue but I've exhausted all the options I can. Only problem is ratio.

Are you sure there are peers that want to download from you? How many seeders and leechers are in the swarm?