ext2fs bug

[gabor at zahemszky.hu]

Hi!

I've got 2 disks (a 1TB and a 2TB), these disk were written under Linux 
2.4.
I can mount them under FreeBSD, and I can reach about half of the 
files, but
on some files, I only get some FS errors. In dmesg, I can see the 
following
errors:

g_vfs_done():ada2s1[READ(offset=-756558786560, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-899189821440, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-756558786560, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-899189821440, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-756558786560, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-899189821440, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-756558786560, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-899189821440, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-756558786560, length=4096)]error = 5
g_vfs_done():ada2s1[READ(offset=-899189821440, length=4096)]error = 5

The disk is not bad: I can read the same files under the original 
Linux,
and on a newer Linux-machine, and I can read it under FreeBSD with the 
e2fsprogs package's
debugfs tool (I can copy the files with the dump and rdump commmand 
from debugfs.)

Itt looks, that there are some misinterpretation of some of the 
metainfo
in the Ext2 fs-driver. (Or maybe some signed/unsigned bug in it.)

Can anybody help? Can I help to anybody with some more information?

Thanks,

Gabor < Gabor at Zahemszky dot HU >

PS: sometimes I can only see az empty directory. Sometimes, I can reach 
half of the files
in a directry. But the kernel error message is the same.