aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Lost .met files after PC freezed  (Read 2880 times)

aaractingi

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Lost .met files after PC freezed
« on: April 26, 2004, 11:37:01 AM »

Hi,

I use amule 1.2.6 on a Mandrake 10.0, Temp and Incoming dir are on a FAT32 partition. For some reason I had to hard reset my PC, and I "lost" most of my current downloads. I noticed that the .met and .met.bak showed a size of 0 byte, whereas the .part file still seems ok.

I saw another thread about this problem, but couldn't find an answer. I moved my Temp dir to an ext3 partition today and I'll see if it helps, but is there a way to import the parts of the files that were already downloaded?

Thanks a lot,
Alex
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: Lost .met files after PC freezed
« Reply #1 on: April 26, 2004, 12:28:36 PM »

The obvious and elegant way is to move all *.met.bak files into *.met... but since your .bak files are 0 bytes long, that will not help :-(
There are apps which reconstruct .met files, but I've never tried them (never needed them, thanks God). Join #amule in irc.freenode.net and ask. Some user will answer surely. Or just google for it (or look at http://www.emule-project.net

Hope that helped.
Greetings.
Logged

aaractingi

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: Lost .met files after PC freezed
« Reply #2 on: April 26, 2004, 12:47:19 PM »

Thanks for your answer!
I'll join the IRC channel tonight, and wiull try to reconstruct my .met files.
By the way, how come both my .met and my .met.bak files got corrupted at the same time?
(not the first time it happens, sadly)
Thanks again for your answer,
Alex
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: Lost .met files after PC freezed
« Reply #3 on: April 26, 2004, 12:52:40 PM »

No idea really. I never used 1.2.6. I went up until 1.2.5 and then directly into v2-rc1. Maybe that was a 1.2.6 bug, but I don't know. If it still happens in the v2-rcX versions, then it might be a kernel or a filesystem module issue rather than an aMule problem, becase no-one has reported such a problem yet on this versions ;-)

We'll meet later at night, I guess.
C'ya!
Logged