Outline · [ Standard ] · Linear+ Continuous file corruption

There's a continuous file corruption whenever emule freezed and is restarted. A certain part will always be considered corrupted no matter which user you get it from. This was also complained by others in the support section. wonder what's up

QUOTE

There's a continuous file corruption whenever emule freezed and is restarted.

I'm not really sure what to make of this, I'm not sure I completely understand your problem. But the best advice I can give is to simply keep waiting. Its possible that your problem is related to the new fix for "supercompressed blocks/0 filled part senders" - you aren't trying to download a CD image by any chance are you? Just try and be patient more than likely you WILL eventually find a good source for the file.

There's a few threads talking about possibe problems with the new fix for "0 filled part senders". I can only find one of them right now...
here

I am not quite sure if the problem is related. It is not an image file to start with. Let's see how I can make it more clear... this is not the first time it happened. I am certain that if I delete the file and redownload the exact same one, it is bound to finish because I have tried it before. The only thing that is stopping me from doing it is that I have less than 1 mB to complete and don't want to restart a 600mB download.

Anyway, the last part continues to give constant part corruption problem and restarts at the exact same size before the last chunk is downloaded. And it goes on and on and on.... and on...

I have experienced lately the same kind of problem.
I'm using v1e. Previous versions worked well. So the v1e until suddenly started to behave weird. No matter what kind of file or length.

Maybe I should downgrade to v1d?

I'm having this problem right now and I'm over it. Time to change emule clients. I was trying to get a .bin file and had just a tiny bit at the end of file to get to complete it and it would not finish. This happens to me over and over and over. Normally I delete the file and start the download again. Believe it or not, downloading 700mb will still be quicker than waiting around for this tiny section at the very end of the file to complete. Heck it's not even a complete part. By last night was the last straw. I checked the stats and my client had downloaded 1.3gb of a 700mb file. WTF! It had kept re-downloading this same part of the file over and over and over again. emule kept saying this part was corrupt. but if I exit emule, start it up again, it says there may be corruption and is hashing the file. then it says file checked out ok. I'm using emule plus v1e. but not any longer. what a waste of time. I've been replacing my computers, network cables, hubs, nics etc. and all along it appears it's a software issue.

- km

QUOTE

I'm having this problem right now and I'm over it. Time to change emule clients.

Of course that's your choice. But I urge you to try and be patient a little longer. This issue has been resolved in v1f and will be released soon! If you really can't wait you can simply use another client temporarily to finish the last chunk of your file.

Not sure if this applies, but theres one file that Im having problems with. Its got 26MB remaining so i dont think its the last chunk, that needs downloading.
So far ive got the corrupted message for part 21, more than 15 times for the same file. File is a video file which is why im not sure if it faces the same problems as cd images.
The other video files of the same set arent having these problems, which makes it even weirder.
Oh well.

Wait and see.

Also The corruption loss for the video file is quite small to what I considered it to be. 17Mb of corrupted data.....surprisingly small for something which has corrupted 15+times

This post has been edited by reanimated838uk: May 25 2003, 01:01

QUOTE (thisIsRandom @ May 25 2003, 12:51 AM)

Of course that's your choice. But I urge you to try and be patient a little longer. This issue has been resolved in v1f and will be released soon! If you really can't wait you can simply use another client temporarily to finish the last chunk of your file.

sounds interesting. i'll try v1f when it comes out. i've gone back to v1d for now. it's just got me a bit mad thats all as I had spent quite a bit of $$ replacing all these computer components, even get 2 new computers and they all did the same thing at one point or another. but it was always random so was hard to nail down what was wrong. anyway if the programmers are aware of it, then that's great. the problem should be taken care of.

- km

@KoolMonkey : 1f will also have a new jucy feature for releasers, which you might be interested in

what's the juice moose? I still use v1 of plus to release on and v1e to download on. i like v1 as you can control the download slots etc and each user gets the same bandwidth. with the later versions it was a bit weird in that one user gets 98% bandwidth and the others get like 0.1k.

- km

thats because of the zz upload system. More info in the common questions section

ZZs upload system should be better for releasers (more info in FAQ):

It maximises your upload speed and gives you a much flatter upload graph, than the official client.
Complete parts will also get out to other clients much quicker, which means the releaser has to upload less to get the same spread.
It works better at higher speeds.

The new "juce" in 1f will make releasing a file even quicker/effective, but your will have to wait for 1f for details.