Hi. I'm fairly new to uploading torrents. Most of my torrents have worked fine, but once in a while the following problem occurs. I'm seeding a torrent for a file on my hard drive (usually a big one, like an ISO), and many hours (sometimes days) after I started seeding, Azureus pops up an error message saying some chunk of the file is corrupted and it will redownload. Ignoring the original file on my hard drive, Azureus then tries to download it from the Internet. The problem is, I'm usually the only seeder! When this happens, naturally I check the original file to see if it's all right, and invariably it is fine. I have peers waiting for this seed, so I delete the torrent from my download queue and open it up again using the "Open/Torrent File..." menu. Azureus tells me that the file already exists on my hard drive, and says that if I open this torrent file, it will check the original to make sure it is complete.
Now, in theory, what Azureus should do is check the file, and once it finds that the file is complete, move it to the upload queue, right? Well, what happens is that it gets to 99.8%, decides that the file is not complete, leaves it in the download queue and tries (fruitlessly) to download the "missing" 0.2% When this first happened, I deleted the torrent file, made a new one, and posted a message to the forum asking those who had been downloading to delete the file and try the new torrent file. But then two days later, the same thing happened with the same file! I know this ISO file is fine. I've opened it and run it twice. I don't want to delete the file and once again ask everyone to delete it and start again, particularly if the same thing is going to happen 2 days from now.
Have any of you ever had this problem, and, more importantly, do you know how to fix or avoid it? I'm using Azureus 3.0.4.2 on a 2.16 GHz Intel Core Duo MacBook with 2 GB of memory running OS X 10.5.1. I have a fiber optic Internet connection through NTT, here in Japan, and my upload speed on Azureus occasionally surpasses 1MB/s. The file I'm currently having trouble with can be found here. [Edit: Now I've got the same problem with another ISO file here.]
Any help would be greatly appreciated. :bow-pray:
Now, in theory, what Azureus should do is check the file, and once it finds that the file is complete, move it to the upload queue, right? Well, what happens is that it gets to 99.8%, decides that the file is not complete, leaves it in the download queue and tries (fruitlessly) to download the "missing" 0.2% When this first happened, I deleted the torrent file, made a new one, and posted a message to the forum asking those who had been downloading to delete the file and try the new torrent file. But then two days later, the same thing happened with the same file! I know this ISO file is fine. I've opened it and run it twice. I don't want to delete the file and once again ask everyone to delete it and start again, particularly if the same thing is going to happen 2 days from now.
Have any of you ever had this problem, and, more importantly, do you know how to fix or avoid it? I'm using Azureus 3.0.4.2 on a 2.16 GHz Intel Core Duo MacBook with 2 GB of memory running OS X 10.5.1. I have a fiber optic Internet connection through NTT, here in Japan, and my upload speed on Azureus occasionally surpasses 1MB/s. The file I'm currently having trouble with can be found here. [Edit: Now I've got the same problem with another ISO file here.]
Any help would be greatly appreciated. :bow-pray:
