aMule Forum
English => en_Bugs => Topic started by: Archmage on July 07, 2008, 10:34:04 AM
-
I'm using the XFS-filesystem, but when my PC crash/hardware reset/has an electricy short cut than the part.met-files for the files that I was active downloading are trashed (they have 0 bytes). Moreover the part.met.bak-files are also trashed (they also have 0 bytes), leaving me with an absolute useless part-file.
Since aMule isn't storing the information what part-files are what file, I'm left with no clue what to do with this files, beside deleting them and redownload everything.
I'm sure that this isn't the planed behavior.
-
Sounds like a full or inconsistent file system to me. Did you run a fsck ? What's your free disc space ?
Note - free disc space checking was fixed only recently.
-
fsck didn't report any errors. It is a 250 GB hard drive, with one 250 GB XFS partition, where 130 GB is free.
-
XFS is the least suitable filesystem for a system that has to face shutdowns. Use a more solid filesystem, or buy a electricity accumulator to save your data before shutdown.
-
Isn't there another way instead of switching the filesystem?
I'm very happy with the performance so far. The only problem are the files that are currectly open when there is a problem. And when downloading the part.met, the part.met.bak seems to be both open.
Would it be possbible to have one close when downloading, so that we have a part.met.bak that can be used for something?
-
Both are closed while downloading. Occasionally the met file gets updated, and immedeately after that copied to the bak file. (Not if the met file should be zero at that moment for whatever reason.)
The only explanation for your problem is that the writes get stuck in a disc cache, and then get trashed at your "PC crash/hardware reset/has an electricy short cut" event. What about that btw ? This is 2008. Computers don't crash all the time, not even those running Windows.