Jump to content

Prevent breaking completed files as 99.9% on reseeding by same torrent


cdotrun

Recommended Posts

Posted

It is always a good idea to reseed the files you have using the same torrent seed you got the files with and still wanted by others. A problem with poorly designed P2P programs, they convinced my utorrent that the first piece (often) is invalid, causing utorrent to blank out that part of the file I have that I have downloaded for days.

Worse, I am the only seeder! The leeching P2P programs were unaware that I have more pieces than they do, so they faked that they are holding on a piece that they have (which in reality they dont) to prevent my utorrent from leech-and-run.

So, I would like utorrent to show a dialog when another client reports a hash error on a piece you already have, and give the option to let it fix all or just this (which piece in which file) or ignore all or just this.

Or better: download the conflicting pieces other clients claimed anyways and let the user decide later to patch or not. Perhaps ability to keep them for the user to test out the validity of each pieces.

Posted

1. Other peers don't tell you when they receive hashfailed pieces.

2. I can easily imagine this being abused: think swarm poisoners randomly lying to seeds by telling them that they have hashfailed pieces. What are the consequences? Seeds waste bandwidth by redownloading pieces that are in fact already valid in their copy, but the poisoner lied about. Sure, they can hashcheck the piece before attempting to redownload, but what happens when the poisoner decides to lie about a ton of pieces? Massive CPU usage spike.

Better solution: tell the other applications to stop modifying the files without your consent.

Posted

No no no there were NO poisoners involved in my case! But leechers were BitComet and Xunlei.

What appeared to me was the file I was trying to reseed uT somehow reported its first piece missing, and when I open that file with some editor I see that it starts with blanks instead of some scrambled binary text!

Nice if you could add an option to force completed files read-only to others so whatever miscommunicated between my uT and the other leechers, it won't mess up what is already on my side?

Thanks!

Posted

Other clients don't "report" to µTorrent about any hashfails. If µTorrent detects that a piece is corrupt, and it removes the piece, then it's only doing its rightful job to prevent hashfailed pieces from being seeded.

I honestly don't see where this request is going. Read-only? Requested before. Whether other clients munge the data is none of µTorrent's business -- you need to take it up with those client developers and ask them why they decided that messing with existing data is a Good Idea™.

Why are you even using multiple clients to download/seed the same files anyway?

Posted

I am completely sure there are nothing hostile on my computer! uTorrent is working perfectly! I know this is a silly request to make a seeding torrent "read-only" to others, but I would like this just in case the other clients were trying to mess up the files I just download and forgot to backup to elsewhere not shared.

Very well... let me make this a "allow users to run a script or program on the files once it is completed" feature request, just like A-----s the bogged slow Java-based client, just so I can run a DOS command "attrib +r %file_in_completed_torrent%", antivirus or perhaps to sync files immediately with my network drives and media players.

[EDIT: oops, HA HA, it's already there in the torrent properties, but can you also put it as an advanced option as default for all torrents added? I don't want to have to repeat the same configuration on each task.

Posted
I am completely sure there are nothing hostile on my computer! uTorrent is working perfectly!

Commercial software can indeed act in a hostile manner.

And I think arbitrarily corrupting your download files WOULD qualify as such!

Posted

Thanks Ultima about the global run on completion! That is what I will need. Let's hope the Devs can get to it soon! (8 more nano-revisions to go?)

That shouldn't be hard, it's just an extra advanced setting that utorrent can copy the string value to a new torrent when it is added. I think the multi-trigger part would be easy with DOS or Linux: just point to a batch script :-)

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...