Re: fsck seg fault failure on vmware -i386?

[David Laight <david%l8s.co.uk@localhost>]

On Sun, Feb 07, 2010 at 02:49:35PM +0700, Robert Elz wrote:
> 
> Which leaves (reformatted a little for readability)
> 
> dp1 = {di_mode = 56751, di_nlink = 19288
>       di_u = {oldids = {0, 0}, inumber = 0},
>       di_size = 13817003198315359381,
>          di_atime = -1077945624, di_atimensec = 134541206,
>          di_mtime = 224938, di_mtimensec = 0,
>        di_ctime = 134605714, di_ctimensec = 0,
>        di_db = {224938, 0, 134605973, 224938, 0, 18730, -1077945464,
>                134563445, -1077945548, 134605973, 1, 134563194},
>        di_ib = {-1148186544, 134607596, 56196},
>        di_flags = 72, di_blocks = 9, di_gen = 0,
>        di_uid = 900, di_gid = 9, di_modrev = 224938},
> 
> as the inode in question.

That data doesn't look very good to me at all.
(Under the assumption it is supposed to be a disk inode.)

di_size is a little large (isn't that the file size in bytes?)
None of the time fields is anywhere near 'now'.
There are silly numbers in di_db (these are the fragment numbers for
the first few disk blocks) and di_ib (the indirect blocks).
(All those numbers should be muliples of the 'frags per block' value).

Looks like the inode table (on disk) is seriously stuffed!

        David

-- 
David Laight: david%l8s.co.uk@localhost