On Fri, Jul 23, 2010 at 8:49 AM, Robin Smith <[email protected]> wrote:
> > > 2010/7/23 Łukasz Michalik <[email protected]> > > On 21:53 2010-07-22 -0400, Robin Smith wrote: >> > I am on a couple of different trackers that often have the same >> content. >> > In order to build ratio on one site (Tracker A), I decided to try and >> > reseed files obtained from a different site (Tracker B). >> > >> > On Tracker A, I downloaded the torrent file, stopped it, right >> clicked all >> > files and said "Don't Download" (I am using a web interface to >> rTorrent >> > 0.8.6/0.12.6 called ruTorrent - it is running on a QNap TS439Pro NAS >> box). >> > I moved the files I had downloaded from Tracker B over top of the 0 >> byte >> > files from Tracker A (0 bytes since nothing had downloaded). I then >> issued >> > a re-check on the torrent for Tracker A. It ran through the recheck >> and >> > said I was 52% complete, which sounded about right based on the files >> I >> > had moved. >> > >> > When I went back to Tracker A, it reported that I had downloaded 13GB >> of >> > the torrent from peers on the Tracker. However, I had not downloaded >> > anything other than the torrent file itself. My ratio on Tracker A >> was >> > borked. >> > >> > I have been working with admins at Tracker A to understand why this >> > happened, and the consensus there is either: >> > >> > 1. User Error >> > 2. Client Issue with rTorrent 0.8.6/ libtorrent 0.12.6 >> > >> > The suggestion from most folks over there was to talk to rTorrent >> devs >> > about it, so here I am... >> > >> > If it is 1, can someone help explain what I might have done wrong? >> What si >> > the correct way to reseed so that rtorrent/libtorrent does not report >> that >> > I downloaded data >> > >> > Could it be 2, a client issue? >> > >> >> Never had any issue like you described, I suspect another option though: >> >> 3. Frontend issue with ruTorrent. >> >> What I do in that scenario is just put .torrent from tracker B in >> watch dir, rtorrent picks it up, notices files with same names exist, >> rehashes them (if uploaders on tracker A and B did what they should >> have which is 1:1 identity in data and filenames, given they were >> uploading same release, I get 100% completeness) and starts uploading >> with ratio 0. It might not work perfectly if uploader decided to do >> something as stupid as clobbering .nfo file, adding/removing some >> files or even reencoding. >> >> -- >> Pozdrawiam, >> Łukasz P. Michalik >> > > Good suggestion, I'll see if I can find an example where the file names are > the same. Unfortunately, they were different. The TV trackers often rename > the files to follow their "Season Pack" guidelines. Its actually quite > annoying, but I have no control over it. > > Dumb question, but how could ruTorrent be the issue? Isn't it just a > "simple" front end to libtorrent/rtorrent as opposed to interacting with the > tracker? Or am I not understanding what's involved in the front end ... > Update: The problem is caused when you have the torrent started and do the re-hash. If you ensure the torrent is stopped first, do the re-hash, then start the torrent this issue does not occur. This fix was found in a thread from 2008 on the tracker in question and supposedly the bug was reported at Rakshasa and confirmed. Two years later and the bug still exists. I'm not a dev and I don't know what more to do other than to confirm that an old bug is still in there. Thanks
_______________________________________________ Libtorrent-devel mailing list [email protected] http://rakshasa.no/mailman/listinfo/libtorrent-devel
