Print

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

[MAB]

My linux crash and after reboot it lost all files i download. Is there way to take them back or i can go to shoot my self and erase amule from my drive for eternity?

[Mr_Manatane]

Same problem on my computer.
I think under the same circumstances (brutal shutdown due to electric falldown). All of my .part.met files are corrupt.
Of course, help is needed please ! (I got an average 150 dl waiting for some help!!)

[deltaHF]

try to move your part.met files and rename the *.bak files

greets

[Jacobo221]

Did that work? An answer would be appreciated: other users might encounter the same problem in some future.

Thanx and regards.

[Mr_Manatane]

Yes indeed. But I face another problem so I didn't answer right back (and I was a litlle busy).
That's ok, the backup files are fine and allow to get a working conf for dling.

I now work around the second prob : Amule can't write/rename files in the Temp folder. I can't change perm/name nor write and so on the flies after emule has been shut.

before launching amule, I can work perfectly fine on the temp files (rename, delete and so on), all permission are ok.
Some samples :
[mr_manatane@localhost mr_manatane]$ ls -als /mnt/win_i/E_Mule_Temp/
total 23884384
64 drwxrwxr-x    3 mr_manatane mr_manatane    65536 avr 26 09:58 ./
32 drwxrwxr-x    9 mr_manatane mr_manatane    32768 jan  1  1970 ../
342848 -rwxrwxr-x    1 mr_manatane mr_manatane 351075984 avr 22  2004 001.part*
875200 -rwxrwxr-x    1 mr_manatane mr_manatane 896204800 mar 12  2004 002.part*
32 -rwxrwxr-x    1 mr_manatane mr_manatane     2051 avr 26 09:58 002.part.met*
42528 -rwxrwxr-x    1 mr_manatane mr_manatane 145920000 avr 21  2004 003.part*
32 -rwxrwxr-x    1 mr_manatane mr_manatane      507 avr 22  2004 003.part.met*

I precise : All files are located on a FAT32 formatted partition defined by the following : /dev/hda11 /mnt/win_i vfat iocharset=iso8859-15,uid=501,gid=501,codepage=850,syn
c,umask=002,noexec 1 0

If you got a quick answer, I'm interested. I keep searching.

[Jacobo221]

I guess your gid is 501 (that's an important point you forgot to tell us ;-) )
I don't have very clear what the problem is. From what I understood:
1) You have all permisions on a FAT partition's folder
2) aMule starts and all permissions are lost; aMule can't write on that folder
3) aMule is closed but the permissions problem persists

If this is correct, then you should try being root to see if you still can't access those files. If you can't, then those files aren't "closed" (BIIIIIIG bug, I don't think it's that ;-) )
 If you can, then the permissions on that folder have changed. since the kernel applies permissions on a fat partition equally to all directories and to all files (umask sets permissions for both fiels and directories, dmask only for directoryies and fmask for files),if you can't write on that folder, you shouldn't be able to write on any other folder on that partition. Anyway, I don't think aMule executes a command such as remount or so (no idea, though) since those commands most of the times require superuser priviledges.

Please be more verbose. I mean, explain a little on the things you tried to fix it yourself and the results you obtained. that will help us too ;-)

As a clue, aMule doesn't care about the file's permissions. It only cares on the directory's permissions, so, if you have ~/.eMule with no write permission on your user, aMule will still be able to overwrite it if the folder containing that file (your home directory) has write (and execute) permissions for you. I hope this example meade clear what I meant by "amule doesn't care about file permissions" ;-)

Well, just explain a little more about yor problem.

Greetings.

[Mr_Manatane]

AAAArgh! It's getting awfully worse!

1) Answers to your questions :
You're right: you cleary understood the problem (even if I wasn't very verbose and my english spelling is quite approximative)
Yes, I'm user mr_manatane (501) and have a group mr_manatane (501).

Right also :
In fact,
- before launching amule (initial state: just after booting, ), everything's fine
- after the first launching and shutting of amule, every file of the partition /mnt/win_i is problematic (even those not belonging to the E_Mule_Temp and E_Mule_Incoming); cannot change anything at them. Even if I'm root. Answer is :

[mr_manatane@localhost win_i]$ sudo mv Thumbs.db Thumbs.db.bak
Password: [******]
mv: ne peut déplacer `Thumbs.db' vers `Thumbs.db.bak': Read-only file system

>Anyway, I don't think aMule executes a command such as remount or so (no idea, though) since those commands most of the times require superuser priviledges.

What says a mount :
(...)
/dev/hda11 on /mnt/win_i type vfat (rw,noexec,sync,iocharset=iso8859-15,uid=501,gid=501,codepage=850,umask=002)
(...)

Moreover, I found these three lines in the /var/log/messages :
Apr 26 09:58:45 localhost kernel: Filesystem panic (dev 03:0b).
Apr 26 09:58:45 localhost kernel:   fat_free: deleting beyond EOF
Apr 26 09:58:45 localhost kernel:   File system has been set read-only

Before trolling, I'd like to know if the dev 03:0b represents (or is linked to) the partition in cause.

2) Another problem appears : (It's the 1st amule launching after the one above)
[root@localhost mr_manatane]# amule &
[1] 2566
[root@localhost mr_manatane]# Initialising aMule
Config:
x1: 47 y1: 201 x2: 1110 y2: 526
split read, found : 0
srv_split read, found : 463
Detected temp dir /mnt/win_i/E_Mule_Temp on fat32 mount device /mnt/win_i, disabling chmod for that files
Detected Incoming /mnt/win_i/E_Mule_Incoming dir on fat32 mount device /mnt/win_i, disabling chmod for that files
Server listening on port 4712.

*** TCP socket at 4662
*** UDP socket at 4665  (chat)
*** UDP socket at 4672
Serverlist loaded.
*** reading servers
Loading temp files from /mnt/win_i/E_Mule_Temp/*.part.met.
Loading 003.part.met... ERROR!
Loading 013.part.met... ERROR!
Loading 002.part.met... ERROR!
(and so on)

So I can consider my .met files are corrupt? Further, There arent any more backup files in the Temp folder! Is ist normal or linked with the first problem?

[Kry]

The error is on your filesystem, not amule related.

[Mr_Manatane]

I'm okay, but what causes the FS to panic, during the exec of amule?
BTW what should I (re)install or what should I work around to get a working conf please? Could I have only a clue?

[Mr_Manatane]

okay. I've solved the problem.
It appeared to be an error in the clusters of the partition. This error wasn't solved the first boot after the crash of the computer because the fsck.msdos program doesn't change anything on the filesystem (must work deeper on that). Made a fsck on win$ to repair it for sure.
So these errors caused the Fs crash makin it read-only and so on and so on. Couldn't imagine a fs error wouldn(t be repaired!!
Thanks for the remarks and suggestions.

[Kry]

Sorry for the dry reply, but I was in a hurry