Print

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

[underhosi]

before i went to bed i still had 12 GB free space on my harddisc, this morning only 500MB left.
But all the files i choosed to download are not ready yet.
so how can that be. all the files that were downloading in amule stopped, everything turned black.

i'm in trouble here, anyone here to help?

[lionel77]

I think what happened was the following: You started a lot of new downloads before you went to bed. Since HFS+ (the default file system on OS X) does not support sparse files, aMule allocates the full file size whenever the first bytes of a given file are downloaded. Over the course of the night aMule allocated 11.5gb worth of hard drive space for files that it had started to download. Then aMule realized that given the available hard drive space and the "Min disk space" limit (aMule Preferences -> Files) there was not enough space available to allocate space for the next file it was starting to download. As a consequence, it stopped the download of all files (set their status to stopped).

In order to get aMule going again you want to do the following two things:
1) Make sure that the available hard drive space is at least a bit more than the "Min disk space" limit (see above).
2) Resume (control-click on a file -> Resume) only those files for which disk space has already been allocated, i.e. which are downloaded more than 0.0%. Once some of these files are finished you can burn them to CD/DVD or move them to a different hard drive and start downloading either new files or resume files that are still at 0.0% download progress.

Hope this makes sense.

[ken]

Actually, lionel77, aMule doesn't allocate the full space required for a file on receipt of the first byte.  Rather, each byte it receives is just put in the proper place in the file.  So, if a byte belongs at the beginning of the file, the file system will only allocate the first block.  If it belongs in the middle of the file, the file system will allocate enough space to cover from the beginning to the middle.  If it belongs at the end, the file system will make sure the full size of the file is allocated.

So, it is not true that if a file has more than 0.0% download progress all of the necessary space has already been allocated.  The only sure fire way to make sure you don't run out of space is never start downloads the sum total of whose sizes is more than your free space.

So, the fix for underhosi's problem may be more complicated than you suggest.  It's currently hard to tell how much space has actually been allocated for a given partial download and how much it will need to complete.  You have to determine its part file number, go to the Temp directory, and check the size of the .part file.  Then subtract that from the total size that it will be when completed (as reported by aMule).  The result is the amount of free space you will need for it to successfully complete.

Using that method, find a download which has been completely allocated, or which has enough space to completely download.  Resume that download.  Let it complete.  When you're done with it, remove it from your hard drive to free up some room.  Now repeat the process with the next download.

Or, of course, you could just free up enough room on your drive to accomodate all of the downloads you started and resume them all.  Or, cancel some downloads for whom space has been allocated, but which you don't need urgently.  You can always download them later.  Then resume the rest.

The bottom line is that aMule can't manufacture new hard drive space.  You have to have enough available for the things you're trying to download.  What exactly did you expect to happen when you started more downloads than you could fit on your disk?

[lionel77]

Thanks for the clarification, ken. I had just assumed that since hfs+ does not support sparse files, aMule would allocate space for the complete file at once.