jonaf Posted June 7, 2006 Report Share Posted June 7, 2006 I've read all the posts & links to the 'tons of hashfails' & 'bad torrents' and the 99.9 problem (system files trying to get overwritten or DMZ mode for a router). Thing is I have no router, the incomplete files are simple .mp3, and I'm the only seed. Everyone is stuck at 99.9%; availability is 1.999. # Seeds are correctly displayed as 0(1).I don't know if it's hashfails or not as I'm a seeder. Do clients report hashfails back to the seeder, or does it simply re-request the data. Any way to determine from the seeding side (from the log perhaps)?Details on the actual torrent: 24 files, all mp3, piece size 64KB & there's 1524 pieces. The files that are not getting completed are tracks 7 & 8. Track 7 is 349.8KB while Track 8 is 6.5MB. The uncompleted stuff seems to be the end of track 7 & beginning of track 8. The below is when I chose to download the torrent to a NEW folder (to ensure that everything I get was from peers & not me....from the now 0.999 availability):(Tracks are sorted numerically, track 7 is selected)The peculiar thing is that if I opened the .torrent file & pointed it to the previously downloaded 99.9% completed data folder, and selected 'open for seeding', uTorrent surprisingly let me seed without error & shows both track 7 & 8 @ 100% completion. So I thought maybe the files were actually at 100% (on-disk) but uTorrent wasn't showing it correctly. But to invalidate that claim, I played track 8, and there is in fact some seconds seconds missing from the beginning & a slight second missing from the end of track 7. This is a gapless album so it's pretty easy to tell there's stuff missing.What could be the problem?------------Also, when I open the .torrent for seeding (from the original data), I start sending stuff out to peers but that slowly trickles down after about 1 or 2 pieces....and most peers end up with only 64KB or 128KB uploaded to them (2 pieces)....is this evidence of hashfails?Also...Don't know if that means anything though....peers status is 11(24)------------------------728.969: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:0->16384728.969: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:32768->16384728.969: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:16384->16384729.062: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:0->16384729.062: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:16384->16384729.062: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:32768->16384730.641: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:32768->16384730.750: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:32768->16384731.047: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:0->16384731.047: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:49152->16384731.047: x.x.x.x : [burst! 1.1.3 ]: Got Request: 474:16384->16384731.141: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:0->16384731.141: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:16384->16384731.141: x.x.x.x : [burst! 1.1.3 ]: Sending Piece 474:49152->16384Hashfail? Looks to be continually requesting the same 4 pieces...and my upload speed is pretty much almost max (30KB) just for this one client.------------------------Sorry, this was the concatenation of 3 consecutive posts 'cause I forgot about the 'rule' at first. Link to comment Share on other sites More sharing options...
Firon Posted June 7, 2006 Report Share Posted June 7, 2006 DON'T USE OPEN FOR SEEDING. If µTorrent said your files are not complete, then they are not. You changed one of the files, and that screwed it up.Yes, you are sending out bad data. No, they don't say there's a hashfail, they just re-request it until they ban you eventually. Link to comment Share on other sites More sharing options...
jonaf Posted June 7, 2006 Author Report Share Posted June 7, 2006 DON'T USE OPEN FOR SEEDING. If µTorrent said your files are not complete, then they are not. You changed one of the files, and that screwed it up.Yes, you are sending out bad data. No, they don't say there's a hashfail, they just re-request it until they ban you eventually.I haven't (manually) changed any of the files...I guess I'm mistaken about what the procedure is when you open a torrent? My understanding is:1) it does a check of the data against the hashes stored in the .torrent2) if any of them failed, your status is set to downloading, unless if you checked 'open for seeding' it just won't let you seed.Is that right or wrong?And are you saying don't use oepn for seeding only for the case in which I downloaded the data & opened it for seeding, or for any torrent I create or download?What causes hashfails? I would really like to resolve this problem. I've so far uploaded 80MB to that one peer after he was 99.9% complete, but his 'Burst' client just keeps on requesting.Does anyone know of a .torrent-viewing application? I would like to locate the hash stored in the torrent and compare it with what data I have on my hard drive. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted June 7, 2006 Report Share Posted June 7, 2006 When you force a re-check and the piece goes missing, the data in that piece is bad. Period.Open for Seeding skips the hash check. If the filesizes match, it lets you seed, even if the data mismatches. Link to comment Share on other sites More sharing options...
jonaf Posted June 8, 2006 Author Report Share Posted June 8, 2006 When you force a re-check and the piece goes missing, the data in that piece is bad. Period.Open for Seeding skips the hash check. If the filesizes match, it lets you seed, even if the data mismatches.Thanks, all clear now. Any reason why it skips the hash check when you open for seeding, since I'm guessing it's by design?Also, I have to confess...I am not the original seeder so it is possible that he made the torrent, some of the data got changed up a little, then posted it. What he did was supply tracks 7 & 8 as http downloads so we could complete the full download. I guess to differentiate on whether I'm sending bad data or if data was changed is to create the torrent with the 99.9% downloaded + http'd tracks 7&8 and diff the hashes in the file. If different, data was changed after the .torrent was created; otherwise it's an inet problem. Correct? Link to comment Share on other sites More sharing options...
Ultima Posted July 1, 2006 Report Share Posted July 1, 2006 Because if you're opening for seeding, you're declaring that you have 100% of the pieces -- that's how you're a seed. If you know you have 100% of the pieces, and set that option, why would you want to hash check again? At any rate, the option is more explicit now, having become "Skip hash check" instead. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.