Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mithrandir77]

Hi to everybody.
My amule-cvs (and as i can remember amule 2.0.3 too) stops all the downloading files when no free space remains on the hd.

Why it doesn't stop only the last download it has started (which causes the problem) as emule do instead of all the downloading files?

Is it a bug or is it the expected behaviuor?


Thanks a lot



p.s.: excuse me for my not so good english...  

[thedude0001]

Basically this is expected behaviour. If any file runs out of diskspace it's being stopped. And if the file system is full it is full. It doesn't matter in what order the downloads were started, when there's no space left there's no space left

Thinking about it I guess I know the different behaviour with emule you may have noted. emule tends to allocate the complete space for a file relatovely early in a download. So if you start 5 new downloads and don't have enough space these five will be stopped, but the others will continue downloading since the disk space for them is already allocated (emule does so in order to reduce fragmentation on the hard drive). amule doesn't do so, it only uses the space for data actually downloaded...

[mithrandir77]

Thanks a lot.
I don't know about this difference between amule and emule.

Can you explain me about the reason of this difference?  

[skolnick]

@thedude:

What about we guys who use filesystems which do not support sparse files? (FAT32 in my case) when a download stops for no free space, there are usually lots of files which already allocated all of their space, and could continue downloading with no problems at all. That's a problem for me, since amule does not tell how much space needs to finish (like emule does) and when i let it alone, I sometimes come back, and find all my downloads are stopped simply because one of them left no free space. That would be no problem for emule, should not be for amule IMHO.

Regards.

[Kry]

aMule only stops files when there is no space to continue downloading.

[mithrandir77]

Originally posted by skolnick
@thedude:

What about we guys who use filesystems which do not support sparse files? (FAT32 in my case) when a download stops for no free space, there are usually lots of files which already allocated all of their space, and could continue downloading with no problems at all. That's a problem for me, since amule does not tell how much space needs to finish (like emule does) and when i let it alone, I sometimes come back, and find all my downloads are stopped simply because one of them left no free space. That would be no problem for emule, should not be for amule IMHO.

Regards.

thedude, this is the same problem for me...
I run amule on Fat32 (to let me to use on windows when i have to reboot)...

[skolnick]

Originally posted by mithrandir77
Thanks a lot.
I don't know about this difference between amule and emule.

Can you explain me about the reason of this difference?  

There is not such big difference. In fact, the difference more than amule or emule, lies in the filesystem they use to store the files. If you run emule on NTFS filesystem, and check the option to "use sparse files" it will behave the same as amule (use only actually downloaded space, will not allocate full space). But if you untick that option (on emule) or use it on FAT32, the space is complketely allocated at once. That is because NTFS supports "sparse files" while FAT32 does not. Same happens with amule, all of the filesystems in UNIX (at least ext3 and UFS for sure) do support sparse files, so amule uses only actual download space. But if you use amule on FAT32, it will allocate the full space of the download, no matter what, since the filesystem lacks this feature.

@Kry: I'm not really sure about the latest CVS versions, but in some weeks ago CVS, amule would stop all the downloads when it left no free space, no matter if the downloads had or not the full allocated space. I'll check current CVS and report back.

Regards.

[Jacobo221]

after readin skolnick's post, i think fiels should be stopped when they are known not to have neoguh space to continue downloading instead of all at a time. In fact, I thought it worked this way already

compatibility with eMule is one of the big deals with aMule, remember

[mithrandir77]

Originally posted by Kry
aMule only stops files when there is no space to continue downloading.

Ok... But it stops all files downloading, even if it is running on a FAT32 partition