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?