aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: .part .met temp files not cleared after download complete ?  (Read 3142 times)

mrechte

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 4
.part .met temp files not cleared after download complete ?
« on: April 30, 2005, 07:49:20 AM »

Hi,

When checking my temp directory, I noticed that there are .met files thare are bigger than the biggest file I am currently downloading. I wonder whether that directory is properly cleaned.

How would I know that a file is no longer used, and therefore  can manually be deleted ?

Thanks
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: .part .met temp files not cleared after download complete ?
« Reply #1 on: April 30, 2005, 08:59:13 AM »

click in the amule-gui on your downloads, rightclikc and in the middle you can read what part file it is, at the preview

or select file details from that menu, its also written there
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

mrechte

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 4
Re: .part .met temp files not cleared after download complete ?
« Reply #2 on: April 30, 2005, 09:18:50 AM »

Thanks for your help

I just realised that each current download creates one .met file of nearly (I say nearly because in some cases it is less) the file size, even if a small portion of it is downloaded. This is is a big waist of hard disk space !

Regards

Marc.
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: .part .met temp files not cleared after download complete ?
« Reply #3 on: April 30, 2005, 09:30:25 AM »

no its not a big waste...

hte file size is most often completly allocated after you dl 9,98 MB of the whole file (which is one part)

so then the amule creates a container where this downloaded part goes into, and it starts to download the next part,
but since you dont start usually with part 1 and then 2 and so on, all the file size is used, to put the actuall parts already where they belong.

other sharing systems where teh file size increases while downloading, start at teh beginning, which makes them slow, since in ed2k you can download 2 different parts independently. every mule programm will do it this way
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: .part .met temp files not cleared after download complete ?
« Reply #4 on: April 30, 2005, 04:24:41 PM »

###.part is the file name where your downloaded data goes. ###.part.met is the description of the .part file, and should be only some kb.

When aMule downloads a piece of data, opens the .part file, seeks to the position where this piece belongs to, and writes it there. This will result in the file size enlarged to the position of the last downloaded data piece. Actually on file systems which support sparse files, disk space is only allocated for real downloaded data, not for empty parts.

Example: say you start downloading a 800Mb file. Say, that aMule first downloads 180kb from the middle of the file. When it is saved, the .part file size will be 400Mb, but only 180kb disk space is allocated.
Logged
concordia cum veritate

mrechte

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 4
Re: .part .met temp files not cleared after download complete ?
« Reply #5 on: May 02, 2005, 08:13:19 AM »

Thanks a lot for this clarification. To convice myselft I ran these commands:

$ du 017.part
348508
$ du -b 017.part
418304000
Logged