Thread: uTorrent : Disk IO related errors with a large amount of torrents

I am running Windows 7 x64 Enterprise, uTorrent 2.2 build 23235 and I normally run 50 -60 torrents at a time (mostly seeding) and have had no issue. However, I recently increased the number of torrents that I am seeding to 200 and I will intermittently receive the following two errors on random torrents:
"Error: Files missing from job. Please recheck."
"Error: Element not found."

I will stop the torrent, force re-check, and the file will no longer be 100% complete but something like 99.8, 99.9 percent complete. It will finish to 100% and seed fine.

These are torrents from multiple communities (private and public).
I have tried deleted the torrent and re-adding it.
The directory and file names are not too long nor do they contain any special characters.

I have been unable to find a definitive answer for these two errors with Google. Several searches pointed to turning uTorrent's diskio.coalescewrites to FALSE. This had no affect.



Can anyone help?

- damnfinevulcan

I have some issues with ver 2.2 recently, and I just update it to 2.2.1, then every thing fine now.

Hi, are you trying to cross seed data i.e download from one tracker & seeding at another tracker? Make sure you do complete hash check before starting the cross seeding. And if it comes short of like 0.2% then you can't seed it to both the trackers at the same time.

Originally Posted by sTuDD

Hi, are you trying to cross seed data i.e download from one tracker & seeding at another tracker?

I agree with sTuDD . I think you are trying to cross seed. Otherwise I am using the same Version and seeding about 900+ Torrents and has got no Problem.
If you have the Problem which sTuDD mentioned then follow the Instructions Below..

EDIT:
Right Click on the Torrent go to Advance > Set Download Location.
And then specify Location.
And Then Click Force Re-Check while Right click on the torrent.
And when checking is complete then click Start and you are Done.

Originally Posted by sTuDD

Hi, are you trying to cross seed data i.e download from one tracker & seeding at another tracker? Make sure you do complete hash check before starting the cross seeding. And if it comes short of like 0.2% then you can't seed it to both the trackers at the same time.

Yes, I am cross seeding. The torrents are 100% with Tracker 1 and when the torrent associated with Tracker 2 is added I set the download location appropriately and do a force re-check. It then may show up as 99.x% complete at which point it finishes to 100%. Now this is where I have a problem: at a point in the future random cross-seeded torrents for Tracker 2 will show up with the 2 originally reported errors. Have I not followed a necessary step?

I have been using the steps humbug suggested when I see these errors but they continue to happen.

As an update I updated uTorrent to 2.2.1 and have not had the errors. I will report back. Thank you for the help thus far.

This is behaving as most clients do. I get the same errors on cross seeded torrents in rtorrent as every torrent's set of data differs ever so slightly. If the torrent doesn't actually stop, ignore it, it just means you can't send the corresponding chunk that someone requested because it was overwritten with the chunk from tracker 2. Your client just reports the error and moves onto another request.

Example in scene releases would be a nfo getting tagged by a topsite script, tacks on a name to the bottom of the site it bounced through, few bytes difference between trackers, depending on where the tracker got it.

Rehashes result in which ever torrent you rehash last getting its version of the release, so all previous rehashes of the same release would report issues if that part is requested.

Q

------------------------Post auto merged------------------------

The only way to avoid these errors is to copy the entire release to a different directory and specifying tracker 2 to use that copy of the data. It will sync its differing chunks and no other torrent would be fighting it since it is its own copy entirely. This would use a lot of disk space, and manual intervention, unless you understand hard links.


Q

This is exactly right copy the file to another location and then from tracker 2 download it to the new location letting it download your last.2% I do this ALL the time it works for sure. I am using Windows 7 X64 bit Ultimate and I have the same exact issue as you when I try to seed to both trackers from same file.

Originally Posted by opensaysme

This is exactly right copy the file to another location and then from tracker 2 download it to the new location letting it download your last.2% I do this ALL the time it works for sure. I am using Windows 7 X64 bit Ultimate and I have the same exact issue as you when I try to seed to both trackers from same file.

I located the affected torrents and followed this step. I will report back after a period of time to see if the torrents are stable.

The issue seems systemic and all of the torrents that are cross seeded with Tracker 2 have produced either of the errors. Unless there is another solution I will have to duplicate the files and use separate directories.

Any other ideas? :)