|
Notes |
|
|
|
|
While hashing, aMule uses all CPU with high priority (all other progs freeze, music stop playing) for several seconds. |
|
|
|
|
|
On what kind of file-system / medium is the file stored? Can you check your dmesg for possible IO errors? The error-message suggests a problem with either your filesystem or hardware. |
|
|
|
|
hi
I use ext3 filesystem and i get this error in dmesg:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x64
ata1.00: cmd c8/00:00:68:d7:61/00:00:00:00:00/e2 tag 0 dma 131072 in
res 51/40:00:0b:d8:61/00:00:00:00:00/e2 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
02 61 d8 0b
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 39966731
ata1: EH complete
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
So it's not related to aMule? |
|
|
|
|
No, it's probably not related to aMule.
The next time you get that exception, check your dmesg's for specific errors.
You might also want to run a full fsck check on the filesystem using badblocks (pass the "-c" flag to fsck.ext3). |
|
|
|
|
After fsck'ing, amule managed to hash the file.
There was indeed some problem on my fs.
I don't know how to close bugs, sorry.
Thanks,
Regards,
Charly |
|