John Lenton writes:
> as the subject says:
>
> lrwxrwxrwx 1 root root 281474976710666 Jan 27 20:50 imlib1 -> imlib-base
>
> it isn't the only one, for example
>
> lrwxrwxrwx 1 root root 281474976710669 Jan 27 14:43 fd -> /proc/self/fd
>
> i.e. 2**48 + what it should be.
Can you do the following:
ls -i (path)/imlib1; ls -i (path)/fd # record inode numbers
debugfs /dev/hdX
stat <inode_number> # '<' and '>' are required
send output. This should tell us if the badness is stored on disk or in
memory. Of course e2fsck would help as well. Were these newly created
inodes, or existing ones? If you shutdown and restart, does it go away?
Anything in syslog about ext2 warnings or errors?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
