Re: e2fsck problem: (Bad address) while doing inode scan

On Mon, 31 Mar 2003 12:23:32 -0700, Erik Andersen <andersen@xxxxxxxxxxxx>
wrote:

>Next step...  Try running an strace if the libc5 binary and
>compare the set of lseek calls being made to the strace you
>already made of the uClibc binary.  I suspect that will tell
>us a great deal, since the libc5 binary works,
I straced glibc-2.1.2 since libc5 is on vmware and more problematic to test
right now.

This is uclibc:
...
...
lseek(3, 176455680, SEEK_SET)           = 176455680
read(3, "\266\201d\0w\0\0\0\246\225\353;R\226\353;\207K\364:R\226"..., 8192)
= 8192
lseek(3, 176487424, SEEK_SET)           = 176487424
read(3, "@\241\2\0A\241\2\0B\241\2\0C\241\2\0D\241\2\0E\241\2\0"..., 1024) =
1024
_llseek(3, 4294967296, 0x9febfc00, SEEK_SET) = -1 EFAULT (Bad address)
write(1, "Error reading block ", 20Error reading block )    = 20

This is glibc-2.1.2 (Red Hat 6.x):
...
...
2
lseek(3, 176455680, SEEK_SET)           = 176455680
read(3, "\266\201d\0w\0\0\0\246\225\353;R\226\353;\207K\364:R\226"..., 8192)
= 8192
lseek(3, 176487424, SEEK_SET)           = 176487424
read(3, "@\241\2\0A\241\2\0B\241\2\0C\241\2\0D\241\2\0E\241\2\0"..., 1024) =
1024
_llseek(3, 18446744072097627136, [6978010112], SEEK_SET) = 0
read(3, "\0\373g\0\1\374g\0\2\375g\0\3\376g\0\4\377g\0\226\1h\0"..., 1024) =
1024
_llseek(3, 18446744072097628160, [6978011136], SEEK_SET) = 0
read(3, "\1\373g\0\2\373g\0\3\373g\0\4\373g\0\5\373g\0\6\373g\0"..., 1024) =
10
...
and go on and on, then it does lseek again.
...

Thanks

-- 
giulioo@xxxxxxxxx