have a look at this, I did a run of fsck and had a similar result, a size error is reported with exactly the large file only ... can this be a coincidence? I don't think so. Also, AFAIK I'm using sparse files for temp, hope the bug is not in this area ... would be a shame (and waste of Hd space) if one could not use that feaure ... then again I'm not sure about sparse files, a I can't find an option in amule and ls and du show he same filesizes, Could be that I remember that from emule and mixed it with the knowledge that reiserfs can handle sparse files too. I'm not an expert there ...
Results:
vdr01 ~ # umount /dev/hda5
umount: /mnt/hda5: device is busy
umount: /mnt/hda5: device is busy
vdr01 ~ # umount -l /dev/hda5
vdr01 ~ # fsck.reiserfs --fix-fixable /dev/hda5
reiserfsck 3.6.17 (2003 [URL]www.namesys.com[/URL])
Will check consistency of the filesystem on /dev/hda5
and will fix what can be fixed without --rebuild-tree
Will put log info to 'stdout'
###########
reiserfsck --fix-fixable started at Tue Aug 23 18:15:14 2005
###########
Replaying journal..
Trans replayed: mountid 73, transid 4954288, desc 6111, len 4, commit 6116, next trans offset 6099
Trans replayed: mountid 73, transid 4954289, desc 6117, len 4, commit 6122, next trans offset 6105
Trans replayed: mountid 73, transid 4954290, desc 6123, len 4, commit 6128, next trans offset 6111
Trans replayed: mountid 73, transid 4954291, desc 6129, len 4, commit 6134, next trans offset 6117
Trans replayed: mountid 73, transid 4954292, desc 6135, len 7, commit 6143, next trans offset 6126
Trans replayed: mountid 73, transid 4954293, desc 6144, len 40, commit 6185, next trans offset 6168
Trans replayed: mountid 73, transid 4954294, desc 6186, len 14, commit 6201, next trans offset 6184
Trans replayed: mountid 73, transid 4954295, desc 6202, len 6, commit 6209, next trans offset 6192
Trans replayed: mountid 73, transid 4954296, desc 6210, len 14, commit 6225, next trans offset 6208
Trans replayed: mountid 73, transid 4954297, desc 6226, len 20, commit 6247, next trans offset 6230
Trans replayed: mountid 73, transid 4954298, desc 6248, len 9, commit 6258, next trans offset 6241
Trans replayed: mountid 73, transid 4954299, desc 6259, len 1, commit 6261, next trans offset 6244
Trans replayed: mountid 73, transid 4954300, desc 6262, len 68, commit 6331, next trans offset 6314
Trans replayed: mountid 73, transid 4954301, desc 6332, len 12, commit 6345, next trans offset 6328
Trans replayed: mountid 73, transid 4954302, desc 6346, len 1, commit 6348, next trans offset 6331
Reiserfs journal '/dev/hda5' in blocks [18..8211]: 15 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
/tmp/track-01.isovpf-10670: The file [2 100] has the wrong size in the StatData (4294434816) - corrected to (4294434816)
/amule/temp/002.partvpf-10670: The file [111 231] has the wrong size in the StatData (2832269312) - corrected to (2832269312)
/003.partvpf-10670: The file [111 371] has the wrong size in the StatData (2618664581) - corrected to (2618667008)
/014.partvpf-10670: The file [111 338] has the wrong size in the StatData (2832236544) - corrected to (2832236544)
finished
No corruptions found
There are on the filesystem:
Leaves 24964
Internal nodes 180
Directories 56
Other files 926
Data block pointers 25064981 (2489863 of them are zero)
Safe links 14
###########
reiserfsck finished at Tue Aug 23 18:16:42 2005
###########
vdr01 ~ #
Note the 3 large files with problems 002, 003 and 014.part
Output of previous command 2 day's ago only shows the 0% problem file (014.part)
###########
reiserfsck --fix-fixable started at Sun Aug 21 05:46:01 2005
###########
Replaying journal..
Trans replayed: mountid 73, transid 4489188, desc 4368, len 8, commit 4377, next trans offset 4360
Trans replayed: mountid 73, transid 4489189, desc 4378, len 8, commit 4387, next trans offset 4370
Reiserfs journal '/dev/hda5' in blocks [18..8211]: 2 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
/tmp/track-01.isovpf-10670: The file [2 100] has the wrong size in the StatData (4294434816) - corrected to (4294434816)
/amule/temp/014.partvpf-10670: The file [111 338] has the wrong size in the StatData (2832236544) - corrected to (2832236544)
finished
No corruptions found
There are on the filesystem:
Leaves 31942
Internal nodes 221
Directories 57
Other files 1448
Data block pointers 32036977 (7306137 of them are zero)
Safe links 14
###########
reiserfsck finished at Sun Aug 21 05:48:18 2005
###########
also note that the "lost" value is now down to 1.6 GB .... might be the described problem with the .met files ... how about you simply add the values twice, the original one with the 4GB limit and one bigger? Would of course only work if emule is ignoring unknown values in .met files ... but would keep backwards compatibility ...